Pega CPSSA key terms

The ordered set of stages and processes a case moves through from creation to resolution. Stages represent business phases, and each stage contains processes whose steps perform the actual work.

A major phase of a case life cycle, such as Intake, Fulfillment, or Resolution. A stage groups related processes and can be configured to repeat, to start automatically, or to require a user action.

A container of steps within a stage that defines a unit of work. Processes run sequentially or in parallel and can be chained so that one starts automatically when another completes.

The smallest unit of work in a case life cycle, represented by a shape on the case designer canvas. Each step type performs a distinct action, such as collecting data or sending an email.

A step that creates a task for a user or work queue to complete. It routes work to a specific operator or group and can include a flow action for data entry.

A step that executes without human intervention, such as sending a notification, calling a data transform, or invoking a service. It moves the case forward automatically.

A stage that is not part of the main sequence and is entered only when specific conditions are met, such as a rejection path. It lets a case branch into exception handling without disrupting normal flow.

A rule that evaluates combinations of input property values against rows of conditions and returns a result. It is commonly used to drive routing, pricing, or eligibility logic in a case.

A rule that evaluates a series of branching conditions to reach a result. Unlike a decision table, it evaluates one condition at a time, making it suitable for logic where later tests depend on earlier outcomes.

A reusable boolean expression stored as a rule and referenced wherever conditional logic is needed. It centralizes a test so that changing the rule updates every place it is used.

A rule that sets deadlines and timing goals for a case or assignment, such as a goal and a deadline. It can trigger escalations, notifications, or automatic actions when time thresholds are crossed.

A shared container of assignments that a group of operators can pull work from. Routing to a work queue distributes tasks across a team rather than to a single named user.

An organizational unit that groups operators and can own work queues. A work group defines who is eligible to receive work routed to its associated queues.

A rule that copies, maps, or sets property values between pages or within a page. It is used to initialize data, translate between data structures, and prepare data for integrations.

A named attribute that holds a value on a case or data object, with a defined data type such as text, integer, or a page. Properties are the building blocks of the application data model.

An in-memory structure that holds a set of related properties, similar to an object instance. Pages can be single instances or lists and are referenced by name in rules and expressions.

A rule that loads and caches a page of data for reuse across the application. It can be scoped to a requestor or node and can refresh on demand or on a schedule.

The in-memory store of pages available to a running application at a given moment. Understanding clipboard structure helps diagnose data availability and performance issues.

A rule that defines the shape of a data object, including its properties and relationships to other types. It governs how instances are stored, validated, and displayed.

A rule that defines a business object that can be processed as a case, including its life cycle, data model, and user interface. It is the central design artifact for a case management application.

A technique for defining variations of a rule that apply only when specific conditions are true, such as a particular property value or date range. It avoids duplicating rules for each variation.

The engine's process for selecting which rule instance to apply when multiple versions exist. It considers class inheritance, circumstance, and availability to choose the most specific match.

A named group that defines reusable behavior and data structure through inheritance. Rules are organized by class, and subclasses inherit and can override rules from their parent classes.

A reusable user interface rule that defines a portion of a screen, such as a form or a layout. Sections can be embedded in other sections and are the primary building block of the UI.

A rule that defines the full-page container for a user interface, including the header, navigation, and the sections it hosts. Different harnesses serve different contexts, such as perform or review screens.

A structural element within a section that arranges its child components, such as in columns, rows, or tabs. Layouts control positioning and responsiveness of the fields they contain.

A rule that defines the user interface and processing for a single step in a flow, including the section displayed and the data changes applied on submit. It connects user interaction to case processing.

A rule that centralizes the visual styling of an application, including colors, fonts, and spacing. Changing the skin updates the appearance of all components that reference it.

A rule that assigns an operator to a set of roles and an application, determining which rules and features the user can access. It is a primary control point for authorization.

A named set of privileges and permissions that can be granted to operators through access groups. Roles control what actions a user may perform within the application.

A named permission that a rule or action can require before it executes. Privileges are granted through access roles and checked at runtime to enforce fine-grained authorization.

A rule that restricts read or write access to properties based on conditions such as user role or case state. It enforces data-level security beyond role-based menu access.

A record representing an individual user, including credentials, contact details, and the access groups assigned to them. It is the identity used for authentication and authorization.

The process of verifying a user's identity before granting access to the application. It can be handled locally or through external identity providers using standard protocols.

An authentication scheme in which one set of credentials grants access to multiple applications through a trusted identity provider. It reduces password sprawl and centralizes identity management.

A warning raised by the platform when a rule deviates from recommended design practices, such as excessive complexity or improper inheritance. Guardrails help maintain application quality and maintainability.

A rule that defines how the application communicates with an external system, specifying the endpoint, request format, and response handling. It is used to retrieve or send data during case processing.