Blueprint Issues

Hi,

I am facing two issues while using blueprint. I would appreciate some guidance from the community:

  1. For the use case of extending current application, when I am importing an updated blueprint back into my application, I am getting the below class/data errors. Essentially, the classes already exist and therefore the wizard is suggesting that I create new classes. However, that would not be ideal as I would like to ‘extend’ current rules, not create new classes. What is the right approach to follow here so that I can import the updates case lifecycles without having to create a new class?

  2. Exporting a blueprint of my current application (size 5.4 MB) and importing it as an asset on the blueprint tool is throwing the below error. Is there a restriction that has been imposed? How does one “reduce the size of an exported PEGA blueprint”?

For the first point in your query.
as you are extending existing application, I hope you have selected

in which case for case types you should have seen

and should have used

i would recommend you watch this video (from 7.19) to see this in action

@Amey_Thombre pega forums blocks time stamps, you’ll need to change it from using full colon : to say .

e.g. 10.01

I’ve had the same problem on my webinar summaries, else you get the “proprietary information hidden warning”

Could you please confirm Extend with Blueprint works for new case types and data objects? The screenshot from Saurabh seems to have the case types already imported. Please clarify