Pega CPBA key terms

A lightweight, design-first delivery methodology that builds a working application in short micro-journeys, starting from a shared business vision rather than a full requirements document.

A human-centered approach used in Pega Express to understand real user needs through empathy, ideation, and rapid prototyping before configuring the application.

A short, focused delivery cycle inside Pega Express in which a small slice of the application is designed, built, demonstrated, and refined with stakeholders, typically lasting days rather than months.

The smallest release that still delivers a complete, satisfying experience for its users; Pega Express favors it over a bare minimum viable product because adoption depends on user delight.

A representative profile of a user group, describing goals, context, and pain points, used during design to shape the case types and screens that serve that group.

The end-to-end sequence of stages a customer or user experiences while achieving an outcome, mapped early so that case types and channels align with real behavior.

The blueprint for a business transaction, defining its stages, steps, data, processes, and user interface; every case instance is created from a case type.

A single instance of a case type that tracks one piece of work through its lifecycle, carrying its own data, history, assignments, and attachments.

A major phase in a case lifecycle, such as Intake, Processing, or Resolution, that groups related steps and controls when the case can move forward.

A unit of work inside a stage, representing an action or milestone the case must pass, which may contain one or more processes and assignments.

A sequence of shapes that defines the flow of work within a step, including assignments, decisions, subprocesses, and integrations.

A task routed to a user or work queue that must be completed before the process continues; it appears in a user's worklist or workbasket.

The configuration that connects a process step to a user interface section and defines what happens to case data when the user submits the assignment.

A shared pool of unassigned work items that eligible users can pick up; also called a workbasket, it supports team-based routing rather than named individuals.

The personal list of assignments currently routed to a specific operator, shown in the user's portal for action.

An organizational unit that groups operators and managers, providing a default work queue and reporting scope for the team.

The overall structure of stages and steps that a case passes through from creation to resolution, visible as a progress indicator to users.

A reusable definition of a data structure, such as a customer or product record, that can be referenced by case types and populated from internal or external sources.

A named, cacheable rule that loads data on demand and can be scoped, refreshed, and shared across the application to reduce repeated calls to source systems.

A rule that maps and manipulates clipboard data, copying values between pages, setting defaults, and converting structures during case processing or integration.

The in-memory data structure that holds the pages a user's session is working with, including case data and reference data loaded by data pages.

The configuration that connects a Pega application to external systems, using connectors for outbound calls and services for inbound requests.

A rule that lets Pega call an external system, such as a REST or SOAP endpoint, and map the response back into application data.

An inbound interface that exposes Pega functionality to other systems, allowing external applications to create or update cases through a defined contract.

A security rule that binds an operator to an application, a portal, and one or more roles, determining which rules and features the user can access.

A named collection of privileges that grants or denies specific actions, such as deleting cases or running reports, to the access groups that reference it.

A user record identifying an individual, including credentials, organizational placement, and access group membership that together determine what they can do.

A granular permission, such as the ability to perform a specific action, that is granted through roles and checked by the application at runtime.

A security model that grants access based on conditions evaluated against case or user properties, allowing fine-grained control beyond static roles.

A reusable user interface rule that lays out fields, labels, and controls, and is referenced by flow actions and harnesses to render screens.

The outer layout rule that defines the frame of a portal or case screen, including headers, navigation, and the area where sections are displayed.

The web interface users see when they log in, composed of a harness and navigation, and assigned to users through their access group.

A deployable unit that bundles rules, case types, data, and security settings, built on a hierarchy of built-on applications to enable reuse.

A lower layer in the application hierarchy whose rules are inherited by the current application, supporting reuse of shared components across products.

A versioned container for rules that controls which rule versions are available at runtime and supports migration between environments.

A numbered release of a ruleset, such as 01-01-01, with rules copied forward between versions so that changes can be staged and deployed safely.

A rule that specifies the class, columns, filters, and grouping for a report, and can be run directly or used as the source for a report widget.

The interface where users find, run, and organize report definitions, including categories and personal reports.

A Pega-built application delivered through a mobile channel, using responsive or dedicated mobile screens and offline-capable case processing.

A capability that lets mobile users continue working on assigned cases without connectivity, synchronizing data when the device reconnects.