What Pega Infinity builds automatically
One of the most significant advantages of a high-fidelity Pega Blueprint™ is the volume of application components that Blueprint import generates automatically. When you import a Blueprint, the system builds a substantial set of application components without manual configuration, establishing the foundation of the application. Before import, the Blueprint preview defines the intended application. After import, that definition becomes a running application in the development environment, using generated or simulated data to validate the outcome. Understanding what exists in this post-import state, and how it was created, helps delivery teams focus on work that requires human judgment instead of rebuilding what the platform already provides
The following table describes the primary building blocks of a Blueprint and is not exhaustive, as Blueprint features expand frequently:
Case Types, Data Types, and Personas
|
Case Type Rules: Blueprint import generates the full Case Type structure from the workflow definition: workflow Stages and Steps, including alternate Stages such as rejection flows; Step Views for Collect Information and Approval steps; the Case Data Model; and Assignment routing. These elements are not placeholder structures awaiting development. They are functional components aligned with the Blueprint design and ready to run at import. |
|
| Data Object Rules: Blueprint import translates the Data Model directly into data classes with property definitions, applies primary field highlighting to support summary panes, and establishes links to the systems of record that the Blueprint designates. Because Blueprint drives this generation, the resulting Data Model reflects actual business requirements rather than a developer's interpretation of them. |
|
| Personas and access control: Blueprint import generates access groups and Persona-specific access roles based on the Personas in the Blueprint. The import creates Portal rules for each channel (web, mobile, and email), along with workbaskets and work queues for each Persona. The access structure that the team agreed on during Blueprinting is present in the application at import. |
|
Sample data and user stories
To enable immediate testing, Blueprint generates realistic sample records for each Data Object at import. In parallel, Blueprint automatically converts components (including workflow steps, data fields, and notes) into work items in the backlog.
The following example shows a Training Course Data Object as defined in Blueprint and the sample records that Blueprint generates automatically at impor
Gap filling
Where the Blueprint does not specify certain structural elements, Pega Infinity™ applies intelligent defaults: creating default Views where none exist, recognizing patterns for alternate Stages, and applying standard naming conventions. This gap-filling behavior means the application runs immediately after import, even when the Blueprint contains areas that require further elaboration.
Draft mode
The import places Processes in draft mode, which means they run end-to-end even when configuration warnings are present. This design choice lets practitioners test and demonstrate the application immediately after import, without waiting to resolve every configuration detail.
Check your knowledge with the following interaction:
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?