In this tutorial, we’ll walk through how to create a complete pay (KYC onboarding) application using Pega Blueprint, the new automation tool that allows you to generate case types, data models, personas, and application structure with minimal manual setup.
Blueprint drastically reduces the time required to build an application from scratch, giving you a ready-to-customize foundation aligned with your business needs.
1. Accessing the Blueprint Dashboard
To get started, navigate to:
mega.com/blueprint/dashboard
Log in with your account, and you’ll see the Blueprint dashboard.
Click Create Blueprint to begin.
2. Selecting Templates and Application Context
Blueprint provides a library of templates according to the industry and type of application you’re building.
- Industry: Select Banking
- Click Next
- Sub-Industry: Choose Retail Banking
- Department: Select Onboarding New Customers
Blueprint will then ask for the application purpose. Choose:
- Know Your Customer (KYC)
You’ll also select:
- Language
- Location
Click Next, and Blueprint will start generating your template.
This process may take a minute. Blueprint analyzes your inputs and builds an initial application with stages, case types, personas, and data objects tailored to your selection.
3. Choosing Case Types
Once the generation is complete, you will be prompted to select the case types to include in the application.
For banking and KYC workflows, common case types include:
- Global KYC Customer
- Screening Cases (e-screening, adverse media, etc.)
- Onboarding Investigation
- Related Party Onboarding
Select the case types that apply and click Next.
Blueprint will display each case type with its stages and processes. For example:
- Identification & Due Diligence
- Background Screening
- Risk Assessment
- Final Resolution
4. Selecting the Data Object
Blueprint will then ask for the primary data object.
For onboarding workflows, select the basic customer information object.
Click Next.
5. Defining Personas
You can now define the personas who will interact with the application. Example personas include:
- KYC Analyst
- Operations Manager
- Credit Analyst Manager
Blueprint can auto-generate personas using AI, or you can manually add them.
Click Next.
6. Reviewing Your Blueprint
Blueprint generates a complete application outline, including:
✔ Stages and Workflows
For example:
- Identify Due Diligence
- Required customer information
- Screening and documentation review
- Perform Due Diligence
- Background checks
- Regulatory validations
- Risk evaluation
- Resolve
- Final decision
- Case closure
✔ Data Model
Blueprint creates:
- Properties and fields
- Data objects
- Embedded objects
- Child cases
✔ Personas and Access Layers
✔ Sample Data
When everything looks correct, download the Blueprint file.
7. Uploading the Blueprint to Pega
Go to your Pega environment and create a new application.
Choose:
“Build from a Blueprint”
Upload the file you downloaded earlier.
Pega will begin generating:
- Case types
- Data objects
- Personas
- Portals
- Sample data
This process may take several minutes. In my example, Blueprint generated:
- 13 case types
- 17 data objects
- 14 personas
- 3 channels (portals)
8. Reviewing the Application in Dev Studio
Once the application is created:
- Switch to Dev Studio
- Verify that the correct branch is attached
- Review:
- Case types
- Workflows
- Data objects
- Views
- Background rules
Sometimes Blueprint may not fully configure all case creation rules, so minor adjustments may be required.
9. Exploring the Application in App Studio
App Studio is the best place to work with:
- Views
- Data models
- Relationship maps
- Case previews
Use the Data Model Viewer to visualize relationships between data objects.
Use Case Type Preview to run a test case, review screens, and evaluate user flow.
In the example:
- The Global KYC Customer case type has stages automatically created by Blueprint.
- Some child case creation steps needed manual correction.
- Views are fully editable in App Studio, replacing old-style section rules.
10. Editing Views and Data Models
Constellation uses views instead of sections.
You can:
- Add fields
- Modify layouts
- Use data transforms
- Configure validation
- Reuse views across case types
If a rule appears locked, check your branch settings.
Always work with Branch Development ON to prevent version conflicts.
11. Final Notes and Next Steps
Blueprint gives you a strong foundation, including:
- Application structure
- Case lifecycle
- Personas
- Data models
- Sample logic
From here, you can:
- Refine workflows
- Add missing logic
- Configure validation
- Build UI views
- Define relationships between objects
- Customize the entire onboarding process
In upcoming tutorials, we’ll explore:
- Creating views in Constellation
- Building and connecting data objects
- Configuring background logic using calculated expressions
- Fixing child-case creation flows
- Mapping end-to-end onboarding processes
If you have questions, leave them in the comments — I’m happy to help.