[MGNLUI-3622] Provide simple boolean logic for availability rules Created: 12/Oct/15  Updated: 11/Mar/21  Resolved: 11/Mar/21

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

Type: New Feature Priority: Neutral
Reporter: Aleksandr Pchelintcev Assignee: Unassigned
Resolution: Obsolete Votes: 1
Labels: to-specify
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Relates
relates to MAGNOLIA-6407 Access permissions to apps for user r... Closed
Template:
Acceptance criteria:
Empty
Date of First Response:
Story Points: 5

 Description   

Proposed additions:

  • configurable rule negation
  • simple AND/OR rules that delegate to sub-rules

This simple improvement that would allow us:

  • to get rid of redundant rule pairs like e.g. (IsDeletedRule/IsNotDeletedRule).
  • to provide more flexible availability logic


 Comments   
Comment by Roman Kovařík [ 12/Oct/15 ]

Don't you want to go with voters like in MAGNOLIA-6407 so we are consistent?

Comment by Michael Mühlebach [ 12/Nov/15 ]

Evaluate this vs using Voters which is currently done for the travel demo users.
Lets organize a discussion on this topic with PM before implementing.

Comment by Mikaël Geljić [ 12/Nov/15 ]

Voter-based availability was our first proposal back during development of 5.3, but it was demoted for various reasons... Definitely worth re-evaluating though.
See my comment back on the concept here.

Comment by Roman Kovařík [ 11/Mar/21 ]

Implemented in M6.2 as negate property of availability rules.

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