Watch the replay here:

On the 31st July 2025 we hosted an engaging webinar that explores how to build high-fidelity blueprints using Pega’s Blueprinting approach—from creative ideation through to delivery-ready design. You'll learn how to define your vision, structure case types, capture detailed workflows, and connect data and integrations.

The webinar covers best practices for engaging stakeholders, configuring personas, previewing and refining blueprints, and accelerating app delivery through import capabilities. Alongside expert insights and live demos, the webinar showcases how Blueprint forms the creative foundation for confident, collaborative, and efficient project delivery.

During that session we had a really engaged audience asking many questions check them out below:

📋 Blueprint Fundamentals & Getting Started

Q: How does Blueprint work with headless applications?

A: Blueprint's primary focus is on building the processes and data structures needed to achieve business outcomes, rather than UI components. It excels at designing and streamlining processes through Stages and Steps – elements that remain essential even in headless scenarios. If your business outcome doesn't require a Pega UI, all Blueprint steps remain relevant except perhaps the PREVIEW capability, which is UI-focused.

🔗 Learn More: Pega GenAI Blueprint Overview

Q: Is Blueprint available for on-premises customers with security concerns?

A: Security is a top priority that the product team actively addresses. Currently, Blueprint operates in the cloud with robust security measures: you own the blueprints you create and control sharing permissions. We also offer SSO integration for customer authentication on Pega Community sites.

An important consideration is Blueprint's rapid evolution – even with an on-premises option, customers would need to apply frequent patches to stay current, something automatically handled in the cloud version.

🔗 Learn More: Pega GenAI in Pega Cloud

Q: Does Blueprint consider CRM, CLM, or Service Desk frameworks when generating suggestions?

A: The product team is actively working to incorporate more strategic application frameworks into Blueprint's AI suggestions. Currently, Blueprint provides generic application designs with case types and personas, but enhanced integration with our strategic applications is planned for future releases.

🔗 Learn More: Building an Application with Blueprint

🤖 AI Capabilities & Prompting

Q: Should I focus on good prompting techniques or functional descriptions?

A: Focus on clear functional descriptions rather than worrying about perfect prompting. Blueprint offers multiple ways to enhance your initial input:

• Upload supporting assets: Import flow diagrams from tools like Mural, and Blueprint will recognize and generate different Case Types accordingly
• Iterative refinement: After initial processing, you can add case types, update descriptions, and upload BPMN process diagrams
• AI-assisted evolution: Blueprint uses updated information to suggest and revise Stages and Steps

Remember, Blueprint may not deliver your exact vision initially, but it highlights considerations you might have missed. You can then select preferred elements, remove unwanted pieces, and add missing components.

🔗 Learn More: Creating a Blueprint

Q: How can I transform an existing Pega application using Blueprint?

A: Several approaches are available for application transformation:

1. Export to Blueprint: Use the built-in export functionality (contact support if experiencing timeouts)
2. Screen capture method: Record video demonstrations of your application in action – these videos can serve as Blueprint input
3. Documentation approach: Screenshot process flows and data types for reference during Blueprint creation

🔗 Learn More: Working with Blueprints in Pega Platform

🔄 Iterative Design & Best Practices

Q: Aren't we at risk of "paving existing cowpaths" when starting with demos or BPMN diagrams?

A: Excellent point! The key is leveraging multiple iterations to reimagine processes:

1. First iteration: Use existing documents/BPMNs to understand current state
2. Second iteration: Describe expected outcomes without existing constraints
3. Compare and contrast: Analyze both approaches for the same problem statement
4. Keep it simple: Focus on Ideate → Trial → Compare → Contrast

This approach helps you avoid simply digitizing existing inefficiencies while leveraging valuable institutional knowledge.

Q: Should Blueprint encourage more case types than traditional development approaches?

A: Blueprint will suggest case types based on your business description, but stakeholder collaboration determines what moves forward. It's perfectly acceptable to delete, add, or refine suggested case types. The key is collaborative decision-making among all stakeholders.

Upcoming Feature: Case type merging capability is currently in development to help consolidate related case types.

📊 Case Design & Management

Q: Can I add new case types to an existing Blueprint and deployed application?

A: Yes, absolutely! Here's how:

1. Within Blueprint: Click the Workflows tab to add more case types to existing blueprints
2. Alternative approach: Create a new blueprint with additional case types
3. Import process: Use "Extend Application from Blueprint" to import new case types into existing applications
4. Selective import: Choose which case types and data classes to import, giving you full control over the extension process

Q: How does AI decide between multiple case types versus parent-child relationships?

A: AI generates multiple case types based on your application description, but the team collaborating on the blueprint makes final decisions about:

• Which case types to implement
• Parent-child relationships between case types
• Overall case architecture

The collaborative aspect is crucial – Blueprint provides suggestions, but business stakeholders determine the final structure.

Q: Can I leverage existing BPMN flow diagrams for new lifecycle requirements?

A: Absolutely! Blueprint supports BPMN integration in multiple ways:

1. Initial upload: Include BPMN diagrams during blueprint creation
2. Iterative refinement: Upload new BPMN diagrams to existing case types
3. Regeneration: When you upload updated BPMN processes, Blueprint regenerates stages and steps incorporating the new flow logic

This flexibility allows you to refine requirements iteratively while maintaining process integrity.

Q: Can I add case types later using the same blueprint?

A: Yes, Blueprint supports ongoing case type additions throughout the design process. You can add new case types at any time and configure them as needed.

🔗 Data Modeling & Integration

Q: How should I handle data model discussions with clients who find them too technical?

A: Here's a practical approach to keep clients engaged:

Current Recommendations:

• For each "collect information" step, document: what data you're capturing and what data users need to see for decision-making
• Mark fields as integration-sourced without worrying about specific sources initially
• Work with services teams to identify available data sources after collecting business requirements

Upcoming Enhancements:

• Blueprint will suggest proper data structures for case type data
• Automatic segregation of integration vs. non-integration data
• Enhanced tools to facilitate discussions with service SMEs

🔗 Learn More: Understanding Data Modeling Concepts

Q: How do I balance case type data models with reusable data objects?

A: The data model generates as you work on case stages and steps, allowing for continuous refinement. The key is collaboration between business and IT teams throughout the evolution process. Blueprint encourages this collaborative approach where both perspectives contribute to data model development.

Remember: Blueprint puts workflow before data model intentionally, but both should evolve together through stakeholder collaboration.

Q: Does Blueprint recognize and recommend new data structures added on-the-fly?

A: Yes! When you add new case types with descriptions, AI suggests structures for them. Similarly, updating case type descriptions triggers Blueprint to ask if you want to regenerate stages and steps based on the new information.

Q: Will Blueprint import automatically include the common data model?

A: This is currently under discussion by the product team. They're evaluating the best approach for common data model integration during the import process.

🔐 Security & Data Privacy

Q: How is client data kept private when importing legacy application data?

A: Blueprint maintains enterprise-grade security through multiple layers:

Storage Security:

• Files (PDFs, BPMN models) are encrypted at rest in private cloud storage
• Option for customer-managed S3 repositories
• 256-bit encryption with TLS protection

Privacy Controls:

• Blueprints are private by default – visible only to creators unless explicitly shared
• No AI training on your data – content generates blueprints but isn't retained by LLM providers
• SSO and access controls ensure only authorized organizational users access data

Compliance:

• Data remains in-region (UK, EU, US) for residency requirements
• Full Pega Cloud security stack including threat monitoring and disaster recovery
• Your data stays yours – private, protected, and compliant

🔗 Learn More: Pega GenAI in Pega Cloud Security

Q: Are there plans for enhanced security configuration with Data Objects and Personas?

A: Yes! The product team is developing more comprehensive security enhancements beyond current capabilities. Blueprint already generates security configurations from imported personas based on your configuration choices, and additional security features are planned.

🏢 Strategic Applications & Industry Focus

Q: Should Blueprint recommend Smart Investigate, Smart Dispute, or CLM based on application functionality?

A: Blueprint can leverage strategic applications through industry selection. For example:

• Choosing Banking → Retail Banking → Financial Crime provides pre-existing application purposes
• These selections can pull suggestions from strategic applications like Smart Investigate or Smart Dispute
• Industry-specific templates help align Blueprint suggestions with proven patterns

This approach ensures Blueprint recommendations align with established Pega strategic application best practices.

🤝 Collaboration & Version Control

Q: Is version control available within Blueprint?

A: Currently, Blueprint doesn't support formal version control, but offers workarounds:

Current Options:

• Use the 3-dot menu to duplicate blueprints before sharing
• Manage versions through descriptive blueprint naming
• Create backup copies before major changes

Future Development:

• Version control is on the product team's feature backlog
• Formal versioning capabilities are being evaluated

🔗 Learn More: Pega GenAI Blueprint Release Notes

Q: How do we ensure cross-team collaboration during blueprint creation?

A: Blueprint supports collaboration through:

• Invitation system: Invite team members to edit blueprints collaboratively
• Shared editing: Multiple stakeholders work on the same document simultaneously
• Version management: Duplicate blueprints to maintain version 1, 2, 3 as needed
• Real-time collaboration: Teams can work together even without a Pega instance

⚙️ Processing Logic & Advanced Features

Q: How should I handle decision shapes and multiple outcomes in Blueprint?

A: Current best practices for decision shapes:

Documentation Approach:

• Use notes sections extensively to document decision outcomes
• For each decision, document what happens for different paths
• Capture automation steps or collect steps for each decision outcome

Upcoming Enhancement:

• Multiple processes per stage capability is in development
• This will allow better grouping of steps and clearer referencing in notes

Complex Logic Recommendation:

• For complex processing logic, diagram flows using Visio or Mural first
• Use these diagrams to strategically choose Blueprint implementation approach
• Identify primary stages and alternate stages based on your flow diagrams

Q: Are there plans for technical configuration like SLAs and decision logic directly in Blueprint?

A: Yes, these capabilities are in the feature backlog for future releases. The product team is working on incorporating more technical configuration options directly within Blueprint.

🔌 Integration & Microservices

Q: How are microservices or API layers handled within Blueprint?

A: Blueprint supports microservices architecture through strategic data organization:

Design Approach:

• Create classes for each microservice content area (understanding non-flat structures)
• Align/define service calls into larger entities for better organization
• Group related microservices (e.g., Account Services) into dedicated applications

Import Strategy:

• Create separate applications for different service domains
• Use selective import to choose specific elements for each application
• Import account-related content to account applications, other content to separate applications

This approach maintains microservices architecture while leveraging Blueprint's organizational capabilities.

📈 Reporting & Analytics

Q: Will Blueprint generate reporting capabilities when detailed reporting information is provided?

A: Reporting enhancements are on the product backlog with planned capabilities:

Planned Features:

• Describe business needs and expected outcomes/actions from reports
• Help match reporting needs with optimal solutions (reports aren't always the best approach)
• Potentially identify report attributes (still being determined)

Philosophy: Blueprint will help identify the best approach to meet your information needs, which may include reports, dashboards, or other solutions depending on the specific business requirement.

📥 Import & Application Development

Q: Is importing intended as one-and-done or an iterative Blueprint-driven process?

A: The vision is to get you significantly closer to release-ready applications post-import. While some work remains after import, Blueprint continues evolving to handle more development tasks automatically.

Current State:

• Import provides a strong foundation requiring minimal post-import work
• Continuous Blueprint enhancements reduce manual development needs

Future Direction:

• More automated application generation
• Reduced post-import development requirements
• Enhanced Blueprint-to-production workflows

Q: How are conflicts handled when uploading blueprints incrementally?

A: Blueprint follows these conflict resolution principles:

Import Rules:

• Once a case type is imported, update it in place rather than re-importing
• Imported data classes cannot be imported over again
• Use "Extend Application from Blueprint" for adding new elements

Best Practices:

• Plan your import strategy to minimize conflicts
• Use selective import to control which elements are brought into existing applications
• Maintain clear separation between new and existing components

🎯 Project Sizing & Estimation

Q: How do Blueprint and the estimation tool work together with App Studio?

A: Pega offers an integrated approach to project estimation:

Estimation Tool Integration:

• Pega has a new estimation tool that leverages Blueprint files
• Available to Pega employees and partners
• Provides effort estimates based on Blueprint designs

Learning Resources:

• Academy course available in the estimation tool header
• Comprehensive training on Blueprint-to-estimation workflows

🔗 Learn More: Check the Academy course referenced in the estimation tool for detailed guidance on this integration.

💡 Community Engagement

Q: Where can I get ongoing support and ask detailed questions?

A: The Expert Circle is your primary resource for continued Blueprint support:

• Post detailed questions as you experiment with Blueprint
• Access community expertise and best practices
• Get responses from Blueprint experts and fellow practitioners
• Stay updated on new features and capabilities

🔗 Join the Community: Pega Community Expert Circle

🔍 Quality & Fidelity

Q: Is there a vision for flagging desired or achieved fidelity within blueprints?

A: Yes! The product team is developing a "Fidelity Progress Bar" that will:

• Help understand if required fidelity has been reached
• Track completion across different blueprint areas
• Include additional questions to assess blueprint completeness
• Provide clear indicators for stakeholder communication

This feature will help teams determine when blueprints are ready for import versus needing additional refinement.

This Q&A compilation represents insights from our Project Delivery with Pega GenAI Blueprint webinar. For the most current information and detailed documentation, please refer to the official Pega documentation links provided throughout this discussion.

🔗 Additional Resources:

• Pega GenAI Blueprint Overview
• Blueprint for Accelerated Application Design
• Working with Blueprints in Pega Platform
• Pega Community