Idea Summary
If a component has been configured with an Authorization Scheme that evaluates to false, then the current condition will also be false. This eliminates the need to use logic like "APEX_AUTHORIZATION.IS_AUTHORIZED" in multiple locations.
Benefits:
- Enhances UX by concealing unauthorized elements.
- Mitigates the risk of typos in Authorization Scheme names.
- Boosts performance by eliminating the need for PL/SQL expressions.
Use Cases
- If a "Delete" button uses the Authorization Scheme name "can_delete" along with a server-side condition such as "APEX_AUTHORIZATION.IS_AUTHORIZED('can_delete')".
- Same for a Navigation Menu Item.
Preferred Solution (Optional)
- Application flag that's valid for the entire application by default.
- Server-side condition type "Is Authorized," or a component flag that sets the condition to false if not authorized.