To address the complaints from customers and prospects about receiving irrelevant offers and products, the following two Pega solutions can be implemented:

Pega Marketing: This solution helps in creating personalized marketing campaigns. By leveraging predictive analytics and customer data, it ensures that the marketing efforts are relevant and targeted. This reduces the chances of customers receiving irrelevant offers.

Customer Decision Hub: This hub centralizes the decision-making process by using real-time data and analytics to personalize interactions with customers. It helps in understanding customer needs and preferences better, thus preventing the delivery of irrelevant offers.

References:

Pega Marketing Overview

Customer Decision Hub

 Ensuring Quality with Automated Testing:

Automated testing programmatically ensures the quality of rules, maintaining the integrity of the CI/CD pipeline. This is crucial for consistent and reliable deployments.

 References:

Pega Lead System Architect documentation emphasizes the importance of automated testing in CI/CD models to ensure rule quality and pipeline integrity.

 Therefore, the correct answer is:

B. Automated testing programmatically ensures quality of rules to maintain the integrity of the pipeline.

 Edit Input Rule: Create an Edit input rule on the customerinfo property. This rule will automatically convert the first and last names to upper case when the data is entered or updated, ensuring consistency.

 Data Transform: Develop a post-processing Data Transform that converts the names to upper case. This Data Transform can be invoked in the flow action to ensure that the names are converted after the user submits the form.

References:

Pega Academy: Configuring Data Transforms and Edit Input Rules

Pega Documentation: Data Transform Rules

To ensure the host system origin is trusted in a Pega web mashup implementation:

In the authentication service JNDI binding parameters, specify the protocol, host, and port (Answer A):

Explanation: Specifying these parameters ensures that the Pega system recognizes and trusts the origin of the mashup requests.

When deciding between using a Wait shape or an assignment with an SLA in a Pega case flow:

Assignment with SLA (C):

An assignment with an SLA is preferred when there is a requirement to adjust the case urgency at the time of assignment creation. SLAs allow you to specify goals, deadlines, and escalation actions that can modify the urgency of the case.

This approach is suitable when you need to ensure that the case is handled within a certain timeframe and that the urgency can dynamically change based on business rules.

References:

Pega Case Management Best Practices

Pega SLA Configuration Guide

 Page List vs. Page Group: In Pega, a Page List is an ordered collection of pages indexed by position (e.g., 1, 2, 3). A Page Group, on the other hand, is an unordered collection of pages indexed by a string value (e.g., "CompanyA", "CompanyB").

 Sorting Requirement: Since the requirement specifies that the list must be sorted by company stock ticker, a Page List is more appropriate because it allows for sorting and ordered iteration.

 Implementation: Use a Data Transform or an activity to populate and sort the Page List. You can use Pega's built-in sorting functions to order the list by the stock ticker.

References:

Pega Academy: Data Management with Page Lists and Page Groups

Pega Documentation: Working with Collections

Queue Processors in Pega: Queue processors are responsible for asynchronous processing of queued tasks. They can be configured to run on different types of nodes.

Types of Nodes:

Web user nodes: Handle user requests.

Real-time nodes: Handle real-time processing tasks.

Background nodes: Handle background processes such as agents and queue processors.

Stream nodes: Handle stream processing and Kafka services.

Potential Root Cause: If a queue processor is not running, it is likely due to an issue with the node type that handles background processes, which are the background nodes. If the background node is down, the queue processor will not function properly.

References:

Pega documentation on node types and their functions.

Pega Platform 8.x help files related to queue processors and background processing.

Max Attempts: The maximum number of retry attempts set is 4.

Initial Delay: The initial delay before the first retry attempt is 2 minutes.

Delay Factor: The delay factor is set to 2, which means the delay doubles with each retry.

Calculating Delays:

First attempt fails, delay before second attempt = Initial delay = 2 minutes.

Second attempt fails, delay before third attempt = Initial delay * Delay factor = 2 minutes * 2 = 4 minutes.

Third attempt fails, delay before fourth attempt = 4 minutes * Delay factor = 4 minutes * 2 = 8 minutes.

Delay Between Attempts: The question specifically asks for the delay between the second and third attempt, which is calculated as 8 minutes.

References:

Pega documentation on queue processor configuration.

Pega Platform 8.x help files related to processing retries and delay factors.

 Automated Pega Unit Tests:

Having new team members create and run automated Pega unit tests against their rules ensures that they adhere to best practices and catch errors early.

 Rule Check-In Approval Process:

Using the rule check-in approval process allows for a review of changes made by new team members, ensuring that all rules meet the required standards and best practices.

 References:

Pega best practices for rule management and team collaboration recommend these approaches to maintain code quality and adherence to standards.

 Therefore, the correct answers are:

A. Have new team members create and run automated Pega unit tests against their rules.

C. Use the rule check-in approval process to review the changes that the new team members make.

Handling reference data from external systems efficiently is crucial to minimize system resource usage.

Use the System of Record (SOR) data access pattern to populate the page contents (Answer C):

Explanation: The SOR pattern ensures that the application fetches data directly from the external system when needed, rather than storing and maintaining copies of the data. This approach minimizes memory usage and keeps the data up-to-date.

To configure a data page that accepts either a postal code or a city name as a parameter and calls the appropriate REST connector:

Use separate REST connectors for each parameter type and a when rule to determine which connector to use based on the input parameter.

Alternatively, use an activity to evaluate the parameter and dynamically select the appropriate REST connector at runtime.

To define Authentication Service data instances in Pega, the following rule types are used:

Data pages: Used to retrieve and store authentication-related data.

Activities: Perform operations such as authentication logic and integration with external systems.

Data transforms: Used to map and transform authentication data.

References:

Defining Authentication Services in Pega

When defining a report that shows detail about each product associated within a given order case, you need to optimize the detail properties for the product in the product class. This is because the detailed information about the products is inherently part of the product class. By optimizing these properties in the product class, you ensure that the report can directly reference the necessary details without needing additional lookups or joins, thus improving performance and report accuracy.

Single Advanced Agent Configuration:

Create a single advanced agent and configure its schedule based on the server's local time zone.

Modify Agent Schedule:

For the Eastern US server, set the agent schedule to the Eastern US time zone.

For the India server, adjust the agent schedule to the India time zone.

Time Synchronization:

Ensure that both servers' clocks are synchronized using a standard time protocol to maintain consistent execution times.

When designing a solution that requires customer data from multiple external systems and ensuring it is as current as possible, consider the following:

Parallel Data Loading: Use the Load-Data Page and Connect-Wait methods to load the data in parallel. This approach improves performance by reducing the time taken to gather the required customer data since multiple data sources are queried simultaneously.

System of Record (SOR) Pattern: Employ the System of Record (SOR) data access pattern to fetch the most current customer data from the external systems directly. This ensures that the data used is up-to-date and reflects the latest information available from the source systems.

References: Pega Platform documentation on data pages, Connect-Wait methods, and data access patterns.

Aggregation components in a decision strategy are used to:

Perform Calculations:

Aggregation components are designed to calculate values based on a list of actions or records.

Examples include summing up totals, calculating averages, or other statistical measures.

Use Cases:

Commonly used to aggregate customer interaction data, such as total purchases, average spend, etc.

Strategy Implementation:

Place the Aggregation component in the strategy where calculations are required.

Configure the aggregation logic (e.g., sum, average).

References: Pega Decisioning Aggregation Components Guide

Identifying and resolving out-of-memory errors in a cluster node involves understanding the alerts that typically precede such conditions.

PEGA0004 – Quantity of data received by database query exceeds limit (Answer A):

Explanation: This alert indicates that a database query is returning more data than expected, which can lead to memory issues as the system tries to handle large data sets.

To allow three physicians to review the orders in parallel, you need to use the "Split For Each" shape. This shape enables parallel processing for each item in a list, such as the list of physicians.

Understanding Split For Each Shape in Pega:The "Split For Each" shape allows you to create instances of a subprocess for each item in a specified list. This means each physician can independently review and evaluate the surgical procedure requests simultaneously.

Configuration Steps:

Step 1: Create a list of physicians who will be performing the evaluations.

Step 2: Add a "Split For Each" shape to the process flow.

Step 3: Configure the "Split For Each" shape to iterate over the list of physicians.

Step 4: Define the evaluation subprocess to be called for each physician.

Step 5: Ensure that each physician's evaluation subprocess is independent of the others.

Advantages of Using Split For Each:This approach allows all three physicians to perform their evaluations simultaneously, reducing the overall processing time and ensuring that the process can advance as soon as two out of three evaluations are completed.

References:Pega Documentation on Split For Each shape provides detailed steps on how to configure and use this shape in your process flows.

To address difficulty in creating a customer service request through Facebook Messenger:

Change the text analyzer configured for the channel (Answer C):

Explanation: The text analyzer is responsible for interpreting user input. Improving its configuration can enhance its ability to understand and process customer requests more accurately.

Applicability:Applicability rules ensure that the right offers are presented to the right customers. If Anna holds a higher value card (Premier Rewards), the new Rewards card offer might not be applicable to her because it is a lower-tier product.

Configuration Steps:

Define applicability criteria for each offer.

Ensure that offers are presented based on customer profiles and existing products.

References:Pega Academy lessons on Offer Management explain the role of applicability rules in ensuring that relevant offers are presented to customers.

 Personas and Channels:

Personas represent the people involved in the Microjourney, defining access roles and privileges.

Channels represent how personas interact with the application, defining the technology used for these interactions.

 References:

Pega Express delivery approach focuses on designing and delivering outcomes quickly by defining key personas and the channels they use to interact with the application.

 Therefore, the correct answers are:

F. The three pillars define Personas and Channels, as Personas represent the people that are involved in the Microjourney, and the channels represent how personas interact with the application.

A. The three pillars define Personas and Channels, as Personas represent the access roles and privileges that are required in the Microjourney, and the channels represent the technology that the personas use to interact with the application.

To restrict the ability to withdraw a case to specific users, the following rule types can be used in combination:

Access When (Answer B):

Explanation: An Access When rule can be created to conditionally grant or deny access to the withdraw action based on the user's role and whether they are the creator of the case or a work group manager.

Robotic Desktop Automation (RDA) is recommended in this scenario because it enables Customer Service Representatives (CSRs) to launch and interact with multiple applications from a single interface. RDA automates repetitive tasks and integrates different systems without requiring backend changes, making it an ideal solution for environments where applications are built on diverse technologies. This approach improves efficiency by reducing the manual effort needed to synchronize data across systems, ensuring real-time updates and data consistency.

References:

Pega Robotics: Pega Robotics Overview

Pega Customer Service: Pega Customer Service Capabilities

To troubleshoot chronic performance issues in a cloud-based production application, you can use the following techniques:

Performance Alerts and Exceptions in PDC: Review the alerts and exceptions in Pega Predictive Diagnostic Cloud (PDC). PDC provides real-time monitoring and insights into performance issues.

Performance Alerts and Exceptions using PLA: Use the Pega Log Analyzer (PLA) to review alerts and exceptions. PLA helps in identifying and diagnosing performance bottlenecks by analyzing log files.

References:

Pega Predictive Diagnostic Cloud (PDC)

Pega Log Analyzer (PLA)

 Using the PropertyRead access control policy for the SSN and date of birth ensures that only users with the appropriate access (e.g., HR Manager) can view these details. This approach masks the information for other users.

 References:

Pega best practices for data security and access control recommend using PropertyRead policies to restrict access to sensitive information.

 Therefore, the correct answer is:

A. Use the PropertyRead access control policy for the SSN and date of birth.

Class Structure Flexibility: The class hierarchy allows for instances of Parking and Auto to be stored either together or separately, depending on the implementation requirements and table mapping configurations.

The best solution for maintaining discounts in an e-commerce application by a business manager is:

List Landing Page with Default Data Sources (D):

A list landing page provides an intuitive interface for business users to view, manage, and update discount details. By defining default data sources, the data is automatically fetched and displayed, simplifying the maintenance process.

This approach ensures that business managers can easily access and modify discount information without needing deep technical knowledge.

References:

Pega Platform Help on Configuring Landing Pages

Define Privilege:

Create a privilege specific to the section containing personal data.

Assign Privilege:

Assign this privilege to roles associated with managers in the HR organization.

Team A publishes branch,

Automation server merges three branch,

Team B and C rebase the application

To extend the Pega Foundation for Healthcare (PFH) data model:

Direct Inheritance for Extension (B):

Use direct inheritance to extend the foundation data model provided by PFH. This ensures that the core data model remains intact while allowing for the addition of new fields and data classes specific to the company's needs.

Pattern Inheritance for Behavior (B):

Utilize pattern inheritance to extend application-specific behavior. This allows for customization and the addition of application-specific logic while maintaining a clear separation from the core data model.

References:

Pega Foundation for Healthcare Implementation Guide

Pega Inheritance Models Documentation

For back-to-back processing on the follow action form to ensure that getnextwork processing does not occur, configure it to "Look for the assignment to perform." This ensures that the system checks for the next assignment within the current context without moving to the next item in the work queue. References:

Pega Get Next Work Configuration: Get Next Work

A rule-utility-function (RUF) has the advantage of being directly callable from a decision table, which is a common requirement in Pega applications for implementing business logic. This direct invocation capability simplifies the design and execution of decision rules. References:

Pega Rule-Utility-Functions: Rule-Utility-Functions

Tax Case Type and Specialization:

Create a new tax case type within the Pega Platform application to handle the independent tax processing functionality.

Utilize case type specialization to define different processes for each country. This means creating specialized versions of the tax case type based on the country property.

Country-specific Processes:

Each specialized tax case type will have its own processes tailored to the specific tax regulations and requirements of the respective country.

This allows for the flexibility to handle different tax processing rules and ensures compliance with country-specific tax laws.

Routing and Assignment:

Configure routing rules to assign the tax cases to the appropriate tax consultants based on the country.

Use decision tables or decision trees to determine the correct tax consultant for each case, ensuring that the case is handled by a consultant with the relevant expertise.

Efficiency and Maintenance:

By using case type specialization, the application maintains a clear and organized structure where each country’s tax processing logic is encapsulated within its own specialized case type.

This makes the system easier to maintain and update, as changes to tax processing rules can be made within the specific country’s specialized case type without affecting others.

When tuning the agent configuration on a production system, it is important to review and adjust default agents because:

Not Necessary for Every Application: Some default agents are not necessary for every application and can be disabled to improve performance.

Should Never Run in a Production Environment: Certain agents are intended for development or testing environments and should not be active in production to avoid unnecessary processing and potential security risks. References:

Pega Agent Configuration Guidelines: Agent Configuration

Retention:Retention strategies focus on keeping existing customers and preventing churn. Next-Best-Action can help identify at-risk customers and offer personalized incentives to retain them.

Service:Enhancing customer service by providing personalized and relevant recommendations can improve customer satisfaction and loyalty. Next-Best-Action helps in suggesting the best service actions based on customer data and context.

Collections:In collections, Next-Best-Action can be used to determine the most effective strategies for recovering debts, such as personalized payment plans or reminders.

References:Pega Customer Decision Hub documentation on business issues highlights the importance of Retention, Service, and Collections in decisioning strategies.

 Queue Status "Available": When the queue status for an item is "Available," it indicates that the item is ready for processing but has not yet been picked up by the agent.

 Failed Processing: If the agent attempted to process an item but failed, it can be reflected in the status. The item remains in the queue, and the system logs may indicate the failure reason.

 Scheduled Processing: The status "Available" can also mean that the item is scheduled for future processing based on the agent's schedule.

References:

Pega Academy: System Queue Management

Pega Documentation: Understanding Agent Status and Queue Management

The class structure in Pega defines how different case types and sub-cases relate to each other. EventBooking cannot be a subcase of Auto if the business logic does not support such a relationship. Ensuring the correct hierarchy is crucial for maintaining logical and functional consistency in the application.References:

Pega Class Structure Guidelines: Pega Class Structure

The Exclude Operators option in the Security Policies landing page allows administrators to specify certain operators, such as Admin or Executive roles, who should be exempt from the lockout policy. This ensures that critical users retain access even after multiple failed login attempts, aligning with the requirement to exclude specific roles from lockout policies.

References:

Pega Security Policies: Configuring Security Policies

Pega Authentication: Authentication and Access Control

Ensuring that new team members adhere to best practices can be achieved through the following methods:

Branch Review: Utilize the branch review feature in Pega, where senior team members can review the contents of the branch. This allows experienced developers to provide feedback and ensure that the new rules meet the required standards.

Branch Quality Review: Regularly review the quality of the branch to identify any rules that have guardrail warnings. Guardrails are best practice guidelines in Pega, and addressing these warnings helps maintain high-quality, robust rules.

References: Pega Platform documentation on branch development and guardrail compliance.

 Dynamic Layout: This layout allows for flexible arrangements of items within the form. It supports wrapping content based on screen size, making it ideal for responsive design.

 Row Configuration: Within a dynamic layout, elements can be configured to flow like words in a sentence, wrapping to the next line as necessary. This is essential for displaying book covers in a row that adapts to different screen widths.

 Responsive Behavior: Dynamic layouts are designed to handle varying screen sizes seamlessly, ensuring that the UI remains user-friendly on all devices.

 Reference: Pega documentation emphasizes the use of dynamic layouts for creating flexible and responsive UI designs (Pega Platform 8.7 Documentation, User Interface - Layouts).

 Extending Core Pega Classes:

Extending existing core Pega Platform classes such as Data-Party-Person, Data-Party-Com, and Data-Address-Postal ensures that the application adheres to standard Pega data models.

Persisting instances of these extended classes in the PegaData schema aligns with best practices for data persistence and reuse.

 References:

Pega Lead System Architect documentation on data modeling recommends extending core Pega classes to maintain consistency and leverage built-in functionalities.

 Therefore, the correct answer is:

A. Extend existing core Pega Platform classes such as Data-Party-Person, Data-Party-Com, and Data-Address-Postal, persisting instances of the extended classes in the PegaData schema.

 In a decision strategy, to use a customer property in an expression, you need to prefix the property with the keyword Customer.

 This ensures that the property is correctly identified and retrieved from the customer data page.

Enable Auditing:

On the Rule-Declare-Decision Table RuleForm, check the option to enable auditing.

Monitor Changes:

This configuration will track changes made to the decision table in the production environment.

Wait Shape with Case Dependency:

The best practice in Pega for handling dependencies between cases is to use a Wait shape configured with case dependencies. This ensures that the mortgage case waits for the completion of the credit report case before proceeding.

By configuring the Wait shape to monitor the status of the credit report case, it ensures that the mortgage case automatically resumes once the credit report case is resolved.

Process Configuration:

In the mortgage case process, insert a Wait shape where the process needs to pause for the credit report.

Configure the Wait shape to depend on the resolution of the credit report case. This can be done by specifying the case ID of the credit report as a dependency.

Automation and Efficiency:

This method is efficient as it automates the waiting process without manual intervention. The mortgage case resumes automatically once the credit report case completes, ensuring smooth workflow automation.

It avoids the need for complex SLAs or additional activities to check the status of the credit report case, simplifying the process design.

Routing to Specialist:

Once the Wait shape condition is satisfied, the process flow continues to the step that routes the mortgage case to a specialist.

This ensures that the mortgage case is routed at the appropriate time, maintaining process integrity and efficiency.

The system will consider the assignments with urgency value equal to and greater than the specified value in the Operator rule. Once all assignments are processed from the work queue based on the threshold urgency value, the lower urgency assignments are then considered.

Urgency Thresholds: The system checks the urgency of assignments in each work queue. Assignments with an urgency equal to or greater than the threshold are considered first.

Get from Work Queues First: With this option selected, the system prioritizes processing work queues before considering individual workbaskets.

Lower Urgency Assignments: After processing assignments meeting the urgency thresholds, the system will then consider lower urgency assignments if there are no higher urgency tasks left.

To create a report that shows the number of employees with varying years of service, the best approach is to use a SQL function:

SQL Function: Create a SQL function that categorizes the employees based on their years of service. This function can then be used in the report definition to generate the desired output.

Implementation: Implement the function to return different categories such as more than 20 years, between 15 and 20 years, etc.

References:

Creating SQL functions in Pega

Criterion 1: Owns a smart mobile

Engagement Policy Level: Group level

Explanation: The criterion "Owns a smart mobile" applies to all data plans and can be considered a group-level policy. It filters the audience at a broader level to ensure they have a smart mobile device.

Criterion 2:

Under graduation student

Engagement Policy Level: Issue level

Explanation: The criterion "Under graduation student" applies to multiple data plans (1 GB and 3 GB) and is more specific to the issue of targeting educational segments. Thus, it is suitable at the issue level.

Criterion 3:

Post graduation student

Engagement Policy Level: Action level

Explanation: The criterion "Post graduation student" is specific to the 5 GB plan and is most appropriate at the action level. This level ensures the targeting is precise for this particular plan.

New customer

Engagement Policy Level: Group level

Explanation: The criterion "New customer" can be applied across multiple offers and thus is suitable for the group level to broadly target new customers.

Existing customer

Engagement Policy Level: Action level

Explanation: The criterion "Existing customer" is applied at the action level to ensure specific offers (3 GB and 5 GB plans) are appropriately targeted to customers who already have a relationship with the company.

Step by Step Comprehensive Detailed Explanation with References:

Group Level Engagement Policy:

Conditions that apply broadly across multiple offers or groups of offers fall under group-level policies. Examples include owning a smart mobile and being a new customer.

Issue Level Engagement Policy:

Conditions that are relevant to a specific issue, such as educational status for specific data plans, are categorized under issue-level policies. This ensures that offers targeting undergraduates are consistently managed.

Action Level Engagement Policy:

Conditions that are specific to individual actions or offers are best managed at the action level. This includes targeting post-graduation students for the 5 GB plan and existing customers for specific plans to ensure precise targeting.

References: Pega's best practices for engagement policies recommend using group-level policies for broad criteria, issue-level for segment-specific conditions, and action-level for highly specific targeting to ensure effective and relevant customer engagement.

To create a new control with a shortcut key:

Create a new autogenerated button control and alter its caption to support a shortcut key (Answer A):

Explanation: Using autogenerated controls ensures consistency with Pega’s UI framework, and adding a shortcut key to the caption makes the button accessible via keyboard shortcuts.

To ensure that all development teams (A, B, and C) are working with the latest version of the shared rulebase, the tasks should be ordered as follows:

Team A publishes the branch to the system of record.

The system of record triggers the job on the automation server.

Automation server requests conflict detection.

The automation server merges the branch to the system of record.

Teams B and C import the application rules within their local environment.

Step by Step Comprehensive Detailed Explanation:

Team A publishes the branch to the system of record:

Explanation: Team A needs to publish their changes to the central repository (system of record) to make them available for integration and further processing.

The system of record triggers the job on the automation server:

Explanation: Once the branch is published, the system of record initiates an automated process to handle the new changes. This step triggers the automation server to start its job.

Automation server requests conflict detection:

Explanation: The automation server needs to check for any conflicts between the newly published branch and the existing codebase. This ensures that any issues are identified and resolved before merging.

The automation server merges the branch to the system of record:

Explanation: After conflict detection and resolution, the automation server merges the changes from the branch into the main codebase in the system of record.

Teams B and C import the application rules within their local environment:

Explanation: Once the merge is complete, Teams B and C can import the updated application rules into their local environments to ensure they are working with the latest version of the rulebase.

References: According to Pega’s best practices for managing distributed development teams, this sequence ensures that changes are properly integrated and conflict-free before being distributed to other teams, promoting consistency and minimizing integration issues.

Scenario testing in Pega is used to create UI-based, end-to-end tests for applications. The following statements are true about scenario testing:

Scenario Tests Can Include Another Scenario Test (A):

Scenario tests can be nested, allowing one scenario test to include another. This enables the reuse of common test steps and enhances the modularity of test cases.

Scenario Tests Do Not Support File Uploads or Downloads (C):

Scenario tests are designed to simulate user interactions but do not support file uploads or downloads as part of the test execution. This limitation ensures tests focus on UI interactions and business logic.

Scenario Tests Support the Setup or Cleanup of Test Data (E):

Scenario tests allow for the setup or cleanup of test data before or after the test execution. This capability ensures that the test environment is correctly prepared and that any test data is appropriately managed.

References:

Pega Scenario Testing Guide

Pega Platform Test Automation Documentation

To minimize potential development conflicts and ensure that both development teams work with the most current version of the Policy Administration application, the following best practices should be followed:

Perform Branch Reviews when Merging Branches (A):

Regularly review and validate changes made in branches before merging them into the mainline. This ensures that any conflicts or issues are identified and resolved early in the development process.

Branch reviews help maintain code quality and prevent integration problems.

Periodically Sync the Policy Administration Application Code (D):

Synchronize the Policy Administration application code regularly to ensure that the Quoting application team is working with the latest version.

This practice helps to avoid discrepancies and ensures that enhancements and updates in the Policy Administration application are consistently reflected in the Quoting application.

References:

Pega Platform Best Practices for Branching and Merging

Pega Application Development Guide

To configure the application to handle the requirement where employees can designate alternate operators to perform their work while they are on vacation, follow these steps:

Define a custom Access When rule:

Create an Access When rule named pxAssignedToMeOrAlternate. This rule will allow the system to check whether the assignment is for the current user or their designated alternate.

The rule should include logic to determine if the assignment belongs to the operator or the operator’s alternate.

Modify the pyUserWorkList Report Definition:

Access the pyUserWorkList report definition which is used to display the worklist for the current user.

Modify this report to include a filter condition using the pxAssignedToMeOrAlternate Access When rule. This ensures that the report displays assignments for both the current user and any assignments for which they are an alternate.

Assign Worklist assignments to alternate operators:

Ensure that the assignments visibility is adjusted accordingly by modifying the security settings to allow access to assignments for alternate operators.

Testing and Verification:

Test the configuration to ensure that alternate operators can see and access the worklist items of the operators they are covering for.

This approach leverages Pega’s Access When rules to dynamically adjust the visibility of assignments based on operator relationships, ensuring that alternate operators can perform work as needed without requiring manual assignment transfers.

References:

Pega Documentation on Access When rules: Access When Rules

Pega Documentation on Report Definitions: Report Definitions

To avoid creating unnecessary case-level properties and views in Pega Express:

Define case type views using "* page, property" syntax for the majority of the fields (Answer A):

Explanation: Using this syntax allows you to reference existing data types and properties, reducing redundancy and the need for additional case-level properties.

 Loading Customer Data in Parallel:

Using the Load-DataPage and Connect-Wait methods to load customer data in parallel ensures that the data is retrieved efficiently and concurrently from multiple sources.

 System of Record (SOR) Data Access Pattern:

Using the SOR data access pattern to reference customer data ensures that the data is always current and consistent across all child cases.

 References:

Pega documentation on data management and integration patterns recommends these approaches to maintain data integrity and performance.

 Therefore, the correct answers are:

A. Load the customer data in parallel using the Load-DataPage and Connect-Wait methods.

C. Use the System of Record (SOR) data access pattern to reference the customer data.

In a highly available system with crash recovery enabled:

Yes, If the authentication cookie was lost (Answer C):

Explanation: If the authentication cookie, which maintains the user’s session, is lost during the crash, the user will need to be reauthenticated to establish a new session.

To address the requirement where users working in one application need to create cases in another application, the recommended approach is to implement Federated Case Management (FCM).

Federated Case Management: FCM allows different Pega applications to share and manage cases across multiple systems. This approach enables seamless case creation and management, ensuring that users can interact with cases regardless of the application they are working in.

Synchronization and Communication: FCM facilitates synchronization and communication between different Pega instances, ensuring that case data is consistent and accessible across the applications.

References: Pega Platform documentation on Federated Case Management.

Data Transform Configuration:

Create a data transform that copies the selected items to the page list property.

Post-Processing Action:

In the flow action, add the data transform as a post-processing action to ensure it executes after the form submission.

Testing:

Test the form submission to verify that the selected items are correctly copied to the page list property.

References:

Pega Academy: Data Transform and Flow Actions.

Pega Documentation: Configuring Post-Processing Actions.

 Job Scheduler with SendEmailNotification Utility:

Running a job scheduler to pull customer records matching the current date and using the SendEmailNotification utility ensures that emails are sent out at midnight. Recording failures in a data type captures the necessary error information.

 Job Scheduler with CorrNew Utility:

Using the CorrNew utility to send emails and record any exceptions in a data type also satisfies the requirement for recording email delivery failures.

 References:

Pega documentation on job schedulers and email utilities provides guidelines for implementing scheduled tasks and handling email delivery.

 Therefore, the correct answers are:

B. Run a job scheduler, and pull the customers that match the current date. For each record, invoke the SendEmailNotification utility. If any exception is received in email delivery, mark the failure in a data type.

D. Run a job scheduler, and pull the customers that match the current date. For each record, invoke the CorrNew utility. If any exception is received in email delivery, mark the failure in a data type.

Configure Add Party User Action:

Go to the user actions section in the case type configuration.

Local Action Configuration:

Ensure that the addparty user action is available as a local action during case creation to allow case workers to add a work party.

Graphical user interface, application Description automatically generated

 Association Rules: Association rules in Pega are used to define relationships between different classes. By creating association rules for the set of classes used in reports, you streamline the process of joining these classes in various reports.

 Simplified Reporting: When managers create reports, they can easily include the necessary class joins by leveraging these predefined association rules, thus reducing complexity and the likelihood of errors.

References:

Pega Academy: Building Reports with Association Rules

Pega Documentation: Association Rules

Defining a case type within a case type-specific ruleset provides several advantages:

Branch Ruleset Association: By associating each branch ruleset with case-specific user stories, you can better manage development and testing. This allows for more targeted reviews and testing, ensuring that changes are isolated and easily traceable.

Component Application Conversion: If there is a possibility that the case type might be converted to a component application in the future, having a case-specific ruleset simplifies the process. It allows the case type to be more easily packaged and reused across different applications.

References: Pega Platform best practices for ruleset management and case type design.

To configure a report definition that lists new customer cases created in a given day and the average opening balance for all account child cases for each customer, you should use the "class join" feature in Pega. This feature allows you to join data from different classes, which is essential when dealing with cases and their child cases. Specifically, you can create a join between the customer case class and the account child case class to aggregate the average opening balance.

The Localization wizard in Pega is designed to facilitate the process of localizing an application. It extracts string values from various parts of the application, ensuring that all text is available for translation. It also creates field value rules for labels used throughout the application, allowing for easy updates and translations. These capabilities are crucial for maintaining a consistent user experience across different languages and locales.References:

Pega Documentation on Localization Wizard: Pega Localization Wizard

To ensure that every attempt by a developer to check a rule into a certain ruleset version is reviewed before that rule is allowed to be checked in:

C. Override the FindReviewers decision tree to invoke a when rule that evaluates the criteria, if the when rule returns true, the decision tree returns SendBack.

By overriding the FindReviewers decision tree and incorporating a when rule, you can enforce criteria such as complete history tab fields and justified warnings. If the criteria are not met, the decision tree returns SendBack, preventing the rule from being checked in.

References:

Pega Documentation on Rule Check-In: Rule Check-In

Pega Documentation on Decision Trees: Decision Trees