Access/ visibility of Subscriptions

​@MelanieSchmiedel not sure when it comes to Subscriptions, but in general in order for a user to be able to see other users data (printed PDF in Report Archive / History Logs) they can only see it if they have ADMINISTRATOR system proviledge.

It’s worth a check.

Hi Marcel,

thanks for the hint. I checked the permissions the user has, and there is no Administrator privilege added to our end-.user role and yet she can see the permissions

I also checked her other permissions, but it’s the same (no admin privilege).

kind regards,

Melanie

What version do you use ?

Checking on Apps 10 U23 and Cloud 24R2, the SQL qeury for that screen specifically has a filter on the username being the person logged in.

Hi Simon,

I guess that's the reason. We`re on Apps 10, UPD20 and when I open the console there is no pre-filtering:

So, possibly just in need for an update.

Kind regards,

Melanie

Don’t forget to click on the actual line to see the SQL code:

Click here first, otherwise it won’t populate the SQL statement actually being made on the right :)

Ah, yes: the WHERE clause isn`t there:

Cool so yeah it seems that’s something they’ve added after U20 then :)

Yeah, seem like it - not a big deal. Thank you very much! Have a nice day :-)

Hi ​@MelanieSchmiedel, 

Thank you for raising the concern regarding the visibility and accessibility of subscriptions on APP10. You're right to check, subscriptions are intended to be personal, meaning each user should only be able to view and access their own configured subscriptions.

To provide an accurate solution, could you please confirm the version of APP10 you’re currently using?

Thank you!

Hi Shakya,

yes, we`re using App10 with UPD20.

BR

Melanie

Hi ​@MelanieSchmiedel, Thanks again for the details.

As mentioned earlier, in IFS APP10, each user can configure their own Subscriptions. Subscriptions are designed to be personal, Users should only be able to view and access their own setups.

That said, the behavior you've highlighted was identified as a defect in earlier versions of APP10.
The good news is that this issue has been addressed and resolved starting from APP10 Update 21 and onwards.

Regarding the third question you raised, we are currently investigating it and will keep you informed as we have more insights to share.

Thank You. 

Best regards,
Shakya

Hi Shakya,

thank you! Its good to know that the issue is already under control :-). 

Thanks for keeping me posted about the other issue. 

Best regards,

Melanie