Page History
This concept page describes both how to control when an action is available and how to restrict access to such actions.
| Table of Contents |
|---|
Availability
The availability is based on the selection although specific exceptions exists. For instance not all actions operate on a selected node. For redo/undo we will enable/disable based on the undo history size.
...
Q: Do we want to hide a section if all its actions are disabled? What if the user is not authorized to use any of the actions does it then make sense to hide the section?
Access Control
Determining wether the current user has access to an actions should be based on roles. We need to configure the required roles on the action definition.
...
Groups and items can be enabled/disabled.
Logic charts for current behaviour
| Contacts App | S folderActions | G addActions | G editActions | S contactsActions | G addActions | G editActions |
|---|---|---|---|---|---|---|
| no selection or root | x | x | x | x | ||
| mgnl:folder | x | x | x | x | x | |
| any other node | x | x |
...
| Pages | A delete | A preview | A edit | A export | A activate | A deactivate | A activateRecursive |
|---|---|---|---|---|---|---|---|
| no selection or root | |||||||
| any selection | x | x | x | x | x | x | only if no sub pages |
Configuration proposal (rejected)
on each level, section, group, action, we need to configure three things:
...
Overview
Content Tools