Conversation
N J Court
US
Last activity: 11 Sep 2025 10:52 EDT
Approach to adopt Blueprint for an Organization having a strong assest library at an Enterprise layer shared across its divisions
What's the approach should be for an organization, having been deployed many of its application in pega, so have already been developed lot many assets like UI, Data and other reusable component developed as part of its enterprise layers and now wants to develop a new application using blueprint. Shouldn’t it first generate a blueprint for the existing Enterprise layer then use this as a supporting documents, while generating Blueprint for new application OR should it first generate blueprint and then import into the APP studio and while importing select class structure, accordingly? Please guide.
Pegasystems Inc.
IN
Hello @VishnuG6
You should first generate the Blueprint and use it while creating a new application. While creating the application you should choose the built on application and then select the correct class structure in the Application creation wizard.
Regards,
N J Court
US
@SumanKumar Thanks Suman, I understand that part that I can choose it under Built on Application, and generated Case types are fine in the Blueprint stage however what about the data types and integration which also, gets generated in the blueprint, many of these data types, if application already has as common assets across the other already developed applications, wouldn't that create conflicts and mapping issues, that's why I was asking this question, not sure if I able to explain the situation here, so attaching a sample application and a screen shot of App studio, here the application 'CLM for Financial Services - Retail' might already have data object like employee, HR Executive etc.