 A sales representative wants to quote the cost of an insurance policy based on selected coverage options: Calculated fields can dynamically determine the cost based on selected options.

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 achieve the requested behavior in the event center case type:

Create a checkbox for customers to indicate whether they want catering for the event. This allows customers to specify their preference for catering.

Add a decision shape to evaluate whether the customer has checked the catering checkbox. Based on this decision, the case will either proceed to provide a rental rate quote or prompt the customer to choose a menu before receiving a quote.

Configure the menu preferences and appointment date fields with a visibility condition that displays these fields only if the customer selects the catering checkbox. This ensures that customers who do not want catering do not see these fields, streamlining the process.