Conversation
Eclantiqx
IE
Last activity: 14 Oct 2025 8:26 EDT
Is the only way to utilize blueprint for existing application is by extending application feature?
HI all,
We have an application already built and in production for more than couple of years.
Client is really impressed by the accelerated design and development showcased by blueprint.
As we checked, we must allow the pega to build a ready for blueprint export and then utilize this and our documents to create and customize and application in blueprint and extended application to pega platform.
But client is not ready to extended any application due to many concerns and policies.
So, my question is how can we utilize blueprint and still utilize same application with new set of features from Blueprint instead of an entirely new application that extended existing one.
Is this feasible or are we have only the method of extend application to utilize blueprint?
Pegasystems Inc.
IN
Hi @NishanthVanka,
Thanks for writing your query here. And happy to know that your client is really impressed by the accelerated design and development showcased by blueprint.
Could you please explain what are the new features you are looking to build and also about the concerns mentioned here - "But client is not ready to extended any application due to many concerns and policies."
When you extend an application using Blueprint, it doesnt create a new application. It creates a new Branch in the existing application and adds the Case types, Data types etc in that branch. You can learn more about extending application here: https://docs.pega.com/bundle/platform/page/platform/app-dev/importing-b…. I hope this would provide the solution you are looking for.
Regards,
Eclantiqx
IE
HI @SumanKumar,
Thanks for the reply, yes this can help to initiate but this led to next question?
How do we update the case type that has been imported using blueprint.
For example, we have a case type "Federated Opinion". This has 3 stages as per the initial documentation.
We have imported all these changes into the application like the branch you have suggested.
After review, we have merged the code.
Now, comes a scenario where more changes came in the documentation.
What approach should we follow in this case. Should we re-export the application and follow the same approach?
Or do we have a better approach on updating the processes and case types as we build the application where we use the blueprint and documents rather than building in App studio. This was the feature that hooked the client but we are not able to find a relevant source to implement the same.
Thanks,
Krishna Nishanth