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.

Performance-related alerts are recorded in the ALERT log. This log contains entries for operations that exceed specified performance thresholds, providing insights into potential performance issues. References: Pega Platform Help - System Logs.

• A: Each rule in Pega can indeed have multiple guardrail warnings. These warnings indicate the degree to which the rule deviates from Pega's best practices.
• C: Pega Platform performs a guardrail examination when a rule is saved. This is to ensure that developers are immediately aware of any potential issues that may arise from the rule they are creating or modifying. References: Pega official documentation on compliance score and guardrails.

To create a custom status named Open-Review to be applied to assignments in one application, create a Field Value record named Open-Review for .pyStatusWork with the Apply To class set to the class group (A). This approach allows you to customize the status values used in your application and ensure that they are available for use in assignments within the specified class group, which typically corresponds to an application.References: Pega Community documentation on Field Value records and status values.

When a report is created in a class group (MyCo-HR-SelfService-Work), it will return instances of its child classes (MyCo-HR-SelfService-Work-TimeOff and MyCo-HR-SelfService-Work-Expense) unless those child classes are stored in different database tables due to class table inheritance or other data storage configurations. References: Pega official documentation on reporting and class groups.

A keyed data page is best used when a user selects a replacement part from a long list that seldom changes (B). Keyed data pages are designed to efficiently manage large amounts of data that do not change frequently by loading data specific to a key (like a part ID). This improves performance by caching the data and reducing the need to frequently query the source system for the same data.References: Pega Community documentation on data pages and caching strategies

The Purge/Archive wizard in Pega Platform is appropriately used to remove old cases to reduce the size of a database table (B). Over time, completed or resolved cases can accumulate in the system, leading to large table sizes that can negatively impact application performance. By archiving these cases, you can move them out of the primary database tables into an archive, and by purging, you can delete cases that are no longer needed. This process helps maintain optimal database performance and manage storage costs effectively.References: Pega Community documentation on the Purge/Archive wizard and database maintenance best practices.

Branched rulesets are used when multiple teams need to work on the same application version simultaneously. Each team can work in their own branch, allowing for concurrent development without affecting the main application until the branches are merged. References: Pega Platform Help - Branched Rulesets.

Pega best practices recommend keeping activities short to enhance maintainability and readability. Custom Java steps should be limited to reduce complexity and potential errors. Activities should also be limited in general, with preference given to other rule types that are more declarative and less procedural, like data transforms, to improve application performance and maintainability. References: Pega SSA course materials on activity best practices.

Generating report data based on several properties stored in the BLOB (Binary Large Object) can impact performance because it requires full database table scans. Using SQL query tools or activities to archive case data before purging tables can also negatively impact performance, as they may not be optimized for the Pega Platform's data structures. References: Pega Platform Help - Performance Best Practices.

An edit validate rule is used to ensure that data is entered in a specific format. For membership numbers that need to match a particular pattern (M-######-0#), an edit validate rule would be the appropriate mechanism to enforce this format upon entry. References: Pega Platform Help - Edit Validate.

No

YES

YES

NO

When considering post-processing actions on a flow action, it's crucial to understand their implications on the user experience and system behavior. The effect if the flow action is reloaded (A) is important because post-processing actions might not execute again, leading to inconsistent data or user experience. The sequence in which the system runs different actions (B) is critical to ensure that data transformations and business logic are applied in the correct order, maintaining data integrity and consistency. The timing of the commit for the flow action (C) influences transaction management, ensuring that all changes are saved correctly and that the system maintains data consistency, especially in multi-user environments.References: Pega Community documentation on flow actions and post-processing.

To support offline use of applications on mobile devices, you should source UI elements such as drop-down lists using data pages, which can be configured to be available offline. This allows the application to use locally cached data to populate the UI elements even when the device is not connected to a network. References: Pega Mobile Developer Guide on offline capabilities.

Dedicating and classifying a node for the job scheduler allows the job scheduler to run on a node that is optimized for batch processing. This ensures that resource-intensive jobs do not impact the performance of the user nodes, thus maintaining peak performance at all hours. References: Pega Platform Help - Job Schedulers.

• A: Calling the function pega.web.api.doAction() allows for specific actions to be performed in the Pega application from the web mashup, such as refreshing a section or submitting an assignment.
• D: Using the attribute data-pega-event-onpagedata allows for passing data from the web mashup to the Pega application when specific events occur on the page. References: Pega official documentation on Pega Web Mashup methods and attributes.

Rule resolution will choose the rule that is most specific to the circumstances of the case. Since the country is set to Japan, the rule resolution algorithm will choose the rule version that is circumstanced for Japan. Among the options, 01-01-02 is the circumstanced rule that matches the country condition of Japan and would be selected over the base rule and any other versions. References: Pega Platform Help - Rule Resolution.

Adding a footer to the Case Manager portal can be done by updating the skin that's applied to the portal. Skins in Pega define the look-and-feel of user interfaces, including headers, footers, and other elements. References: Pega Platform Help - Skins.

The assignment urgency 6.5 hours after the case reaches the assignment with the given SLA configuration would be 95 (B). Here's the calculation: The initial urgency is 20. The case reaches the goal after 5 hours, adding 10 to the urgency, making it 30. Since the deadline is at 2 hours and has been exceeded by 4.5 hours, the urgency increases by 25, making it 55. Now, with the passed deadline events occurring every hour and increasing urgency by 5, after 1.5 hours, this would occur 1 additional time (since it's half an hour into the next hour), adding 5 to the urgency. Therefore, the total urgency after 6.5 hours is 20 (initial) + 10 (goal) + 25 (deadline) + 5 (passed deadline event) = 60. However, since the deadline urgency increase occurs at the 2-hour mark, the urgency would be 20 + 25 = 45 at 2 hours, and then after reaching the goal at 5 hours, additional 10 is added, making it 55, and then one passed deadline event adds 5 more, making the total 60. Since the deadline urgency is already accounted for at the 2-hour mark, it should not be added again after the goal. Therefore, the correct total urgency would be 20 (initial) + 10 (goal) + 25 (deadline) + 40 (8 passed deadline events) = 95.References: Pega Community documentation on SLAs and urgency calculation.

You should consider using a field value when the list of allowed values is mostly static. Field values are best used for properties with values that do not change often and need to be reused throughout the application. References: Pega official documentation on field values.

To ensure that only a manager can run a specific flow action, the best approach is to add a privilege to the flow action form (B) and then assign this privilege to a role that is exclusive to managers. This role is then associated with the access group designated for managers. Privileges provide a granular level of security that can be used to control access to specific actions within a Pega application, such as executing a flow action. By leveraging privileges, you can ensure that only users with the manager role, who possess the necessary privilege, can execute the flow action, thereby enforcing the desired level of access control.References: Pega Community documentation on privileges, roles, and access groups.

Sixteen hours after the case reaches the assignment, the assignment urgency is calculated as follows: Initial urgency (20) + Urgency after goal (10) + Urgency after deadline (20) + Urgency after passing the deadline (2 hours passed, urgency increases by 20, and this event repeats for the limit of 5 times, so 20x5=100). Adding these together: 20 + 10 + 20 + 100 = 150. However, since none of the options matches this calculation, there might be an error in the given options or a misinterpretation of the question. Based on the provided options, 90 would be the closest, indicating a possible oversight in the question. References: Pega official documentation on Service Level Agreements (SLAs) and urgency calculations.

Building mobile applications with Pega Platform, it's true that the Pega Mobile Build Server is configured in Dev Studio using your Android or iOS developer certificates (B). This server is a cloud-based service provided by Pega to facilitate the mobile app build process. It's also true that the Pega Mobile Build Server requires HTTPS access (D) to ensure secure communication during the build process.References: Pega Community documentation on mobile app development and Pega Mobile Build Server configuration.

Rule resolution in Pega follows the "Rule Resolution" algorithm, which will look for the rule that best matches the class hierarchy and the ruleset list. In this scenario, the rule that matches the Apply to: class of TGB-HR-SelfService-Work-TimeOff and is in the highest listed ruleset that is available (SelfService) will be selected. References: Pega SSA course materials on rule resolution.

To prevent horizontal scrolling on mobile devices, setting the importance of columns allows for the most critical information to be shown first, potentially hiding less important columns on smaller screens. Using percentage widths for layouts ensures that the layout adapts to the screen width, which can also help prevent horizontal scrolling. References: Pega UI design best practices for mobile devices.

Withdrawing the circumstanced rules in the AccountOpen class is the correct action to stop using a circumstanced rule. This allows the non-circumstanced (or base) rule to be used instead without affecting other circumstanced versions of the rule for different case types. References: Pega Platform Help - Withdrawing a rule.

Keyed data pages can return multiple embedded pages if the data structure includes lists or other page structures. They can also have multiple keys, which allows them to return data based on a combination of key values. References: Pega Platform Help - Data Pages.

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.

To send information to an external system of record using a connector, you would typically reference a connector from within a data transform. The data transform can manipulate the data as needed before it is sent out through the connector. References: Pega Platform Help - Connectors.

Since the MSDS rarely changes, a keyed data page that allows multiple pages for each key is the most efficient. This configuration enables the data page to hold the MSDS for each product, identified by a unique key (e.g., the product ID), in memory for quick retrieval without the need to reload the data frequently. References: Pega Platform Help - Data Pages.

The correct configuration for two parallel cases that run independently is the Subprocess shape with the Spinoff flow option enabled (Option C). This allows the Retirement planning case to proceed in parallel without waiting for, or reporting to, the Account review case. References: Pega official documentation on case design and flow shapes.

• A: When using a Pega Web Mashup, leveraging the standard authentication service IACAuthentication and updating the authentication activities to match the external system's requirements is a common practice.
• D: Configuring application permissions by specifying a list of trusted domains in the application rule is important for security purposes and to control which external domains are allowed to embed the mashup. References: Pega official documentation on Pega Web Mashup configuration.

To copy items selected by a user to a page list property when the user submits the form, add a data transform to the flow action as a post-processing action (A). Post-processing actions occur after the user submits the form, making it the right moment to transfer the selected items into the page list property for further processing or storage.References: Pega Community documentation on data transforms and flow action post-processing.

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.

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.

System exceptions and errors are typically logged in the Pega log. This log captures information about the functioning of the Pega platform and the applications running on it, including system errors and exceptions that users encounter. References: Pega System Administration documentation on log files.

To support accessibility, it's recommended to use a calendar control that displays an entire month. This allows users who rely on screen readers or keyboard navigation to select a date without the need for precise mouse control or having to manually input the date, which can be error-prone. References: Pega User Interface Design Guide - Accessibility.

The Static Assembler is a Pega tool used to address rules assembly issues specifically when the server is managing a large number of rules caches. By pre-assembling rules into a static content, the Static Assembler helps in improving performance in situations where cache management becomes complex due to the volume of rules. It creates a set of static files that represents the assembled rules, which can reduce the overhead on the server during rule assembly and cache management. References: Pega official documentation on performance tools and best practices.