Extending Existing Application to add New case type in the Application

[Nagamani20 (nagamani nalabolu)]

Consider, I have exported existing Application as blueprint file.

Now I have modified the existing Blueprint and added new case type. When i am importing the updated blueprint with the option Extend from Blueprint, and while importing i chose the case type build option as “From Blueprint” and proceed with Data object, personas and Review screen. In Review screen, set case type name. After submitting the screen, Pega try to create new application instead of adding new case type in existing application.

We are using Pega infinity 25.1.2 version.

[MarcCheong]

@Nagamani20 there are two options to import your Blueprint, it sounds like you are using Create new Application? You should be using Extend this Application.

This is from Infinity '26, if you are in Infinity '25 it looks like

There’s some great videos on the topic:

• Import: Extending an Existing Application with Inheritance (MLP 1) | Pega
• Import: Incrementally Extending with Blueprint‑Defined Workflows (MLP 2) | Pega

[VenkateswararaoK (Venkateswararao Kurra)]

Hi @MarcCheong

I am a bit confused about the Extend Application with Blueprint options. Please correct me if my understanding is wrong:

1. If I want to add a new Case Type from the same Blueprint that does not currently exist in the Development Application, should I choose “From Blueprint with Inherited Assets”?
2. If I want to add a new Case Type from a different/new Blueprint that does not currently exist in the Development Application, should I choose “From Blueprint”?

Also, could you please explain the purpose of the “Copy Life Cycle from Inherited Case Type” checkbox?

• What gets copied into the new Case Type when this checkbox is selected?
• What is excluded when the checkbox is not selected?
• How does the resulting Case Type differ with and without this option?

Thanks in advance for your clarification

[MarcCheong]

The videos go into great detail to explain this, but I’ll summarise:

1. From Blueprint - will build whatever is selected form the Blueprint file. E.g. Build my “audit” case type
2. From Blueprint with Inherited Assets still builds the case type you selected BUT adds an inheritance path of the case type being created. E.g. Make my Audit case type, inherit from my Compliance case type.
   1. 
3. Copy case lifecycle: This only shows if you use Blueprint with Inherited Assets and it’s a case type. If copies the case lifecycle from your existing assets AND ignores the version in your Blueprint
   1. Under the hood, it copies the pyDefault of the case type, so the case that is created will have the same lifecycle as your existing assets, it will have the data model of the Blueprint.
   2. In my opinion, this is niche and less likely to be used.
   3.