Pega Sandbox

Tag: business

  • How to Create a Bank Application Using Pega Blueprint (Step-by-Step Guide)

    How to Create a Bank Application Using Pega Blueprint (Step-by-Step Guide)

    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.

    1. Industry: Select Banking
    2. Click Next
    3. Sub-Industry: Choose Retail Banking
    4. 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:

    1. Switch to Dev Studio
    2. Verify that the correct branch is attached
    3. 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.

  • Pega Constellation Data Modeling: Step-by-Step Guide

    Pega Constellation Data Modeling: Step-by-Step Guide

    FILES:

    Data model design
    Countries Catalog

    In this guide, we’ll walk through how to design and build a complete Customer Data Model in Pega Constellation.
    You’ll learn how to:

    • Create data objects from scratch
    • Establish relationships between objects (embedded and referenced data)
    • Upload external catalogs (CSV) into Pega
    • Visualize the full data model
    • Reference the data model inside a case type

    This tutorial mirrors exactly what was built in the video—perfect for beginners learning Pega Constellation’s data model capabilities.

    1. Designing the Data Model

    Before using App Studio, it’s important to outline the structure.
    Our Customer object will contain:

    Customer Fields

    • Name
    • Email
    • Phone (list of phone records)
    • Address (single address record)
    • Products (list)
    • Nationality (reference to a Country catalog)

    Supporting Data Objects

    To support the customer entity, we will also create:

    • Phone
    • Phone Types (Home, Mobile, Work)
    • Address
    • Address Types (Home, Work)
    • Products
    • Country Catalog (CSV uploaded from GitHub)

    Each of these will be modeled as a Data Object inside Pega Constellation.

    2. Creating the Customer Data Object

    1. Navigate to App Studio
    2. Click New → Data Object
    3. Name it Customer
    4. Choose Local storage
    5. Click Submit

    Your object is now created.
    Next, we’ll add all fields using the Data Model Visualizer.

    3. Adding Fields to Customer

    Open the Customer data object and add:

    Name

    • Type: Text (single line)

    Email

    • Type: Email

    Phone

    This field is an embedded data reference to a new list-type data object we’ll create.

    Address

    Another embedded data reference to an Address data object.

    Nationality

    This will be a picklist that retrieves records from the Country catalog (CSV).

    Products

    A list of product items (you can replicate the same steps as the Phone object).

    We’ll configure the Phone, Address, and Country objects next.

    4. Creating the Phone Data Object

    1. Click New → Data Object
    2. Name it Phone
    3. Choose Local
    4. Add the following fields:

    Phone Type

    • Type: Data Reference
    • Points to: Phone Types data object
    • Mode: Single record

    Phone Number

    • Type: Phone

    Save the object.

    5. Creating Phone Types (Dropdown Source)

    1. Create a new Data Object named Phone Types
    2. Add one field:
      • Type (Text)
    3. Go to Records and add the allowed values:
      • Home
      • Mobile
      • Work

    These values will appear automatically as dropdown choices thanks to Pega’s auto-generated data pages.

    6. Creating the Address Data Object

    1. Create Address as a new Data Object
    2. Add:
      • Address (Text)
      • Address Type (Data Reference → Address Types)

    Create Address Types

    1. Create Address Types Data Object
    2. Add a Type field (Text)
    3. Add records:
      • Home
      • Work

    7. Creating and Uploading the Country Catalog

    We’ll use a CSV catalog from GitHub containing:

    • Country Name
    • Alpha-2 Code
    • Country Code (numeric)

    Steps to import:

    1. Create a Data Object named Country (or CountryCode)
    2. Add three fields:
      • Name
      • A2
      • Code
    3. Click Import
    4. Upload the CSV file
    5. Map the columns
    6. Validate and import

    Pega will automatically create the data pages that expose these records.

    8. Adding Nationality to the Customer Object

    Inside Customer:

    1. Add a new field: Nationality
    2. Type: Picklist
    3. Data Page Source: Country list data page
    4. Display Field: Name

    This will display the country name and reference the selected record.

    9. Visualizing the Data Model

    Open the Data Model Visualizer to confirm relationships:

    • Customer → Phone → Phone Types
    • Customer → Address → Address Types
    • Customer → Nationality → Country Catalog

    This visual map helps guarantee your data structure is correct before adding views.

    10. Referencing the Data Model in the Case Type

    To make the Customer object available inside a case:

    1. Go to Case Types
    2. Select the case (e.g., KYC Customer)
    3. Open the Data Model tab
    4. Add a new field:
      • Name: Customer
      • Type: Embedded Data
      • Data Object: Customer
      • Mode: Single Record

    Now the case can create, store, and use the entire Customer data model.

    What’s Next?

    In the next tutorial, we will:

    • Build the views and forms
    • Bind fields to the UI automatically
    • Display dropdowns powered by our data pages
    • Save Customer data during case processing

    Pega Constellation automates data pages, relationships, and field behavior—making data modeling faster and easier than traditional Dev Studio.