Blueprint Import Fails During Case Lifecycle Generation in Pega Constellation 25.1.2

Blueprint and App Design
1

I have a client that is experiencing issues importing a Blueprint into a Pega Constellation 25.1.2 environment, and I am interested to know whether others have encountered similar behavior or identified a resolution.

The Blueprint-to-App generation process progresses successfully through the build phase and consistently reaches approximately 99–100% completion. At that point, the process displays a cleanup message and the import fails.

One notable observation is that the same Blueprint imports successfully into a 25.1.1 environment but fails consistently in 25.1.2, which makes us wonder whether this could be a regression, defect, or missing hotfix specific to 25.1.2.

What We Observed

  • The build progresses successfully through Client Contact, Building Application Data Model, Generating Fields for Case Types, Generating Fields for Data Objects, Generating Fields for Embedded Objects, and most View generation steps.

  • The failure occurs during: Preparing Views → Case Lifecycle.

  • Cause for failure: Unable to open an instance using the given inputs: .

  • Immediately afterward, the build reports: “An error was encountered during the build process. Performing cleanup.”

  • Cleanup does not appear to remove all generated artifacts. Branches, data classes, tables, and other generated rules remain and require manual cleanup.

  • The same Blueprint imports successfully in a 25.1.1 environment but fails consistently in 25.1.2.

Troubleshooting Performed

  • Imported the Blueprint without renaming generated artifacts. Another team member reported a successful import using default generated names.

  • Used the Customize option during import and modified the Organization Name, Application ID, and generated class names. The import failed.

  • Removed unused data objects such as Customer Info, Plan, Licensing Task, and Commission. The import still failed.

  • Reviewed the Blueprint for special characters and removed several occurrences such as ampersands. The import still failed.

  • Verified data objects actively referenced in the case lifecycle and removed objects identified as unused. The import still failed.

Environment

  • Pega Constellation 25.1.2

  • Blueprint-to-App generation

  • Custom Build option used during import

  • Same Blueprint imports successfully in 25.1.1

  • Failure occurs during Preparing Views → Case Lifecycle

Questions

  • Has anyone encountered Blueprint imports failing during the Case Lifecycle generation step with the error: Unable to open an instance using the given inputs: ?

  • Are there any known defects or hotfixes related to Case Lifecycle generation during Blueprint imports, renaming application IDs or generated classes, embedded data objects, or view generation?

2

We had the same issue in 25.1.2 environment and it failed at same exact step(9.5 - Preparing Case Lifecycle view). However, it works fine in 25.1.3 environment.

Note: We’re able to import successfully without the data objects in 25.1.2 environment.

3

Similar incident: Blueprint file import blockage while creating a new application - #11 by ShivaKumarS17124246

4

Thank you! I’ll see if the client can up this environment to 25.1.3. I’ll look at the incident you posted too.

5

Is the import module the same version? Have you updated it to latest?

Equally is this a fresh download of a blueprint file? With each release things get added to the Blueprint download that may be inconsistent with the import module you are using..

I would make sure you are on the latest import version and generate a new blueprint file to be sure.

6

It is a fresh blueprint file download. Will check the Blueprint Import Module.

7

Blueprint module was latest, no corrupt access group.

The client was able to download into a different stack when setting Dynamic System Setting rule ->EnableUnicodeRuleNames=true. Although the DSS setting exists in the original stack, the blueprint file import failed several times.

Workaround was to import blueprint into a different stack and then export RAP and move to original stack where they first tried the blueprint import.

8

When I run into import problems, I will first use the link to update the import module. After updating the import module, you frequently need to bounce the instance to get the import module updated in memory.