Page History

Summary

actionbar - enabled/disabled visible/hidden

based on selected node/item

based on roles

Availability

...

Problem

The action bar can take several states within one sub-app.

...

• Action bar definition should define two things:
  
  • the structure: sections, groups, and all possible actions in these groups, in one single place. This ensures proper ordering of actions at all time
  • the states that describe e.g. the section titles, the set of actions displayed, and potential substates. This mechanism should allow for additive composition of states (think of the use case for an optional AND editable area in page editor)
• Implementing context sensitivity then only means to configure these states properly and toggle between them.
• It is likely that context sensitivity is not handled at all at the action bar level, but rather straight on the actions.
  
  • If so, the action bar definition is reduced to its sole structure.
  • Edge case (page editor): do we provide a way to configure context-sensitive section titles?

Decision

-

Access Control

...

Configuration Proposal

Given the base path /modules/foo-app-bar/apps/bar/subApps/workbenchbrowser/

...

• An option is to use voters for both visibility and disablement of an action (see delete action).
• We may then consider a default configuration for content subApps