Extending the existing Case Type created from the blue print

Blueprint and App Design
1

Consider, I have created a New Application which is Build from a Blueprint (having one Case Type).

Now I have modified the existing Blueprint and modified the same case type by adding more steps or by removing the existing steps , when i am importing the updated blueprint with the option Extend from Blueprint, and while importing i chose the case type build option as “Use existing”, after the build the system is not creating the rules with new changes, it is just creating a New branch with no rules in it.

2

I believe I had the similar experience. My understanding is that Pega treats the existing Case Type in our application as the source of truth. Selecting “Use existing” instructs the import process to retain the current Case Type rather than regenerating or overwriting it. This might be desirable because the existing Case Type may have been customized manually in Dev Studio, and the system avoids replacing those changes during the import.

3

This is expected, when we did in person events this was talked about in detail.

image
image1920×1199 171 KB

It is mentioned in our docs and other trainings as well.

Pega Docs

Pega’s documentation outlines that when you import a Blueprint, any matching assets must be updated manually because the import engine does not automatically merge structural updates to pre-existing workflows or schemas:

* Manual Synchronization Guideline: "When using existing assets, manually synchronize properties and permissions between the Blueprint and the application, because import does not automatically update existing structures."

https://docs.pega.com/bundle/blueprint/page/platform/blueprint-delivered/understanding-blueprint-import-process.html

Webinar

There is also a webinar on the topic BA/CLSA Community: Delivering with Pega GenAI™ Blueprint - Series Introduction | Pega the answer has not changed since this was published.

“Does Blueprint support iterative development? Can I update a case type using blueprint after initial development?”

  • "Today, on 24.1.1, you can add new case types to existing apps, but not yet change existing case types."
4

As @MarcCheong mentioned, this is expected behavior. Selecting"Use Existing" tells Pega to reuse the existing Case Type and not apply lifecycle updates from the Blueprint. Blueprint extensions are best suited for introducing new Case Types, Data Objects, and Personas, not for updating an already imported Case Type with modified stages or steps