Hi there,
I am struggeling around with defining a dynamic field (dropdown) to be mandatory for specific roles only. So end users in specific roles are required to set a value and to clarify it before moving on with the ticket. But I have other roles, who shall not be enforced to set the value, since they cannot know that detail.
The idea was to use a ACL for that but I could not find a solution so far. Are there any advices?
My first approach was to define the dynamic field via Screens to be mandatory, but to reduce the mandatory to optional for specific roles
The second approach was to define dynamic field via Screens to be optional, and to enforce this field to be mandatory to specific roles
Both approaches would be okay for me, but sadly on both paths I end up with a issue in defining the ACL accordingly.
I found this viewtopic.php?t=39162 but i could not reproduce it on my end.
Is that even possible?
best wishes
I am struggeling around with defining a dynamic field (dropdown) to be mandatory for specific roles only. So end users in specific roles are required to set a value and to clarify it before moving on with the ticket. But I have other roles, who shall not be enforced to set the value, since they cannot know that detail.
The idea was to use a ACL for that but I could not find a solution so far. Are there any advices?
My first approach was to define the dynamic field via Screens to be mandatory, but to reduce the mandatory to optional for specific roles
The second approach was to define dynamic field via Screens to be optional, and to enforce this field to be mandatory to specific roles
Both approaches would be okay for me, but sadly on both paths I end up with a issue in defining the ACL accordingly.
I found this viewtopic.php?t=39162 but i could not reproduce it on my end.
Is that even possible?
best wishes
Statistics: Posted by hkais — 22 May 2024, 12:39 — Replies 0 — Views 11