Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

Dropdown funtionality issue



There is a dropdown control which is sourced from a clipboard page referencing a custom list. This custom list can be dynamically changed in production.
If a value is selected from a dropdown by a user, and that value is removed before the form is submitted, an error is not thrown. Instead, the first value on the new list is selected and no notification is sent to the user.

Error Messages

Not Applicable

Steps to Reproduce

1. Create a dropdown control in a section.
2. Create an activity to copy the data in a clipboard page and refer this clipboard as a source to the dropdown.
3. Refer the section in a flow action and then in a flow.
4. In the flow, select an option from the dropdown and submit it to route it to a different assignment.

Root Cause

​This is an expected behavior. When user does not delete the value in the first assignment, it is seen in second assignment.
But, if user deletes the value in the second assignment, the source is reloaded and it is unable to find the value which was set before.
Hence, it selects the first value in the list of the dropdown.

There is no validation set, hence no error is thrown. 


Create a custom validation rule to fire an error message when value is not found. ​Or, Include a place holder in the dropdown so that no value is pre-selected.
Suggest Edit

Published September 23, 2015 - Updated October 8, 2020

Did you find this content helpful? Yes No

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us