Blueprint import scenarios
When you import a Pega Blueprint® file, Pega Platform™ uses the Blueprint Import module to create a complete application foundation, which generates Case Types, data models, integrations, Personas, and backlog items. The system applies default patterns, reuse decisions, and inferred logic to automatically produce these elements. As a result, teams can focus on refining the application instead of building everything from scratch. This process acts as a translation layer between design intent and implementation, converting Blueprint elements into executable Rules, structures, and configurations that form a working application baseline.
High-fidelity dependencies
The accuracy of this automated generation depends on the quality of the Blueprint. A high-fidelity design provides clear definitions for workflows, data objects, and Personas, allowing the module to generate artifacts that closely reflect the intended solution. When details are missing, the Blueprint Import module fills in gaps using default patterns and best practices, which can introduce assumptions and require additional refinement after import. Using the latest version of the Blueprint Import module is equally important, as the system can interpret newer Blueprint capabilities and generate more advanced artifacts, Rules, and integrations enabled by recent Pega Platform enhancements.
For example, when a Blueprint defines a Case Lifecycle and Personas but does not fully specify assignment logic, the Blueprint Import module generates the complete Case structure, including Stages, Steps, assignment routing, and baseline decision Rules based on Persona alignment. Similarly, when a Blueprint references external data without defining the technical implementation, the module generates the supporting data types, Data Pages, connectors, and Data Transforms needed to establish integration scaffolding. In both situations, the module fills in the gaps by producing a functional implementation that developers can validate and refine, ensuring rapid progression from design to working application.
Automatic gap filling
While the Blueprint Import module establishes a strong application baseline, it does not produce a fully deployment-ready solution. Certain elements require contextual configuration and refinement during the Authoring phase, where Solution Builders validate assumptions, align the application with enterprise standards, and complete details that cannot be inferred from the Blueprint design alone. These gaps often involve requirements that depend on the target environment, organizational policies, or external systems.
During Authoring, teams complete key configurations such as:
- Refining Case processing logic and business rules.
- Configuring integrations, including authentication, endpoints, and error handling.
- Finalizing assignment Views, validation logic, and user experience details.
- Aligning security and access controls with enterprise requirements.
- Validating data models and generated artifacts.
- Completing testing preparation, CI/CD configuration, and governance activities.
This work transforms the imported application from a functional baseline into a production-ready solution that meets business, technical, and operational requirements.
Check your knowledge with the following interaction:
This Topic is available in the following Module:
Quer nos ajudar a melhorar esse conteúdo?