PEGACPSA23V1 Exam Dumps : Certified Pega System Architect

• Customer information: This usually pertains to session-specific data that is relevant to the current user, such as user ID and locale. In Pega, this type of information is typically stored in user pages, which are clipboard pages that contain data related to the current user of the application. User pages are created for each session and include data that pertains to that particular user.
• Previous orders: These are typically a list of orders that are not specific to a session but need to be readily accessible and possibly shared across multiple sessions or users. In Pega, this kind of information is best stored in data pages. Data pages are used to hold data that is loaded once and can be used by multiple users, cases, or processes. They are efficient for data that doesn't change often and is required to be accessed frequently, such as a list of previous orders.
• Current order: This refers to the specific details of the order the customer is currently placing. It is specific to the user's current session and the case they are working on. Therefore, it should be stored in user pages, which are specific to an individual user session and can manage data related to the work they are currently performing.

References:

• Pega's official documentation on Clipboard and Clipboard pages explains how data is categorized and managed within the application.
• Training materials from Pega Academy, which go into detail on the types of clipboard pages and their uses within a Pega application.

You would typically use a field value in Pega when the list of allowed values is:

B. Mostly static. Field values are best used for lists of allowed values that do not change frequently. They enable the use of predefined, constant values across the application, providing consistent data references for fields that have a set list of options.

To localize correspondence into a language not provided by the Pega language pack:

C. Create the Translation rule manually and include the rule in the application ruleset. When a specific language pack is unavailable, manually creating a Translation rule allows for custom translations to be added to the system. This rule should be included in the application ruleset to ensure it is applied throughout the application, catering to the specific language needs.