[MGNLUI-1345] Change action and actionbar section restrictions to availability and use existing classes Created: 13/May/13  Updated: 24/Jun/13  Resolved: 24/May/13

Status: Closed
Project: Magnolia UI
Component/s: framework
Affects Version/s: None
Fix Version/s: 5.0

Type: Task Priority: Neutral
Reporter: Tobias Mattsson Assignee: Jozef Chocholacek
Resolution: Fixed Votes: 0
Labels: actions
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
causality
is causing MGNLUI-1380 Write test for BrowserSubApp.updateAc... Closed
dependency
depends upon MAGNOLIA-4989 Permissions for operations Closed
is depended upon by MGNLDAM-216 AssetsMainSubApp should control appea... Closed
is depended upon by MGNLUI-1244 Config, Pages and Security apps shoul... Closed
relation
is related to MGNLDAM-222 Introduce Restrictions for action def... Closed
is related to MGNLUI-1377 Workbench: root path not respected, c... Closed
is related to MGNLUI-1603 Implement rule based column availabil... Closed
Template:
Acceptance criteria:
Empty
Task DoR:
Empty
Release notes required:
Yes
Sprint: Beta 2, Beta 3

 Description   

Outlined in http://wiki.magnolia-cms.com/display/DEV/Concept+-+Action+availability+and+access+control

  • Change the term restrictions to availability for actions
  • Move roles configuration to a sub node permissions and use the existing class from core for it
    • Node types stays where it is
  • Change the term restrictions to availability as well for actionbar
    • Should use the same configuration object as for actions
    • This means we'll also have permissions on sections and we should evaluate these as well
  • Definitions should have evaluation logic in themselves to allow for custom classes with custom evaluation logic

The existing classes mentioned were introduced in MAGNOLIA-4989


Generated at Mon Feb 12 08:45:40 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.