Conversation

StellarNexus Consulting UG
DE
Last activity: 25 Sep 2025 16:09 EDT
Consistency of Views and Data Models in Blueprint Export from the Pega application
Hello Team,
I would like to get your recommendation for the scenario described below.
An application with a considerable set of assets was used to generate a Blueprint, with the intention of rewiring it in Blueprint SaaS. During generation, the exported Blueprint from the app constructed before can be provided as an application asset to initiate blueprinting.
Now, here's the observed outcome : Only case type names and its stages/step names, data type names, and case/data type models are carried over. Stage views in the generated Blueprint differ significantly from those in the constructed application. In addition, case data model fields referencing data types are not associated correctly, and the resulting views appear distorted.
Questions for clarification:
-
Are view definitions and related configurations included as part of the Blueprint export from Pega?
- What level of consistency should be expected between the original application implementation and the generated Blueprint?
LG,Midhun