Can you explain what a case-type ruleset is in PEGA?

 Case-type ruleset in Pega

In PEGA, a case-type ruleset in Pega is a framework that defines a specific business process or service the application manages. The Case Type Ruleset in Pega specifically includes a set of rules and configurations that describe the structure, stages, processes, and behaviors of a particular case type.

Key Components of a Case Type Ruleset in Pega

 Case-type ruleset in Pega
Case-type ruleset in Pega

1.Case Type: The primary rule that defines the structure and lifecycle of a case. It outlines the stages and steps involved in processing the case.

2.Stages: major phases in the case lifecycle. Each stage represents a significant milestone and can contain multiple steps or processes.

3.Steps: actions or tasks within a stage. Steps can include:

Processes: automated sequences of actions.

Subprocesses: nested processes within a parent process.

User actions: tasks that require human interaction.

Automated Actions: Tasks performed automatically by the system.

4.Case Life Cycle: The end-to-end flow of the case from creation to resolution, defined by the stages and steps.

5.Processes and Flows: Detailed workflows within a stage that specify the sequence of actions, decision points, and branching logic.

6.Data Model: Defines the data structure however, information required for the case, including data objects, properties, and relationships.

7.User Interfaces (UI): forms and screens that users interact with during case processing. This includes harnesses, sections, and controls.

8.Decision Rules: Business rules and logic are used to make decisions within the case. This includes decision tables, decision trees, and when rules.

9.Service Level Agreements (SLAs): timelines and goals for completing stages and steps, ensuring timely processing of cases.

10.Notifications: alerts and messages sent to users based on specific events or conditions within the case.

11.Attachments and Notes: Mechanisms for adding supporting documents and comments to a case.


Consider a “Loan Application” case type in a financial services application:


Submission: Collect applicant information and required documents.

Verification: Verify applicant information and credit history.

Approval: Approve or reject the loan application.

Disbursement: Disburse the loan amount to the applicant.


Submission Stage:

User Action: Fill out the application form.

Automated Action: Send an acknowledgment email.

Verification Stage:

Subprocess: Perform a credit check.

User Action: Review verification results.

Approval Stage:

Decision Rule: Approve or reject based on criteria.

Automated Action: Notify the applicant of the decision.

Disbursement Stage:

User Action: Confirm disbursement details.

Automated Action: Transfer funds.

Detailed Components of a Ruleset in pega

 Case-type ruleset in Pega
Case-type ruleset in Pega

1.Case Type Rule:

Creation: Defines how a case is initiated, including the data collected at the outset.

Case ID: an automatically generated unique identifier for each case instance.


Primary Stages: Core stages in the main flow of the case.

Alternate Stages: Used for exception handling, escalations, or alternate flows.


Step Types:

Collect Information: Gather data from users.

Approve/Reject: Decision points for user approvals.

Process Task: Execute automated processes or subprocesses.

Send Correspondence: Generate and send emails or notifications.

Wait: Pause the case until a specific condition is met.

Transition Conditions: Rules that determine the transition between steps based on outcomes or conditions.

4.Processes and Flows:

Additionally, Flow Rules define the sequence of tasks, decisions, and events within a process.

Flow Shapes provide visual representations of tasks, including assignments, decisions, and integrations.

Flow Actions specify the actions users can take at each step, encompassing UI forms and data entry.

5.Data Model:

Data Types: Define reusable data structures, such as customer, product, or order.
Properties: attributes of data types, such as name, address, or order amount.
Data Pages: Define sources and structures for retrieving data, either from external systems or internal calculations.

6.User Interfaces (UI):

Harnesses: Define the overall layout of a screen.
Sections: Modular components of the UI that can be reused across multiple screens.
Controls: UI elements like buttons, input fields, and drop-down lists.

7.Decision Rules:

Rules: simple true/false conditions to control flow transitions or UI elements.
Decision Tables: A tabular representation of complex decision logic.
Decision Trees: A tree-like structure for branching decision paths.
Map Values: Multi-dimensional tables for complex decision-making.

8.Service Level Agreements (SLAs):

Goals: Target times for completing stages or steps.

Deadlines: maximum allowable times for completion.

Escalations: actions to take if goals or deadlines are missed.


Email: Configurations for sending automated emails.

Push Notifications: Alerts sent to mobile devices.

In-App Notifications: Alerts displayed within the application.

10.Attachments and Notes:

Attachment Categories: Define the types of documents or files that can be attached.

Notes: Allow users to add comments or observations.

Advanced Concepts

1.Case Hierarchies:

Parent-Child Cases: A structure where a parent case can spawn multiple child cases.

Case Dependency: Managing dependencies however, synchronization between parent and child cases.


Date-Based: Apply different rules based on effective dates.

Property-Based: Vary behavior based on specific property values.

Template-based: Moreover, use templates to define common circumstancing patterns.

3.Workbaskets and Worklists:

Workbaskets: Furthermore, queues where cases are assigned for group processing.

Worklists: Moreover, individual user queues facilitate personal case assignments.

4.Case Processing and Routing:

Routing Rules: Furthermore, define how cases are assigned to users or workbaskets

Assignment Types: Additionally, configure tasks to be performed by specific users or roles.


Connectors: Integrate with external systems (e.g., REST, SOAP, databases).

Services: Furthermore, expose PEGA functionality as services to external systems.

Best Practices in Ruleset Pega

  1. Modular Design: Additionally, break down case types into reusable components to enhance maintainability and reusability.
  2. Versioning: Moreover, use ruleset versions to manage changes and updates systematically.
  3. Testing:  Furthermore, implement thorough testing strategies, including unit tests, integration tests, and user acceptance tests (UAT).
  4. Documentation: Additionally, maintain comprehensive documentation for all case types, rules, and configurations.
  5. Performance Optimization: Monitor and optimize case processing performance, especially for complex or high-volume cases.


The ruleset pega for this case type would include all the rules however, configurations needed to define and manage the loan application process, ensuring consistency and reusability across the application.

Few more topics on pega click here

Leave a Comment