Hi!
I just added a dynamic field on the Close window. Now, we would like to make that field mandatory depending on the service assigned to that ticket. Is that possible to do? If yes, how?
I would like to automatize different options in OTRS and i have doubts how i could do that using the OTRS 5.0.28 configuration. Maybe in newer versions there are new options to improve that topic?
Thank you!
DynamicField on Close window
Moderator: crythias
Re: DynamicField on Close window
Hi,
I would do a ACL hiding the close button as long as you have all needed values on the ticket.
regards
Flo
You can not do that. You can hide or show values via ACLs in the dropdown depending on the service, but not the field itself.I just added a dynamic field on the Close window. Now, we would like to make that field mandatory depending on the service assigned to that ticket. Is that possible to do? If yes, how?
I would do a ACL hiding the close button as long as you have all needed values on the ticket.
regards
Flo
OTRS 2025 SILVER (Prod)
OTRS 2025 auf Debian 12 (Test)
Znuny 7.x latest version testing auf Debian 12
-- Ich beantworte keine Forums-Fragen PN - No PN please
I won't answer to unfriendly users any more. A greeting and regards are just polite.
OTRS 2025 auf Debian 12 (Test)
Znuny 7.x latest version testing auf Debian 12
-- Ich beantworte keine Forums-Fragen PN - No PN please
I won't answer to unfriendly users any more. A greeting and regards are just polite.
Re: DynamicField on Close window
Thank you, sorry for dont let you know in advance.
That is not exactly what we are looking for , but still helpful for future needs
Regards,
David
That is not exactly what we are looking for , but still helpful for future needs
Regards,
David
Re: DynamicField on Close window
I will explain the workaround we did in case someone will find it useful.
We have created 2 different ACL´s related to that DynamicField. We added a new possible answer for that DF "N/A". So with one ACL we force to be "N/A" to all Services not "X" but for Services "X", there is not possible that "N/A", so that mandatory DF will be chosen from the 5 different options in order to fill the field and close the ticket! yeah
We have created 2 different ACL´s related to that DynamicField. We added a new possible answer for that DF "N/A". So with one ACL we force to be "N/A" to all Services not "X" but for Services "X", there is not possible that "N/A", so that mandatory DF will be chosen from the 5 different options in order to fill the field and close the ticket! yeah
