The name of Pega's business architecture design that aligns human intelligence and process automation with business logic to deliver high-value software solutions is Center-out.

Center-out Design:

This approach focuses on designing the core business logic and processes first (the "center") and then extending outwards to include the user interface (UI) and channels.

By centering on the core logic, Pega ensures that the most critical aspects of the business process are well-defined and robust. This approach supports scalability and adaptability as the system grows and evolves.

References:

Pega Academy: Center-out Business Architecture

Pega Documentation: Center-out Design Principles

When planning the next Minimum Lovable Product (MLP) release, a Pega Business Architect should focus on the three pillars of case design: Personas and Channels, Case Types, and Data and Interfaces.

Personas and Channels:

Personas: Identify the different user roles (personas) that will interact with the application. Understanding personas helps in designing user experiences that meet their needs.

Channels: Determine the channels (e.g., web, mobile) through which users will interact with the system. This ensures that the application is accessible and user-friendly across different platforms.

Case Types:

Case Types: Define the different types of cases that the application will manage. Case types are fundamental to structuring the application and ensuring that it can handle various processes and workflows efficiently.

Data and Interfaces:

Data: Identify the data required to support the case types and processes. This includes understanding data sources, data structures, and how data will be captured and used.

Interfaces: Determine the interfaces needed to integrate with external systems. Interfaces are crucial for ensuring that the application can interact with other systems and exchange information seamlessly.

References:

Pega Academy: Case Design

Pega Documentation: Minimum Lovable Product (MLP)

To sort the cases so that the case with the most recent create date appears at the top, you need to select the Highest to Lowest sort type for the Create Date column.

Select Highest to Lowest sort type: This ensures that the most recent date is listed first and the oldest date is listed last.

References:

Pega Academy: Report Definitions

Pega Documentation: Sorting Data in Reports

Project delivery leader: The Project Delivery Leader is responsible for overseeing the project plan, managing resources, and ensuring that project milestones are met. They play a key role in verifying the project plan and adjusting schedules to manage expectations and ensure timely delivery.

To ensure that purchase requests automatically go to the manager of an employee in Pega, you should design a case with a step that routes the request to the manager. The steps are as follows:

Define the Manager Routing Step: In the case type design, include a step that specifies the routing logic.

Use Dynamic Routing: Configure the routing step to dynamically determine the manager based on the employee's profile or organizational hierarchy.

Route to Manager: Implement the routing step so that it evaluates the employee's manager information and routes the case accordingly.

This setup ensures that each purchase request is automatically directed to the appropriate manager for approval, streamlining the process and ensuring compliance with organizational policies.

References:

Pega Academy: Routing and Assignments

Pega Documentation: Case Management and Workflow Automation

 Submission: This phase involves the initial contact and filing of the claim, which typically doesn't need to be a separate case as it's an initial action.

Decision tables in Pega are ideal for situations where you need to apply multiple conditions to arrive at a decision. They are best used when you have a limited number of conditions and actions that result in a discrete set of outcomes.

B. A dance studio recommending a membership type based on the number and type of dance classes is suitable for a decision table. The number and type of classes can be mapped to specific membership types in a table format where each row represents a possible scenario and outcome.

D. A hair care company suggesting a line of products based on various attributes such as hair type, scalp moisture, hair moisture, and whether it is color-treated is also suitable for a decision table. Each combination of attributes can correspond to a specific product recommendation, making a decision table an efficient way to handle these rules.

References:

Pega Decision Management Overview

Pega Academy: Decision Table Rules