Martyn Houghton Posted September 6 Posted September 6 We are increasingly using Simple List as a critical element of Enterprise Service Management workflows to validate and implement integration where accuracy is key in passing information between systems. Over time the values in the Simple List change, however to retain the data integrity of the requests raised with the historical information and ensure the display of information in parts of the system such as the 'Details' form remains, this enhancement is for the addition of a 'Historic' flag to list items, which has a simple function of not displaying the item in a drop-down list dialog (i.e. can no longer be selected) but is still present in the simple list for display purposes. Cheers Martyn
Bob Dickinson Posted September 6 Posted September 6 Hi @Martyn Houghton I can see the scenario you are referring to here and how it may look like data is missing/not populated from a UI perspective despite the fact the data exists against the record in the DB. We will discuss this internally. Kind regards Bob
Gerry Posted September 6 Posted September 6 @Martyn Houghton I don't know I am 100% right here, but simple lists are effectively a list of keys/values. I expect, in some places where we use them, I presume we store the key, and not the value, needing a lookup in order to display the value. Adding a "historic" flag to the simple lists does not sound like the correct solution as simple lists are used in a number of places, some of which would not make use of this. Which part of Hornbill specifically are you referring to? Its likely that the correct solution would be to use the Simple List as a lookup to aid in input accuracy, but to then store the key AND value (by which I mean that value AND display value), or even just the Value, if thats the bit thats important. Of course, there is also the issue of language translation, so this might be another consideration. If we know which part of the application you are refferring to we can get the right dev team to take a look at the requirement. Gerry
Martyn Houghton Posted September 10 Author Posted September 10 @Gerry We use it quite commonly use these in custom fields which are shown as part of the Details section of a request with a linked simple list, for example, version number. If the list item is removed from the Simple List the details form will not display anything for that as no value is returned as the Display Value as the list item no longer exists. Cheers Martyn
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now