Generating a Pega Blueprint

To define the context of your application, begin by selecting your primary industry from the available options. Each industry selection unlocks specialized templates and compliance considerations relevant to your domain. 

In the following image, Banking is the selected industry:

Narrow your focus by selecting a sub-industry and specific department or function in your industry. This refinement ensures that suggested Case Types and workflows match your operational reality.

In the following image, Retail Banking is the selected sub-industry:

In the following example, the Blueprint pertains to Retail Banking and the Lending Department, which Blueprint uses to generate loan-specific workflows and Data Models.

After you establish your application's general context through industry and sub-industry selection, provide specific details about your application's purpose and functionality, as shown in the following image:

The Application purpose input field offers two options:

• Pre-built templates: Select from industry-tested solutions that incorporate proven best practices.
• Pega GenAI solutions: Let Blueprint's AI create custom designs based on your unique requirements.

The form includes several input fields that help define your application's specific context:

• Application purpose: Select and start from pre-built industry-specific templates or enter your application's unique purpose.
• Functional description: Provide detailed information about your application's functionality and requirements (consider using the What should I write? option for guidance on what to include).
• Organization name and Language: Specify your organization details and preferred language for the application.

Use the Upload supporting assets feature to provide additional context for the application. You can upload documents that contain detailed requirements, existing process flows, or other relevant information that will help Blueprint generate more accurate and tailored suggestions for your specific use case.

Blueprint provides users with a starting point for application creation. It uses the context of the provided application and applies Pega Platform™ development best practices to suggest templates (such as Case Types and Lifecycles, Data Models, and Personas) that guide the initial design.

As shown in the following image, Blueprint proposes Case Types based on your application's context. Each suggestion includes a description explaining its purpose and typical use cases within your domain:

The following customization options are available:

• Add Case Types: Click Add a Case Type to include additional workflows specific to your needs.
• Remove Case Types: Click the More icon to delete suggested Case Types that do not apply to your use case.
• Modify Case Types: Edit Case Type descriptions to better reflect your business processes.

Each Case Type requires a detailed Case Lifecycle that maps the user's journey from Case creation to resolution. Blueprint generates comprehensive workflows that you can customize to match your specific business processes.

For each Case Type, Blueprint suggests a Case Lifecycle organized into Primary Stages, Alternate Stages, and detailed Steps. The following image displays a Case Lifecycle Blueprint suggested for a Home Loan application Case Type:

The Case Lifecycle tab includes the following customization options:

• Add or remove Stages: Add Primary or Alternate Stages to match your business sequence.
• Add or remove Process: Include additional Process to a Stage as required by your organization.
• Add or remove Steps: Include or Delete additional Process Steps to streamline workflows.

Keep in mind the following best practices for Case Lifecycle design with Blueprint

1. Define application context with accurate industry, purpose, and description.
2. Align Case Types to microjourneys and clarify relationships, statuses, and personas.
3. Ensure lifecycle completeness with a logical start, Resolution Stage, and exception paths.
4. Document details such as routing, Service-Level Agreements, and conditions by using Notes.
5. Validate design by clicking Preview my app to confirm flow and usability.
6. Optimize the Data Model of the Case with correct fields, types, and descriptions.
7. Reference accurate Data Objects and specify sources or systems of record.
8. Validate personas and include Channels, Portals, and landing pages in descriptions.
9. Review Blueprints with stakeholders and check reuse before importing into Pega Platform.
10. Leverage Agile Workbench after import to generate backlog items from Blueprint details.

The Data Model for the Case determines what information your application captures, stores, and processes. Blueprint generates field suggestions based on your Case Types and industry standards.

For each Case Type, Blueprint suggests a Case Lifecycle organized into Primary Stages, Alternate Stages, and detailed Steps. The following image displays a Case Lifecycle Blueprint suggested for a Home Loan application Case Type. This structured view complements the Case Data Model View, which displays all suggested fields with their types and descriptions, ensuring that process flow and data capture align with business needs.

The Case Data Model tab includes the following customization options:

• Add fields: Include additional data points specific to your requirements.
• Modify Field Types: Adjust Data Types to match your validation and processing needs.
• Edit descriptions: Clarify field purposes for development teams.
• Set Primary Fields: Identify key fields that will drive application logic.
• Set Number of Records: Identify if filed references a Single value or Multiple values. 
• Set field capture: Identify source of the field as User input or a Calculated value. 

Personas represent the different types of users who will interact with your application. Blueprint suggests relevant Personas based on your industry and Case Types, ensuring your application design considers all stakeholder perspectives.

For each Case Type, Blueprint also suggests relevant Personas: user types who participate in the workflow, along with their roles and responsibilities. The following image displays the Personas Blueprint recommended for a Home Loan application, which helps clarify who interacts with the Case and how:

The following customization options are available:

• Add Personas: Include additional user types specific to your organization.
• Modify descriptions: Adjust Persona descriptions to match your organizational structure.
• Define access levels: Consider what each Persona needs to see and do within the application.
• Define Channels: Select the Channels the Persona has access to.
• Release planning: Select release and effort required. 

Pega Blueprint consolidates all your design decisions into a comprehensive summary that serves as both a reference document and an export package for development teams.

At the end of the Blueprint process, the Summary page provides a complete, section-by-section overview of the suggested application artifacts, making it easy to review and validate Case Types, Data Models, Personas, and other key elements before moving forward, as shown in the following image:

Final review checklist:

• Verify all Case Types align with your business processes.
• Confirm Data Models capture necessary information.
• Validate Personas represent all user types.
• Check integration requirements are complete.

After reviewing the suggested application artifacts, you can opt how to proceed, whether by launching a live demo to generate a working application, downloading the Blueprint for use in Pega Infinity™, or saving a PDF summary for reference.

Blueprint also has the ability to create a Pega Platform instance from the Blueprint site with your Blueprint-generated application automatically imported:

The following export options are available:

• PDF summary: Generate a comprehensive document for stakeholder review and project documentation.
• Blueprint file: Export a technical file (.blueprint) that can be imported into Pega Infinity for rapid application development.
• Revision history: Track changes and maintain version control for collaborative projects.

Check your knowledge with the following interaction: