Conversation
HCL Tech
IN
Last activity: 10 Feb 2026 9:00 EST
When would you not recommend using Blueprint?
I’m looking for guidance on scenarios where Pega GenAI Blueprint may not be the best choice.
For example, consider an existing Pega application that is already mature, and the new requirement is simply to add a single case type that isn’t a major change to the overall application. In a situation like this, would you still use Blueprint, or would it be better to design the new case type manually within App Studio?
I’d also be interested in hearing about any other situations where you would not recommend using Blueprint.
Pegasystems Inc.
US
@SatyajeethThakur Great question. I recommend using a blueprint for any new development, even if you're only adding a single case type or workflow. You can create a blueprint with just one case type and then extend your existing application from it.
Using a blueprint ensures cleaner architecture, better alignment with stakeholders, and reduces rework compared to building directly in App Studio.
Helpful links:
- How to create a blueprint with one case type: https://community.pega.com/conversations/blueprint-and-app-design/use-b…
- How to extend an existing application using a blueprint: https://docs.pega.com/bundle/blueprint/page/platform/blueprint/importin…
Tip: When extending, select Do not build to omit any unnecessary data objects or personas.
Pegasystems Inc.
US
@DeboliPaul The short answer is yes. The longer answer depends on which version of Pega you are using.
- If you are on 24.1 or later, you can export an existing application as a Blueprint. Once you have the file, it can be used as a supporting asset when creating a blueprint. Once you have the blueprint, you can alter the one or more of the case types. After that, download the Blueprint and use it to extend your existing application.
- If you are on an older version of Pega, we have a different method for you to use which we call heritage modernization, using the Application Signature tool.
I hope this helps! Let me know what you think after going through the materials.
Cognitonic Systems
AU
If the objective is to build a solution that extends existing industry frameworks such as Pega for Government, Smart Dispute, Smart Investigate, or similar packaged applications, it can be challenging to directly leverage Pega Blueprint. Blueprint typically generates a case lifecycle and application structure independently, without full awareness of the pre-configured processes, data models, and guardrails already embedded within Pega industry frameworks.
Industry frameworks are designed with predefined case hierarchies, integrations, data structures, and compliance-driven workflows. When Blueprint generates a new lifecycle, it may not align with these existing structures, which could lead to rework, duplication of functionality, or deviation from recommended framework implementation patterns.
However, Blueprint can still be valuable if used as a starting point for ideation and rapid prototyping. Teams can generate a baseline application design using Blueprint and then manually align or retrofit the generated lifecycle and components into the existing industry framework structure. This approach requires careful review to ensure adherence to framework standards, reuse of existing components, and maintenance of upgrade compatibility.
If the objective is to build a solution that extends existing industry frameworks such as Pega for Government, Smart Dispute, Smart Investigate, or similar packaged applications, it can be challenging to directly leverage Pega Blueprint. Blueprint typically generates a case lifecycle and application structure independently, without full awareness of the pre-configured processes, data models, and guardrails already embedded within Pega industry frameworks.
Industry frameworks are designed with predefined case hierarchies, integrations, data structures, and compliance-driven workflows. When Blueprint generates a new lifecycle, it may not align with these existing structures, which could lead to rework, duplication of functionality, or deviation from recommended framework implementation patterns.
However, Blueprint can still be valuable if used as a starting point for ideation and rapid prototyping. Teams can generate a baseline application design using Blueprint and then manually align or retrofit the generated lifecycle and components into the existing industry framework structure. This approach requires careful review to ensure adherence to framework standards, reuse of existing components, and maintenance of upgrade compatibility.
From a presales and sales perspective, Blueprint is particularly useful as a rapid solution visualization and design accelerator. It allows teams to quickly create conceptual application structures, demonstrate potential case flows, and showcase solution possibilities without needing access to a configured Pega environment. This significantly reduces setup time and enables faster client conversations, workshops, and demonstrations.
In summary, Pega Blueprint is a powerful tool for discovery workshop, early-stage solution design, presales acceleration, and rapid application conceptualization. The project delivery approach has evolved significantly, with Pega Express being replaced by a Blueprint-enabled delivery methodology. Start Blueprinting your customer journey in superfast way through Pega Blueprint!!!
Pegasystems Inc.
US
@Gaurav2105 I like your enthusiasm about blueprint! If you do not already, I encourage you to continue to read the blueprint release notes. We continue to add more features and it is now easy to extend customer service applications with blueprint.
I am curious if you have used the Application Signature tool for heritage modernization. If you have, I would like to hear your thoughts.