Re: Forms Designer - Value List vs Display List (136 Views)
Reply
Frequent Advisor
tony kelman-smith
Posts: 55
Registered: ‎07-31-2007
Message 1 of 3 (139 Views)
Accepted Solution

Forms Designer - Value List vs Display List

We're currently revising the list of Incident Status and I've updated the table pmstatus, which has updated $G.user.pm.status and now I want to update the IM forms

 

My question is around when to use Value List and Display List

 

IM.open.incident uses Value List and calls $G,user.pm.status

IM.update.incident use Display List with the status set out as string (e.g. Assigned;Open;Work In Progress;   etc)

 

Is there any benefit or deteriment of using one over the other ?

 

Thanks,

Tony

Please use plain text.
Honored Contributor
John Stagaman
Posts: 3,099
Registered: ‎07-13-2007
Message 2 of 3 (136 Views)

Re: Forms Designer - Value List vs Display List

[ Edited ]

The advantage of using a global list instead of a hard-coded list in the form:

  • Change once, change everywhere. With hard coded combo boxes, you have to fix the values on each format.
  • if you need to support localization, it's designed to work with global lists.

As to value list/display list:

 

If there isn't a difference between the value list and display list, you can populate only one of the values on the form (there is no need to populate both). I usually use the value list, but you can use either the value list OR the display list. SM will accept whatever value is selected.

----------------------------------------------------
Kudos - what, where, how, and why
Want Good Answers? Ask Good Questions...
Please use plain text.
Frequent Advisor
tony kelman-smith
Posts: 55
Registered: ‎07-31-2007
Message 3 of 3 (104 Views)

Re: Forms Designer - Value List vs Display List

Thanks very much John.  Just what I needed to know

Please use plain text.
The opinions expressed above are the personal opinions of the authors, not of HP. By using this site, you accept the Terms of Use and Rules of Participation