I would like to use a single PL/Sql Function (return boolean) as an Authorization Scheme for multiple components in my Apex application. I am able to use this for List Entries, Pages, Regions and Buttons without issue.
The Authorization Scheme Evaluation point is set to “Always (no caching)” in development and therefore my function has access to Component Type, Component ID and Component Name.
What I've discovered is if I use this Authorization Scheme on an Interactive Grid to determine who can see the grid and if I also apply this Scheme against the Grid's Delete Attribute, when the function is called, the Component ID passed for both cases is the ID of the Interactive Grid. I do not see that I can differentiate between the Authorization of the entire Grid versus the Authorization of the Delete attribute. I run into the same problem with an Interactive Report with Form. The Interactive Report has a Link Attribute with an Authorization Scheme but the Component ID passed is the IR Region. I would not be able to also have an Authorization Scheme against the IR Region and be able to tell it apart from the Link Attribute Authorization as the function in both cases only passes the IR Region ID as a parameter.
Is there a way to tell one Authorization Scheme call from another when you are talking about Regions vs Region Attributes?
Thanks for your help.
Don