24.1 : Use New Drop-Down and Auto-Complete Lists

Hi Etienne,

In 24.1 for "Use New Drop-Down and Auto-Complete Lists" toggle we noticed that the validations change is inconsistent. Is there a rule that system uses to convert existing auto-complete list to new drop down?

It would be great if we know the rule/ logic the system uses to flip the existing auto-complete list to new drop down. 

When we turned this feature on, the behavior is different for some auto-complete lists and there is no detail around the toggle feature.

Any detail will be really helpful.

Tags:

  • Suggested Answer

    0  

    Hi Urva,

    Turning on the feature toggle will only impact DDL and ACL fields on the following pages: Request Details, Project Details and Program Details. In other pages, the auto-complete and dropdown will remain as before.

     The components covered include:

    - Drop-Down list component

    - Autocomplete list which validated by SQL-Custom without filter or field dependencies defined (when no token is used in the SQL)

    - Autocomplete list which validated by List without filter or field dependencies defined (when no token is used in the SQL)

    - Autocomplete list which validated by SQL-User without filter or field dependencies defined (when no token is used in the SQL)

     

    Please note these changes and limitations in the new searchable dropdown that will replace ACL and DDL:

    • If there are more than 50 records in the list, user will see the first 50 records in the list. Users can use in-box search to retrieve and select additional values.
    • For multiselect ACL, user cannot order the values in the selected list like in the old ACL popup.

    We will update the PPM documentation shortly to add this information, thanks for bringing this up to our attention.

  • 0 in reply to   

    Hi Etienne,

    Thank you for the update, this is really helpful. 

    The new dropdown is an interesting feature and can be more of use if the admins have the ability chose  individual validations where this needs to be enabled. The reason I say this, we noticed validations with multiple columns also convert to "new dropdown" and eliminating other useful columns. I will submit ER to have this addressed in near term if possible.

    E.g. 

    Current Format:

    New Format :

  • 0   in reply to 

    You're preaching to the choir here - during our demo meeeting I told the team in charge of this feature that it should be configurable per-validation instead of a global setting. However, due to limited bandwidth and closing release deadline, they went for the global setting.

    I did forward your idea to them and did upvote your idea - I'll share any update in the idea thread. Thanks a lot for your valuable feedback!