Skip to main content

Data access in UI controls

Applications often use lists to manage user input. Populating list values from a data source — rather than embedding list values in a property definition — improves application maintenance by avoiding the need to rerelease an application when the list values change. For example, a financial services company can provide a user with a list of cities with branch offices when scheduling an appointment with a financial advisor. The entries in the list update whenever branch locations are added to or removed from the data source.

Cascaded drop downs

When you populate a list with data from a Data Page, only the selected value is copied to the Data Model of a Case. The value copied to the Case does not need to match the value displayed in the list. For example, a drop-down contains a list of country names. When the user selects a country, the application can copy the country code, rather than the country name, to the Case.

list-source

When you populate a list with data from a Data Page, the items in the list update according to the refresh strategy specified on the Data Page. If the Data Page accepts a parameter, Pega Platform™ creates a Data Page instance each time the parameter changes, updating the list contents.

Check your knowledge with the following interaction:


This Topic is available in the following Module:

If you are having problems with your training, please review the Pega Academy Support FAQs.

Este conteúdo foi útil?

Quer nos ajudar a melhorar esse conteúdo?

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

Pega Academy 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