Follow the Blueprint import journey
The team has established Blueprint Readiness, preserved the validated Case in an agreed Blueprint version, and confirmed progression into Authoring. The focus now moves from confirming readiness to progressing that agreed design into a working application foundation while preserving its outcome, relationships, rationale, and business intent.
The Solution Builder leads the import. The Solution Designer follows the journey from the perspective of the business evidence each decision requires, the connected design it affects, and the meaning that must remain recognizable in Pega Infinity™.
Tip: Follow the agreed outcome through the import journey. At each decision, make clear what the selected design must contribute and which business meaning and relationships must remain recognizable.
Begin from the agreed Blueprint position
The agreed Blueprint version provides the design reference for import. It communicates:
- The agreed outcome and increment
- Connected Case Design and Workflow
- Data and information used by the Case
- Participant responsibilities and access needs
- Significant Decisions and integrations
- Dependencies
- Delivery boundaries
- Rationale
- Owned questions that continue into Authoring
Import choices and later refinements are evaluated against this agreed position.
Import begins from the Blueprint Readiness already established. The agreed position now determines which design progresses and how it should contribute to the application foundation.
Think in connected design containers
Blueprint import does not progress isolated labels into an application. A selected Case Type represents its Workflow, Views, Case Data Model, Decisions, and relationships. A selected Data Object represents its Fields, business meaning, source intent, and relationships. A selected Persona represents participant responsibilities, Case and Data Object access, routing needs, and Channels.
The Solution Designer therefore helps the Solution Builder look beyond each item selected in the import experience. The relevant question is not only, “Should this item be included?” It is, “What connected design does this item carry, and what else must progress with it for the outcome to remain coherent?”
The following figure shows how Case Types, Data Objects, and Personas work together to define a connected application design:
Recognize the target application context
Before evaluating individual import choices, establish where the agreed outcome will be implemented. The application context determines which established capabilities are visible, which import choices are available, and how imported assets can relate to existing application layers.
| Application context | What the Solution Designer makes clear | What the Solution Builder evaluates |
|---|---|---|
| New application built on Pega Infinity | The outcome and connected design that must provide the application starting point | Application structure, naming, class design, and which Blueprint items to build now. |
| Extend an existing application | What is new, what already exists, where the same business purpose is already served, and what must remain specific. | Whether selected items should be created, inherited, redirected to existing assets, or deferred. |
| New application built on an established application or reuse layer | Which established capabilities provide a reusable basis and where the new outcome requires specialization. | Application layering, inheritance, available reuse choices, and the class structure of the new application. |
The Solution Designer does not choose the technical architecture. However, the Solution Designer must understand the selected context well enough to explain the business boundaries, existing value, dependencies, and meaningful variation that the architecture must support.
Tip: Successful collaboration relies on distinct responsibilities. The Solution Designer defines the outcome and supporting business rationale, while the Solution Builder determines the application's structure and technical implementation.
Follow the import journey
The available choices depend on the application context. The following journey shows where the Solution Designer contributes business evidence as the Solution Builder progresses from the agreed Blueprint through selection, review, import, and examination of the result:
| Import stage | Solution Designer contribution | What the Solution Builder establishes |
|---|---|---|
| Select the Blueprint | Confirm the agreed version and the outcome and increment it represents | Which agreed Blueprint version provides the design source for the import. |
| Confirm the application context | Explain relevant business boundaries, established capability, and active dependencies. |
The target application context in which the selected design will be established, including whether any existing application capability can support the business objective for this import. |
| Select the Case Type design | Explain the outcome, Case purpose, Workflow, Decisions, and connected design that must remain recognizable. | Which business outcome and Case journey should progress. |
| Resolve connected Data Objects | Explain the business meaning, relationships, source intent, ownership, and reuse evidence for the required data. | Which data structures and references are required to support the selected Case Type. |
| Select the required Personas | Explain participant responsibilities, Case and Data Object access needs, routing intent, and Channels. |
The roles, access policies, and Work routing requirements for each Persona. |
| Determine how each item contributes | Provide evidence about shared purpose, meaningful variation, dependencies, and what must remain specific to the outcome. | Whether the application foundation should use Blueprint design, established capability, or a combination of both. |
| Review the proposed foundation | Confirm that the selected design and relationships tell one coherent business story. | Whether the complete set of decisions supports the agreed outcome before import runs. |
| Examine the imported result | Evaluate whether the agreed outcome and business meaning remain recognizable as Authoring begins. | What Pega Infinity established from the Blueprint design and import decisions. |
Progress one coherent outcome and its dependencies
A Blueprint may represent several business outcomes and delivery increments. Progress one outcome, or a small set of closely related outcomes, at a time. Begin with the Case Type or Case Types required for the current increment, then follow their relationships to identify the Data Objects, related Case Types, Personas, Decisions, integrations, and other dependencies needed to keep that outcome coherent.
This focused approach allows the team to review the imported result as one connected business story, learn from the import and validation work, and apply those lessons before progressing the next outcome. Design for later outcomes remains in Blueprint until its agreed delivery point.
The following figure shows how a focused outcome is designed, validated, and refined:
Tip: Walk the selected outcome from its Case Type through every relationship required to make that outcome coherent. Bring the complete connected design into the import conversation before individual choices are finalized.
Look beyond each selection
Each selection represents connected business design, not an isolated item. Understanding that design enables the Solution Designer to explain to the Solution Builder what the selection must contribute and the consequences of the import choice.
| Selection | Connected design represented | Why the choice matters |
|---|---|---|
| Case Type | The business outcome, Case Lifecycle, Stages, Processes, Steps, Workflow, Views, Case Data Model, Decisions, and related design supported by the import capability. | The choice influences the working Case journey and the business behavior that provides the starting point for Authoring. |
| Data Object | Business data, Fields, Primary Fields, relationships, source intent, and supporting design represented in Blueprint. | The choice influences which data structures are created or referenced and how the selected Case Type obtains the data it needs. |
| Persona | Participant responsibilities, Case access, Data Object access, routing intent, Channels, and other supported Persona settings. | The choice determines whether the Persona represented in Blueprint is created in the application foundation during this import. Current import guidance presents From Blueprint and Do not build for Personas. |
Version awareness: Import behavior depends on the Blueprint Import Module available in the target environment. Blueprint and the import capability can evolve on different schedules, so not every part of the current Blueprint design is necessarily supported by the installed module version. Before import, the Solution Builder confirms the applicable module and technical implications. The Solution Designer remains aware of those limitations because they affect what should be expected during fidelity review.
Export the agreed Blueprint as close as practical to the import activity so that the import source reflects the current agreed design. The agreed Blueprint remains the reference for intended business design while the Solution Builder evaluates technical implications.
Understand what import establishes
Once the decisions are submitted, the Blueprint Import Module combines the selected Blueprint design with the Solution Builder’s choices to establish a runnable application foundation in Pega Infinity. The result depends on the Blueprint Import Module version, application context, selected choices, and supported design.
The foundation may include supported Case Type structures, Workflow elements, Views, Case and Data Models, Fields, Data Objects, Personas, access-related assets, Channels, Decisions, relationships, sample or simulated data, and implementation or backlog context derived from Blueprint descriptions and Notes. Treat the result as a runnable foundation to examine and refine, not as proof that every element represented in Blueprint transferred unchanged.
The following figure shows how Blueprint import decisions and application context settings contribute to an application foundation in Pega Infinity:
Tip: Collaboration through import continues even as leadership shifts to the Solution Builder. The Solution Designer keeps the agreed outcome, rationale, relationships, dependencies, and stakeholder expectations visible.
This Topic is available in the following Module:
If you are having problems with your training, please review the Pega Academy Support FAQs.
Want to help us improve this content?