In Application Settings, you can specify different values for production levels using text (e.g., URLs, file paths) or picklists (for selecting from predefined options). These settings allow for easy adjustment of values according to the environment the application is running in. References: Pega Platform Help - Application Settings.

No

YES

YES

NO

When integrating multiple Pega Web Mashups into a single page, it is necessary to identify unique names for each mashup to ensure that they are embedded and function independently without conflict on the client ' s page. References: Pega Platform Help - Pega Web Mashup.

To ensure that the advisor and the student can simultaneously edit the draft proposal, configure the locking on the case type to allow multiple users (B). This setting enables a shared access model, where multiple users can work on the case at the same time. Additionally, Pega ' s conflict resolution mechanisms can be utilized to check for changes before committing them to the database, ensuring that any concurrent edits are properly managed and the integrity of the proposal is maintained. References: Pega Community documentation on case locking and concurrent editing.

For each scenario, the appropriate mobile application solution is as follows:

" SDK application " is suitable for Globobank ' s scenario because they want to build a mobile app of its Pega Platform application to embed in its mobile app. The SDK would allow them to integrate Pega ' s capabilities within their existing mobile application environment.

" Signed application " is needed for Metrobank, which wants to distribute their mobile app on Android and iOS app stores. For an application to be accepted on these platforms, it must be properly signed with a developer certificate.

" Unsigned application " fits the scenario for Localbank, as they want to build a mobile app for a Pega Platform application but cannot distribute developer certificates to app developers. An unsigned application does not require these certificates, allowing development to proceed without them.

Based on these explanations, here are the matched solutions:

SDK application - > Globobank wants to build a mobile app of its Pega Platform application to embed in its mobile app.

Signed application - > Metrobank wants to build a mobile app for distribution on Android and iOS app stores.

Unsigned application - > Localbank wants to build a mobile app for a Pega Platform application, but developer certificates cannot be distributed to app developers.

Managing encrypted data in Pega Platform comes with certain limitations, one of which is that encrypted properties cannot be referenced using filter conditions in reports (A). This is because the encryption obscures the actual value of the property, making it impossible for the reporting engine to perform comparisons or filtering based on the encrypted data. This limitation is essential for maintaining data security, as it prevents unauthorized access to sensitive information through report queries. References: Pega Community documentation on encryption and reporting.

The two most common ways to expose your application to an external system are to leverage the Pega API (B) and to create a web service with the Service wizard (D). The Pega API provides a set of out-of-the-box RESTful endpoints for performing operations within the Pega Platform. The Service wizard simplifies the creation of SOAP or REST services, enabling external systems to interact with Pega applications. References: Pega Community documentation on Pega API and Service wizard.

Creating a new ruleset version for each team ensures that each team ' s work is isolated within a specific version, preventing overlap and conflict. Setting up a branch ruleset for each team further isolates development work, allowing parallel development streams that can later be merged back into the main application ruleset. These two options, when used together, provide the most flexibility for teams working on separate enhancements with uncertain release dates. References: Pega Platform Help - Branch Rulesets.

The initial urgency is set at 20. At 5 hours, the urgency increases by 10 (total 30). At 8 hours, the urgency increases by 20 (total 50). After the deadline, the urgency increases by 20 every 2 hours, up to a limit of 5 events. By 16 hours, all 5 events have occurred, adding 100 to the urgency, leading to a total urgency of 150 (initial 20 + goal 10 + deadline 20 + passed deadline 100). References: Pega Platform Help - Service Level Agreements.

Controlling access to an attachment category can be achieved through various configurations. Using a When condition like " IsCurrentStageTesting " (A) allows for dynamic access control based on the case ' s current stage, enabling attachments to be accessible only under certain conditions. Assigning privileges, such as " DeleteOwn " (C), to users enables fine-grained control over actions users can perform on attachments, such as deleting their own attachments, thus enhancing security and compliance with business rules. References: Pega Community documentation on attachment categories and access control.