[MGNLUI-5300] Ability to Hide/Show Dialog fields or tabs Based on a Certain Criteria of the Current User Created: 26/Jul/19  Updated: 10/Mar/21  Resolved: 10/Mar/21

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

Type: New Feature Priority: Neutral
Reporter: Tou Xiong Assignee: Unassigned
Resolution: Workaround exists Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Relates
relates to MGNLUI-2542 Dynamic forms & cross-field interaction Accepted
relation
Template:
Acceptance criteria:
Empty
Date of First Response:
Visible to:
Matthew Harmon

 Description   

As an example of a certain Tab we want to hide from a content editor would be a Developer Tab, which would be intended for developers only.

In our modularized component environment, for example, this would allow us to create a developer only tab where we could add unique classes to a component. This would allow us to scope our CSS to affect each use of the same component differently on the same page.

At the moment, our idea of how we could potentially restrict which user has the ability to view a dialog field/tab or not, would be based on a permission role.  And a property can just be added to the field or tab to tell Magnolia if this should be visible to the user or not.



 Comments   
Comment by Christopher Zimmermann [ 05/Aug/19 ]

Thanks for the suggestion. The idea makes sense and could be valuable. I mark this ticket as accepted which means that we see the idea as valid, but there is no commitment or timeframe to implement the feature.

Comment by Christopher Zimmermann [ 23/Jun/20 ]

It could be possible to engineer a workaround with two dialogs. Have a default dialog which all users can see, and which is used as normal. Then have a 2nd dialog for the advanced users which is accessible via an additional Action in the actionbar. Actionbar items visibility can be configured based on role.

But I do not know the details of how this could be wired up.

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