Blueprint should be the starting point for any development effort with Pega applications. Whether you’re building a new solution or enhancing an existing one, Blueprint provides a structured, AI-powered approach to designing case types and workflows that align with industry best practices.
Need to add a new workflow to your existing application? No problem!
With Blueprint, you can quickly create a single case type tailored to your business need and seamlessly import it into your current application. This approach ensures consistency, accelerates delivery, and leverages Pega’s Center-Out™ architecture for scalable, maintainable solutions.
Here’s how the process works:
Create a New Blueprint:
Start by visiting the Blueprint Dashboard and selecting “Create a Blueprint.” Choose the relevant industry and sub-industry to ensure your design aligns with sector-specific requirements.
Define Your Case Type:
Enter a clear description for your new workflow. For example, if you’re adding a “Claims Escalation” process, specify its purpose and scope, and make that clear in the description that this is for one case type named Claims Escalation.
Review and Refine:
Blueprint provides a visual workflow editor where you can review, modify, and enhance the generated artifacts. You can adjust case stages, add steps, and configure data objects, integrations, and personas as needed.
Import into Your Application:
Once your blueprint is ready, download the file and use the “Extend Application with Blueprint” option in App Studio to import the new case type into your existing Pega application. This allows you to expand your solution without disrupting current functionality.
For a detailed step-by-step guide, refer to the attached pdf.
@garceLooks as easy as 1,2,3…4! I agree with you to start with Blueprint - always. It’s a mistake to think that Blueprint is ONLY for new applications.
Thanks for this post. It’s relevant to ALL Pega customers seeking to accelerate time to market, eliminate inefficiencies in the SDLC (it’s nearly 2026 now!), and reduce costs dramatically…which I believe is 100% of them.
@garce Thanks for sharing! The ‘semantic reasoning’ that is applied to only create one case type, is a great example of practical improvements to your Blueprint. I’m curious, how advanced is Blueprint in regards to this?
For example, is it able to interpret something such as: “do not add single value properties on the work class”,
or “define abstract data classes for xyz” (vs data objects)
or “make sure that a business rule is valid for all case types within the MyOrg-Namespace-Work hierarchy” (which could mean it is defined in MyOrg-Namespace-Work or the same business rule is repeated for all subclasses for which the Blueprint has created cases)?
It’s fun to test out these things to see what they trigger and trying to explain the why, but perhaps some most commonly used ‘magic semantics’ can be shared.
@BasRulesMatterThank you! It is fun to try out new ideas in blueprint. They continue to enhance and add functionality to blueprint. I imagine many of your suggestions will become configurations in future releases.
Your suggestion about the class structure really caught my interest. When the blueprint is imported, it puts all the case data model properties in the case class MyOrg-Namespace-Work-CaseType. I assume business rules are also put in the case class. I see the value in having that option as a configuration. Having business rules and even case properties in the Work class is good for reuse.