Study guide
13.1 Pega Blueprint: Creating, Importing & Modifying an Application Design
Pegasystems Certified Pega System Architect CSA
Track your progress as you read
Finished sections get a check mark.
1 Chapter 1: Exam Overview & Architecture Foundations
1.1 Certified Pega System Architect Exam Format, Blueprint & Strategy 1.2 Pega Architecture & Enterprise Class Structure (ECS) 1.3 Studio Environments: App Studio, Dev Studio, Admin Studio & Prediction Studio
2 Chapter 2: Case Lifecycle Design & Core Workflows
2.1 Case Types, Stages, Processes, and Steps 2.2 Routing Strategies: Worklists, Work Queues, and Teams 2.3 Service Level Agreements (SLAs) & Urgency Calculations
3 Chapter 3: Advanced Case Management Patterns
3.1 Multi-Step Processes, Parallel Processing & Sub-processes 3.2 Child Cases, Data Propagation & Wait Steps 3.3 Optional Actions, Approvals & Case Resolution 3.4 Duplicate Case Detection, Automation Shapes & Automated Correspondence
4 Chapter 4: Data Modeling & Data Page Architecture
4.1 Data Objects, Property Modes & Page Types 4.2 Data Pages: Scope, Types & Refresh Policies 4.3 Data Transforms & Object Mapping
5 Chapter 5: Business Logic, Calculations & Decisioning
5.1 Declare Expressions & Declarative Network Chaining 5.2 Decision Tables & Decision Trees 5.3 Integration Connectors, Systems of Record & Error Handling
6 Chapter 6: User Interface & User Experience Design
6.1 Traditional UI vs Constellation Architecture 6.2 Views, Dynamic Layouts, Design Templates & Action Sets 6.3 Form Validation, Edit Validate & WCAG Accessibility 6.4 Form Views: Default vs Hierarchical Forms, Field Groups & Primary Fields
7 Chapter 7: Rule Architecture & Rule Resolution
7.1 Rulesets, Versioning & Ruleset Stack Hierarchy 7.2 The Rule Resolution Algorithm 7.3 Circumstancing & Rule Specialization
8 Chapter 8: Security & Access Control
8.1 Authentication, Operator Records & Access Groups 8.2 Role-Based Access Control: Access Roles, ARO & Privileges 8.3 Attribute-Based Access Control (ABAC), Encryption & Audit Trails 8.4 The Security Checklist & Secure Deployment
9 Chapter 9: DevOps, Testing & Application Quality
9.1 Guardrail Compliance, Best Practices & Performance Profiling 9.2 Automated Testing: Pega Unit Test Cases & Scenario Testing 9.3 Packaging, Branching & Deployment Manager CI/CD
10 Chapter 10: Reporting & Operational Analytics
10.1 Report Definitions: Querying, Columns, Summaries & Joins 10.2 Filtering, Parameters & Column Exposure Optimization 10.3 Insights, Visual Dashboards & Business Metrics
11 Chapter 11: Mobility, Digital Channels & Portals
11.1 Mobile Channel Configuration & Offline Processing 11.2 Web Mashup, Digital Channels & Constellation Embed 11.3 Channels, Personas, Portals & Landing Pages
12 Chapter 12: Center-out Architecture, Enterprise Reuse & Agile Delivery
12.1 Center-out Business Architecture & the Case for Pega 12.2 The Situational Layer Cake, Modules & Enterprise Reuse 12.3 Agile Workbench, Workspaces, Branches, Delivery Roles & the Estimator
13 Chapter 13: Pega GenAI for System Architects
13.1 Pega Blueprint: Creating, Importing & Modifying an Application Design 13.2 Pega GenAI Autopilot & Pega GenAI Coach 13.3 Pega GenAI Connect Rules, Knowledge Buddy, Agents & Tool Rules
13.1 Pega Blueprint: Creating, Importing & Modifying an Application Design
Key Takeaways Explain This Topic AI
Pega Blueprint is a SaaS design tool that operates independently of the Pega Studios, so stakeholders can collaborate on an application design without a Pega instance or login.
You describe the application in business terms and Blueprint proposes case types, case life cycles, data models, data objects, and personas that you then edit to fit the requirement.
A finished Blueprint is exported and imported directly into Pega Platform, producing a functional starting application rather than a document.
Blueprint does not replace App Studio or the other Pega tools; it augments them by moving collaborative design earlier and making the output directly importable.
Every Blueprint suggestion is a starting point that the team must review and modify; Pega states explicitly that AI-generated recommendations should always be reviewed.
Last updated: September 2026
13.1 Pega Blueprint: Creating, Importing & Modifying an Application Design
Pega Platform '25 added Pega GenAI as a weighted exam domain in its own right, and the first objective in that domain concerns Pega Blueprint . The exam expects you to describe Blueprint's role in transforming application design and to know the create, import, and modify workflow.
1. What Blueprint Is
Pega Blueprint™ is a tool for rapidly and collaboratively designing the foundations of an application that fulfils a business need. Two properties distinguish it from everything else in the Pega toolchain:
It runs independently of the Pega Studios. Blueprint operates as a SaaS tool separate from App Studio and Dev Studio , so project stakeholders can collaborate on an application design without needing a Pega instance or a login . Stakeholders who do have a Pega login can still participate. That removes the single biggest bottleneck in early design — provisioning an environment for people who only need to discuss the design.
Its output is importable, not narrative. The result of a Blueprint session is not a requirements document that someone must then translate; it is a file that imports directly into Pega Platform.
Blueprint does not replace App Studio or other existing Pega tools. It augments them by offering a different surface for collaboration, turning ideas for workflow transformation into a functional application quickly.
2. What Blueprint Generates
You describe what you are trying to build in business terms . Blueprint uses that description to propose:
- Generated artifact What it is What you do with it
- Case types The units of work the application manages Rename, split, merge, or remove
Case life cycles Stages, processes, and steps for each case type Reorder stages, add compliance steps, delete stages that do not apply
Data models and data objects The entities and fields the cases operate on Correct field names and types, add missing attributes
Personas The user roles that interact with the application Confirm the roles, adjust which personas touch which steps
In Pega Platform '25 framing, after you describe the goals, Blueprint suggests an optimal Pega application design including case types, Live Data, and personas , and teams use it to turn application ideas into reusable, collaborative production applications — Pega describes outcomes delivered often within 90 days when the Blueprint is combined with enterprise system integration on the low-code platform.
You also receive best-practice application templates instantly , which is the mechanism by which a Blueprint-generated design starts inside the guardrails rather than needing remediation later.
- 3. The Create → Modify → Import Workflow
- Step 1: Create
Start a Blueprint and describe the business problem in plain language — for example, "a prior-authorization process for an outpatient surgical centre, with clinical review, payer submission, and appeal handling." Blueprint responds with a proposed application design.
Step 2: Modify
This is where the architect earns their keep, and where the exam's judgment questions live. Collaborators refine the design directly in the Blueprint interface: reordering stages, adding required compliance steps, correcting field types, removing personas that do not exist in the organization, and adding the data objects the generative model could not have known about.
Pega is explicit about the review obligation: AI-powered recommendations should always be reviewed before they are accepted. A Blueprint is a well-informed first draft, not a verified design.
Step 3: Import
Export the finished Blueprint and import the file directly into Pega Platform . The import creates the application scaffolding — case types, life cycles, data objects, and views — so the team starts building from a working application rather than from an empty one.
Step 4: Continue in App Studio
Once imported, ordinary development takes over. The imported case types are real rules: you refine views, add SLAs and routing, source data pages from real systems of record, configure security, and write unit tests exactly as Chapters 2 through 9 describe.
4. What Blueprint Does Not Do
Exam distractors in this area usually overstate Blueprint's reach. Hold these lines:
Blueprint does not connect to your systems of record for you. Integration is still designed and built in the platform.
Blueprint does not configure security. Access groups, roles, ARO, and privileges are platform work.
Blueprint does not replace the case life cycle design skills taught in Chapters 2 and 3 — it produces a draft that only an architect who understands stages, steps, and routing can evaluate.
Blueprint does not remove the review obligation. Accepting generated output unexamined is the failure mode Pega warns about in writing.
5. Exam Framing
A scenario typically describes an organization at project inception with business stakeholders who cannot get Pega environment access, requirements trapped in narrative documents, and pressure to show something working. The Blueprint answer is correct because of the specific properties : no Pega instance needed for collaboration, business-language input, generated case types and personas, and an importable result. Distractors that propose writing a requirements document first, building directly in Dev Studio, or exporting to a third-party diagramming tool all discard those properties.