13.1 Pega Blueprint: Creating, Importing & Modifying an Application Design

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:

1. 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.
2. 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:

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.