Skip to main content

Pega GenAI Blueprint for accelerated application design

Pega GenAI Blueprint™ is the key to application design and delivery for Pega Business Architects (BAs). Blueprint incorporates the best aspects of Pega application design and development, acquired over many years of working directly with customers. Blueprint represents the evolution of application and Case design for BAs by providing a collaborative workspace that combines the power of generative AI with Pega best practices to dramatically accelerate the application design and development process. Blueprint is revolutionizing the landscape of digital transformations for Pega BAs.

As a BA, use Blueprint to collaborate with stakeholders from business and IT to deliver transformative Pega applications quickly. Blueprint reduces the application design process from weeks to just a few days or hours in some scenarios. Powered by Pega generative AI features and enriched by built-in industry expertise and Pega application development best practices, Blueprint is the fastest way to convert the business processes of your users and optimal outcomes into a Pega application design.

Blueprint explained

Blueprint is an application for accelerating the design and development of Pega Platform™ applications. Blueprint combines information about the users' industry and the name, purpose, and description of the application and generative AI to instantly suggest optimal application templates based on Pega best practices and successful industry-focused implementations. Elements of a Pega Platform application that Blueprint can generate include Case Types, Case Life Cycles, Case Type Data Models, data objects, and Personas.

Blueprint is available on Pega.com, which makes it accessible for those who do not have access to a Pega Platform development environment. This accessibility marks a meaningful change for BAs who can now collaborate in real time with stakeholders from business and IT to accelerate the design-review-feedback cycle that is crucial throughout the initial stages of development of a Pega project.

Blueprint as a SaaS application

Blueprint is not a Pega Infinity™ feature but a new software-as-a-service (SaaS) application. Pega developers continuously develop Blueprint by releasing improvements to the Blueprint site almost weekly. This cadence ensures that everyone who works in the Blueprint environment can always access the latest functionality.

Note: For more information about the latest advancements in Blueprint features, see the Pega GenAI Blueprint hub or the Blueprint release notes.

From Blueprint to Pega application

Blueprint is rapidly becoming an integral part of the Pega sales process. As a project moves from the sales phase to the application development phase, the Solutions Consultant passes the Blueprint to the Lead Business Architect and Lead System Architect (LSA) on the Pega project.

In the next phase of the project, the Pega Business Architect leads a series of collaborative conversations with stakeholders to ensure every aspect of the proposed Blueprint, including Case Types, Case Life Cycles, Data Models, data objects, and Personas, undergoes review and editing to meet the requirements of both the business and technical teams. Blueprint drastically reduces the time and effort that BAs require to educate and align the business team on out-of-the-box workflow automation features and convert business needs into technical requirements for the IT team.

Once stakeholders align on the Blueprint design, the project’s Lead Business Architect exports the Blueprint as both a PDF and a Blueprint file. The PDF is available for project stakeholders to reference as needed. The LSA then imports the Blueprint file into a new or existing Pega Platform environment.

The Blueprint file contains the baseline application structure that the LSA requires to create a new application or extend an existing one in Pega Platform in just minutes. During the import process, the LSA can compare application elements in the import file against the Blueprint PDF to confirm that the application is importing as expected. Users import Blueprint applications into Pega Platform on a branch, which provides the BA and System Architect (SA) teams the opportunity to make revisions as necessary before merging it with the main application.

The system saves every Blueprint that a BA or another project stakeholder creates to that user’s Blueprint Dashboard, which enables collaborative viewing, editing, and exporting as either a PDF or a Blueprint file as many times as necessary.

Check your knowledge with the following interaction:


This Topic is available in the following Module:

If you are having problems with your training, please review the Pega Academy Support FAQs.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega Academy has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice