Import management

After a Blueprint is imported into Pega Platform, the team reviews the generated application foundation before beginning with configuration, refinement, or validation work. In Blueprint Delivered, this review confirms that the application still reflects the business intent captured in the Blueprint and that the team has a reliable starting point for authoring.

An import review is the first checkpoint after import. The team compares the generated application artifacts to the Blueprint to confirm what was created, what needs correction, and what requires follow-up work.

An application artifact is any application element created or updated during import, such as a Case Type, Data Object, Persona, View, or access configuration. The goal of the review is not to fully build the application. The goal is to confirm that the generated foundation is accurate enough for the team to continue. Blueprint import is a design alignment step that connects Blueprint intent to the application foundation.

During import review, the team should confirm the following details:

• The generated Case Types match the Blueprint design.
• The generated workflows reflect the intended Stages, Steps, and business outcomes.
• Data Objects and Personas are present and accurate.
• Generated artifacts align with the intended business outcome.
• Import decisions, such as build new, inherit, reuse, or defer, produce the expected application structure.
• Missing, incomplete, or incorrect details are identified for follow-up.

For example, a team imports a Blueprint for a travel support application. The Blueprint includes two Case Types: Complaint Resolution and Partner Onboarding. During import review, the team confirms that both Case Types were created, that the Data Objects and Personas match the Blueprint, and that the imported application reflects the intended customer support workflow. If the Partner Onboarding Case Type is missing a required approval step, the team identifies the gap and decides whether the workflow should be corrected in Blueprint or refined directly in Pega Infinity Studio.

In another scenario, a Blueprint includes a Customer Data Object. During import, the team chooses to reuse an existing enterprise Customer Data Object instead of building a new one. During import review, the team confirms that the application references the existing Customer Data Object as expected. If the imported workflow needs a field that the reused object does not provide, the team records that issue for follow-up instead of creating a duplicate Customer Data Object without review.

Blueprint import creates Pega Platform assets that the team can review before continuing development. Except for Access Roles, all assets generated from a Blueprint import are stored in a Branch. A Branch is a temporary place where generated Rules and configurations can be reviewed, adjusted, and validated before they are merged into the main application. After successfully validating the generated assets in the Branch, the Branch must be merged before any development begins.

Workspaces are user-specific, which means that a Workspace and the changes that the Workspace includes are visible only to the Operator using that Workspace. You make the changes visible to other team members by sharing them to a Branch, and then generally available by merging the Branch to an application, and then releasing the application, as the following scheme shows:

For example, a team imports a Blueprint that creates several Case Types, Data Objects, and Personas. Before the team continues with additional configuration, the Solution Builder reviews the generated artifacts in the default Blueprint Branch. If the artifacts look correct, the team can prepare to merge or begin authoring according to the project’s development process. If the team finds that a Case Type was imported with the wrong structure, the issue can be resolved before the changes are merged.

In another scenario, a large Blueprint includes several Case Types. The team decides to import only the first Case Type so that the generated Branch remains small and easier to review. This staged approach helps the team validate one part of the application foundation before importing more assets. It also lets Solution Builders begin authoring one part of the application while Solution Designers continue refining other Case Types in Blueprint.

Check your knowledge with the following interaction: