".blueprint" filetype

Pega-as-a-Service
, , , , ,
1

Does anyone know what kind of filetype .blueprint is and how it can be deconstructed? I’d like to understand (and see) what I’m actually importing here.

2

@Michel Kraaij I checked under the PSC Pega GenAI FAQ page and the community Pega GenAI Blueprint
Frequently Asked Questions but it is not listed there.

Please use the ‘Contact Pega Blueprint Team’ form which is listed at the bottom of the latter FAQ page.

as.png
as.png1332×720 48.9 KB

:warning: This is a GenAI-powered tool. All generated answers require validation against the provided references.

========================================================

here’s what I found about how these files work and how you can understand what you’re importing.

A .blueprint file is a specialized file format used in Pega GenAI Blueprint, which contains the structural definition of a Pega application. These files include foundational assets such as:

  • Case Types
  • Case Life Cycles
  • Data Models
  • Personas
  • Other elements necessary for building a Pega Platform application

While the specific technical structure of the file format isn’t publicly documented (it appears to be a proprietary format), there are two main ways you can “deconstruct” or view what’s inside a .blueprint file:

1. Download as PDF
When creating a Blueprint in Pega GenAI Blueprint, you have the option to download both the .blueprint file and a PDF representation. The PDF provides a visual representation of the application structure defined in the .blueprint file, making it easier to understand what elements are included.

2. Import into Pega Platform
The most comprehensive way to see what’s in a .blueprint file is to import it into Pega Platform:

  • In App Studio, create a new application and select “Build from a Blueprint”
  • Upload your .blueprint file
  • During the import process, Pega Platform will create all the assets defined in the blueprint
  • After importing, you can explore all the created elements to see exactly what was contained in the file

This import process essentially “unpacks” the blueprint into its constituent parts, allowing you to see and work with all the elements that were defined in it.

If you’re working with an existing application and want to understand its structure, you can also export it as a blueprint file (in App Studio > Overview > Export as Blueprint), which creates a .blueprint file containing all the foundational assets of the application.

References: