Idea ID: 1625874

Allow Lists of more than 20 items

Status : Delivered
over 3 years ago

Briefly describe your idea
Provide ability to create Lists (that are not created from an Offering) of more than 20 items

Why is this important, when would it be used
Allow greater flexibility in creating structured data for users to select from.

If you were designing the solution, how would you do it?
Allow lists of up to 200 entries (or possibly even greater)


  • Great news, this idea has been accepted on our product roadmap, timing TBD. Check back for updates. (This is not a formal commitment, and submit to change)

  • solution design:  allow for the administrator to create a look up table, with a name/value pair (and susequently localization capabilities); and turn that lookup table into a list item that can be used/placed on forms. there are probably other metadata for the table and each name/value pair needed...

    additoinal capabilities could be to allow the population of hte list to be dynamic, based upon a query. from an existing table (or from one of the 'lookup tables' i meantioned).  Combined with the additional metadata from my previous paragraph, this would allow for one lookup table to be used for multiple purposes, or the same purpose, but with a different slice of the same dataset.

    for instance; a lookup table for "deployment type"; may contain the following name/values:
    Rollng Update/rolling .     (metadata attribute: nocolor)
    Replacement/replace       (metadata attribute: nocolor)
    Canary Bird/canary          (metadata attribute: nocolor)
    Blue Green/bluegreen .   (metadata attribute: color)
    Red Black/redblack .        (metadata attribute: color)

    Then the adminstrator could create 2 dynamic lists: one list that contains colors, and one that doesnt contain colors; the change management forms could then be configured to use the colored list for services that leverage container based technologies, while the non-colored list could be used for traditional deployment models.


    hopefully that makes sense.

  • Thank you for sharing your idea! Let’s hear what the community has to say. Once there is enough community traction, it will be reviewed by the product team.