Hello,
(Version: OTRS 6)
My users are requesting the creation of more and more dynamic fields.
I am wondering what is the number of dynamic fields that should be considered reasonably as a maximum.
For example, is it considered reasonable and workable to have more than 200 different dynamic fields defined in the system?
Thanks
Maximum reasonable number of dynamic fields
Moderator: crythias
-
- Znuny wizard
- Posts: 380
- Joined: 20 Sep 2010, 16:54
- Znuny Version: OTRS 6 CE
- Real Name: Alexey Yusov
- Company: Radiant System Group s.r.o
- Location: Prague
- Contact:
Re: Maximum reasonable number of dynamic fields
Hello,
There are no limitations for dynamic fields. You should consider only process and administration usabilty reasons
There are no limitations for dynamic fields. You should consider only process and administration usabilty reasons
Alexey Yusov
Production: OTRS CE ITSM 6.0.28 on CentOS 7 + Apache 2.4 + MariaDB 10.4.13 + Radiant Customer Portal
Radiant System OTRS Intergrator
RS4OTRS marketplace
Stay tuned on our Facebook
((OTRS)) Community Edition - what next?
Production: OTRS CE ITSM 6.0.28 on CentOS 7 + Apache 2.4 + MariaDB 10.4.13 + Radiant Customer Portal
Radiant System OTRS Intergrator
RS4OTRS marketplace
Stay tuned on our Facebook
((OTRS)) Community Edition - what next?
-
- Znuny superhero
- Posts: 890
- Joined: 15 Dec 2016, 15:13
- Znuny Version: All
- Real Name: Emin
- Company: Efflux GmbH
- Contact:
Re: Maximum reasonable number of dynamic fields
Hey,
Technically, as Alexey mentioned, that's no problem.
The only problem I see is the user experience of the users when they see all dynamic fields in ticket creation form.
You should get an add-on that will hide/show dynamic fields based on other fields (for example queue, ticket types etc.).
— Emin
Technically, as Alexey mentioned, that's no problem.
The only problem I see is the user experience of the users when they see all dynamic fields in ticket creation form.
You should get an add-on that will hide/show dynamic fields based on other fields (for example queue, ticket types etc.).
— Emin
Professional OTRS, Znuny & OTOBO services: efflux.de | efflux.de/en/
Free and premium add-ons: German | English
Free and premium add-ons: German | English
-
- Znuny guru
- Posts: 5018
- Joined: 13 Mar 2011, 09:54
- Znuny Version: 6.0.x
- Real Name: Renée Bäcker
- Company: Perl-Services.de
- Contact:
Re: Maximum reasonable number of dynamic fields
Maybe that's the right time to use the "Process Management" to define different forms for different "types" of tickets. So users that have e-mail problems see an other form to create a ticket than users that have printer problems...
Perl / Znuny development: http://perl-services.de
Free Znuny add ons from the community: http://opar.perl-services.de
Commercial add ons: http://feature-addons.de
Free Znuny add ons from the community: http://opar.perl-services.de
Commercial add ons: http://feature-addons.de