Pega CPBA flashcards
Pega CPBA · Build recall with a focused review session.
34 cards. Read the term and the definition here. The deck at the top of this page is optional.
- Pega Express phases
- Prepare, Design, Build, Test, Deploy. Prepare sets up team and environments, Design produces the Delivery Roadmap and case lifecycle, then Build, Test, and Deploy proceed incrementally by stage.
- Microjourney definition
- One primary case type plus the supporting case types needed to reach a single business outcome. It is mapped during Design before any case type is built in App Studio.
- Minimum Lovable Product
- The smallest scope that delivers real value to a user, agreed during the first design sprint. Later increments add stages to the same case type rather than new parallel case types.
- DCO artifacts
- Direct Capture of Objectives stores personas, journeys, and requirements as rules inside the application, so they are versioned with the ruleset instead of living in external documents.
- Guardrails dashboard
- An application landing page that reports counts against Pega's recommended limits, such as properties per case type and inheritance depth, flagging designs that will be costly to maintain.
- Case lifecycle structure
- A case type contains stages; each stage contains processes; each process contains steps. A case moves through stages and only one primary stage is active at a time.
- Stage transition order
- When a stage can advance, Pega checks a manual transition first, then automatic transition conditions, then the stage's default fall-through path if no condition matched.
- Process versus step
- A process is an ordered sequence of shapes inside a stage. A step is a single shape; assignment shapes create user or system work items, utility shapes perform logic without creating work.
- Subcase data propagation
- Creating a child case does not automatically share parent data. Properties must be explicitly passed to the child, and results returned through defined data propagation on the Create Case step.
- Case status components
- Status is described by stage, status value (open, resolved, pending, withdrawn), and resolution. A resolved case may be reopened if the case type's configuration permits it.
- Optimistic versus pessimistic locking
- Optimistic locking detects a conflicting save and throws an exception. Pessimistic locking holds a lock for the whole assignment and blocks other users from editing the same case.
- Data page scope options
- Thread, Requestor, Node, and Application. Choose the narrowest scope that stays correct; Node scope is shared by all requestors running on the same JVM.
- Data page refresh strategies
- Reload if older than, reload once per interaction, reload on next access, and do not reload. The strategy is evaluated each time the data page is accessed, not on a timer.
- Data type backing class
- A data type is a data object backed by a class. The Data Designer creates the class, its properties, and the backing data page together in a single guided step.
- Connector versus service
- A connector calls an external system outbound. A service exposes Pega to external callers inbound. REST handles JSON or XML over HTTP; SOAP is used for legacy WSDL contracts.
- Data Transform versus Activity
- Use a Data Transform for property-to-property mapping and shaping. Use an Activity only when you need looping, branching, or commit and database operations.
- Data page simulation
- A testing feature that supplies simulated data for a data page so a case type can be exercised without the live system of record. Simulated values are stored as test data rules.
- Access control evaluation
- Access is resolved as role, then access of role to object, then access when conditions. The most specific matching rule wins, and the requestor's access group supplies the roles.
- Attribute-based access control
- ABAC evaluates runtime conditions such as property values to grant or deny access per case instance, going beyond the static role-to-object permissions defined in the access group.
- Privileges versus roles
- A privilege is a named security check invoked from an activity or flow. It is separate from a role and grants no access-of-role-to-object permissions on its own.
- Sensitive property handling
- Properties can be marked for encryption at rest and for masking in the UI. Masking changes only what is displayed; the stored value is unchanged and remains readable by rules.
- Authentication versus authorization
- Authentication establishes who the user is, using SAML 2.0, OpenID Connect, or LDAP. Authorization decides what that user may do, through access groups and access roles.
- Harness versus section
- A harness defines the overall screen layout and is selected by rule resolution. A section is a reusable fragment embedded in a harness or in another section.
- Repeating dynamic layout
- A layout that renders one row per item in a page list or page group, using a single template. It is the standard choice for displaying list data responsively.
- Flow action role
- A flow action supplies the UI for one assignment step. It references a section and controls which fields are editable, required, or visible during that step.
- Cosmos design system
- The default theme supplying the component library and styling. Custom components are added through the theme, not by editing individual harnesses or sections.
- Rule resolution order
- Class hierarchy from most specific to least, then ruleset list order, then circumstance (property, date, template), then rule availability. The first match wins.
- Situational Layer Cake
- Layered rulesets ordered Organization, Division, Unit, Application. A rule in a higher layer overrides the same rule in a lower layer, enabling reuse with targeted specialization.
- Ruleset branch purpose
- A branch isolates development work from the base ruleset. Merging the branch back requires resolving conflicts rule by rule before the changes reach other developers.
- Skim versus specialize by copying
- Skimming moves a class's rules to a parent so behavior is shared. Specializing by copying duplicates rules into a subclass so the subclass can diverge independently.
- Report definition types
- List reports return detail rows, summary reports group and aggregate, and interactive reports let users filter at runtime. The report's class determines which properties are available.
- Subreport versus join
- A subreport runs a separate query for each outer row and is slower on large data. A join runs as one query and is preferred when the related class is declared on the report.
- Mobile offline support
- Offline-enabled case types declare which data is cached on the device. Changes sync when connectivity returns, and conflicts are resolved by the configured conflict policy.
- Pega Mobile Client container
- A native wrapper that hosts the web application on the device. The same rules render the UI, so rule-only changes do not require a new native build.