A natural augmentation to permissions would be to add a new tab for actions and be able to assign execute rights to roles… Ahh … now that would ease a few tasks on my todo list! While i am at it: the permission UI is rather limited, if you could expand it a tad, allow sorting, more columns, perhaps grouping etc… just a thought, cheers, drew…
We have closed this ticket because another page addresses its subject:
ConditionalAppearance - Make it possible to manage Action availability against the currently logged userlimit access to action by role
Answers
Hello Drew,
Please explain your requirements in greater detail:
- which actions do you need to disable?
- everywhere or for strict business classes?
- for ListViews or for DetailViews?
- for WindowsForms or for ASP.NET applications?
- hide an action from a toolbar, or from a menu, or everywhere?
- for one user or for all users?
- anything else?
Thanks,
Dan
Hello,
XAF v20.1 includes a preview of Action Permissions. This new XAF security layer allows developers to prohibit execution of both custom and XAF system Actions within WinForms and ASP.NET applications: Video Overview | Documentation.
To enable this feature in versions earlier than v20.1.6, set the static SecurityStrategy.EnableSecurityForActions property to True. To add custom Actions or remove system Actions available in the Denied Actions tab, handle the NonSecureActionsInitializing event.
Note that Action permissions will unconditionally hide Actions: we don't expect to interfere with Conditional Appearance, State Machine, TargetObjectsCriteria, or any custom rules that are driven by criteria or object/UI changes within Controllers. If you require dynamic functionality for Actions, use these specific methods and built-in criteria functions such as IsCurrentUserInRole and CurrentUserId. If these solutions do not meet your business needs, please submit a separate ticket and elaborate on your scenario there.
Thanks,
Andrey