Design Best Practice: 1,000 values names in Value List Field
The business requirements is requesting us to is creating new value list field, with over 1,000 value items list with Values Popup Display Control.
We know this is not best approach, we are suggesting for alternative solution: have ODA with record values.
We need prove with the business that large data set of value items in Value List field could impact the slow loading performance. Is this possible for you to give more details why it is causing Archer performance to slow and what are the impacts?
- Community Thread
- Forum Thread
- RSA Archer
- RSA Archer Suite
- Value List
- value name
While Archer can do this, it isn't a good idea, as you note. You could easily demonstrate this by creating a test field and loading with 1K values. Using real values would be best.
Pointing out the margin of error for mis-clicking on the wrong values option, and then reloading the list, and not being able to search for an option will highlight the UI problems.
Likewise, using an ODA nearly eliminates these problems, allows for search, allows for cleaner updates and allows for some fun xref reports.
Regarding "why it's slow"... Any system trying to load this type of data in this manner will have a similar problem. I'm sure doing a validated lookup list in Excel will hiccup, as well, regardless of how fast a nice, new Dell machine you have. 🙂
Is this possible for you to give more details why it is causing Archer performance to slow and what are the impacts?
With that many values the performance issues can be any number of things. Mainly the browser has to load all those values into the browser along with everything else the application has to offer like other values lists, cross-reference/related record data, rules and associated actions.
From an Archer perspective, is the environment sized properly?
RSA Archer 6.6 Platform Planning Guide