When I export a Blueprint to the Pega Platform, only two rulesets are generated (Application and Organization), and all the generated rules are saved in the Application ruleset.
However, when I create an application directly in Pega (without using Blueprint), the system automatically generates three types of application rulesets: Work, Data, and Integration.
Is the simplified ruleset structure generated by Blueprint the expected design behavior?
If so, what is the recommended best practice to refactor or restructure the application in order to align with a standard layered architecture (e.g., separating Work, Data, and Integration concerns into dedicated rulesets)?
Should the additional rulesets be manually created after export, and are there any guidelines or automation mechanisms to properly migrate the generated rules into the appropriate ruleset layers?
@HalynaK2 Yes, this is expected behavior. When a Blueprint is imported into the Pega Platform, only the Application and Organization rulesets are created. All rules generated from the Blueprint including any simulation artifacts are saved in the Application ruleset by default. If required, these rules (for example, integration-related assets) can be manually moved to the appropriate rulesets, such as the Integration ruleset, after the import.
@Dhinesh_M Thank you for the clarification. I would like to confirm whether Pega recommends using the Data ruleset to store rules for Data classes, or if it is preferable to keep them in the Application ruleset after Blueprint import?
@HalynaK2 Pega recommends using a dedicated Data ruleset to store rules that belong to Data classes, rather than keeping them long‑term in the Application ruleset after a Blueprint import.
Thank you for confirming the recommendation regarding the use of a dedicated Data ruleset. I would like to understand if there is a specific reason why the Blueprint import process is designed to place all rules into the Application ruleset by default.
Additionally, I would like to know if Pega plans to enhance the Blueprint import process in the future so that rules can be automatically placed into their corresponding rulesets.
Currently, manually moving rules from the Application ruleset to the appropriate rulesets and deleting them from the Application ruleset is not very user-friendly, so any improvement in this area would be greatly appreciated.
@HalynaK2 to me, Blueprint output is a “foundation” or “starting point”, not a fully layered application architecture. After import, teams are expected to evolve the application using standard Pega guardrails, including introducing layered rulesets as the design matures.
Thank you very much for the clarification and for the detailed explanation.
I appreciate the guidance, and I hope this can be taken into consideration for future enhancements, as enabling a clearer separation of Data rules into their respective rulesets would greatly improve usability and maintainability.