PEGACPSA23V1 Exam Dumps : Certified Pega System Architect

When building a form that involves selecting multiple items, such as courses for enrollment:

B. Create a field group list property and make the property a data reference. This step is essential for defining a structured property that can hold multiple course records, which users can select. Setting it as a data reference allows the property to dynamically pull in course data from an external source or data page.

D. Edit the field group list property and set data access to copy data from a data page. This configuration ensures that the course data available for selection is current and accurately reflects the offerings stored in a data page, facilitating accurate and up-to-date selections by users.

For the use case where a library application displays a read-only list of outstanding past-due books to staff during the book request case process, the appropriate Data Page configuration needs to ensure the data is accessible and specific to each user session without the possibility of modification.

• D. List, Readonly, Requestor: This configuration is optimal for the described scenario. A 'List' type is suitable because it involves displaying multiple records (outstanding books). 'Readonly' ensures that the data cannot be altered during the process, maintaining the integrity of the information displayed. The 'Requestor' scope is chosen because the information needs to be specific to the user session, providing a personalized reminder for the staff member to notify the member about their past-due books.

Options involving 'Page' (B, C, E) are not suitable as they are designed for single records rather than lists. 'Editable' (B, E) permissions are unnecessary and potentially problematic for this use case since the data should not be modified. 'Node' scope (F) would not provide the user-specific session data needed for this functionality.

Correspondence in Pega typically involves automated communication mechanisms within workflows:

D. Email the case worker when the insurance claim is routed to their worklist. This requirement clearly demonstrates the need for configuring correspondence to automate the process of notifying case workers via email when certain events occur, such as routing an insurance claim to their worklist. This ensures timely and effective communication within the case management process.