we have recently upgraded to CA service catalog 14.1.
we need to display 30000 values in drop down, please let us know your views.
my view: creating a table with 30000 rows, and extracting the information from the backend through query.
if we do like this, if there is any performance issue?
Thanks in advance.
Awaiting your reply.
Hi Santhosh - I am not a well-versed catalog person, but from my experience in Service Desk Manager, I would say that yes, with a dropdown that large, there is a fairly big risk of performance issues being caused by that large of a back-fill query for a dropdown.
Hope this helps,
Can you explain us the business case to have a dropdown with 30000 values?
Looks like a user will not be available to read each value to make his choice. It will rather write the beginning of what he wants and then choose an option.
Here is what we have done for our automated Exchange mailing list service.
The textbox "Find a mailing list" triggers a plugin that search in ldap for security groups associated with an Exchange mailing list.