Pega Certified System Architect flashcards
Pega Certified System Architect · Build recall with a focused review session.
32 cards. Read the term and the definition here. The deck at the top of this page is optional.
- Case type
- A case type defines a business transaction's lifecycle, data, and user interface; it contains stages, processes, and steps that organize work from creation to resolution.
- Stage
- A stage is a major milestone in a case lifecycle. It groups processes and controls which work is available during that phase.
- Process
- A process is a sequence of steps within a stage; it can contain assignments, automations, decisions, and subprocesses that complete a portion of the case.
- Assignment shape
- An assignment shape creates a task for a user or work queue. It defines the flow action, routing, and service level for the work item.
- Service level
- A service level sets goal and deadline time intervals for an assignment and specifies escalation actions that run when those intervals are exceeded.
- Work queue
- A work queue is a shared container of assignments. Users pull work based on routing, skills, and urgency rather than assignments being sent to a named operator.
- Subprocess shape
- A subprocess shape calls another process from the current flow. It can run synchronously or spin off asynchronously, depending on its configuration.
- Case locking
- Case locking prevents concurrent edits. Pessimistic locking locks a case when opened, while optimistic locking detects conflicting changes when the case is saved.
- Property mode
- Property mode defines whether a property holds one scalar value, one embedded page, an ordered page list, or a page group keyed by a value.
- Data page
- A data page is a named, automatically loaded clipboard page that retrieves data from a data source and can be scoped to thread, requestor, or application.
- Savable data page
- A savable data page allows write operations, so changes made to its clipboard page can be persisted to the underlying data source through configured mappings.
- Data transform
- A data transform maps values from source properties to target properties. It can set, append, remove, and update pages or lists during processing.
- Declarative processing
- Declarative rules such as expressions and constraints recalculate automatically when input values change, maintaining computed values without explicit procedural steps.
- Linked property
- A linked property stores a reference to another clipboard page. It lets rules access related data without copying all fields into the current page.
- Optimistic locking
- Optimistic locking allows multiple users to open a case but checks a version or timestamp at save time to detect conflicts before committing changes.
- Clipboard
- The clipboard is the in-memory store of property values and pages for a requestor. Data pages and case pages reside there during processing.
- Section
- A section is a reusable UI rule that groups fields and controls. Sections are placed in harnesses and layouts to compose an assignment's user interface.
- Harness
- A harness defines the overall layout and chrome for a case screen, such as perform, review, or confirm, and contains sections that display case data.
- Flow action
- A flow action defines the user interface and processing for an assignment. It specifies the harness or section, buttons, and post-processing steps.
- Visibility condition
- A visibility condition uses a when rule or expression to show or hide a UI element dynamically based on property values or other conditions.
- Action set
- An action set binds UI events such as click or change to actions. It can refresh sections, run data transforms, or navigate within the application.
- Dynamic layout
- A dynamic layout arranges fields in rows and columns and can reflow responsively. It supports inline, stacked, and grid presentation styles.
- Skin
- A skin defines the visual styling for an application, including colors, fonts, spacing, and component styles used across the user interface.
- Localization
- Localization adapts the user interface to a locale by using field value rules for translated labels and locale-specific formats for dates, numbers, and currencies.
- Access group
- An access group links an operator to an application, a default ruleset, and one or more access roles that determine available features and data.
- Access role
- An access role grants privileges and permissions to users. Roles are assigned through access groups and control access to rules, features, and data.
- Access control policy
- An access control policy is an attribute-based rule that evaluates conditions and attributes to permit or deny access to case data or actions.
- Operator ID
- An operator ID identifies an individual user. It stores credentials, personal details, and access group assignments used for authentication and authorization.
- SAML authentication
- SAML authentication enables single sign-on by exchanging signed assertions between an identity provider and the application, so users do not submit separate credentials.
- Property encryption
- Property encryption protects sensitive data by encrypting property values at rest using configured encryption keys, so stored values are unreadable without decryption.
- Production ruleset
- A production ruleset is a locked ruleset version used in production. Rules in it cannot be modified directly; changes require a new ruleset version.
- Audit trail
- An audit trail records changes and access events, often in history or log classes, supporting traceability and security investigations for case data.