Pega Sandbox

Tag: cloud

  • How to Import and Map Data, Pega Course for Beginners

    How to Import and Map Data, Pega Course for Beginners

    Welcome back! 👋
    In this tutorial, we’ll walk through three essential Pega skills you’ll use in almost any real application:

    1. Importing a CSV file into a Data Type
    2. Searching and displaying records using a Data Page / Data Type
    3. Creating an Auto-Complete field with visibility conditions

    Let’s get started.

    1. Importing CSV Data into a Pega Data Type

    First, open the Data Type you created in a previous lesson.
    We’ll be importing a CSV file into it—make sure you have your file ready.

    Step 1 — Import the CSV

    1. Open the Data Type.
    2. Go to the Records tab.
    3. Click Import and upload your CSV file.
    4. Click Next.

    Step 2 — Map Source to Target Properties

    Pega will display each column from the CSV.
    Map each one to the correct target property, for example:

    • first_name → FirstName
    • last_name → LastName

    (Complete all mappings based on your CSV.)

    Step 3 — Configure Import Options

    You can choose how Pega updates existing records:

    • Always update
    • Update if blank
    • Update if source is not blank

    For this example, select Always update.

    Step 4 — Match Existing Records (Optional)

    If your Data Type already contains data, you can match rows by a unique ID.

    We do not have IDs in this example, so we’ll select FirstName as the match key.

    Click Next.

    Step 5 — Validate and Import

    Give the import a name, then:

    • Validate the file
    • Confirm there are no errors
    • Click Finish

    Your Data Type will now show all imported records—hundreds of rows ready to use!
    This is extremely useful when populating lists such as countries, states, cities, or any reference table.

    2. Building the Customer Search Auto-Complete

    Now let’s go back to our case flow.

    We’ll create the first assignment form where users search for an existing customer.
    If the customer isn’t found, we’ll later add a button to create one.

    Step 1 — Open the Section

    1. Open the Flow Action.
    2. Open the Section rule.
    3. Switch to the Full Section Editor.

    This is where we build the customer search UI.

    Step 2 — Add an Auto-Complete Field

    1. From the palette, go to Data Capture → Auto Complete.
    2. Drop an auto-complete field on your form.
    3. Set the Target Property (create a new property if needed).

    Step 3 — Use a Data Source

    Auto-completes can source from:

    • A data page
    • A clipboard page
    • A report definition
    • A property

    Because our customer data is stored in a Data Type, we will use a Data Page List.

    ⚠️ Important: A Page List Data Page must be used to return multiple results.
    A single-record Data Page only returns one item based on a parameter, so it won’t work for autocomplete.

    Step 4 — Select the Data Page List

    Choose the Data Page List created from your Data Type.

    Then configure the search results:

    • Search field: FirstName
    • Display fields: First Name, Last Name
    • Identifier: .pyGUID (the unique ID)

    Step 5 — Add the Hidden Customer ID Field

    Create a property to store the selected ID.

    When the user picks a name from autocomplete, we’ll capture the GUID silently.

    Now save the section and test it.

    3. Testing the Auto-Complete Search

    Open the User Portal and create a new case.

    Start typing in the Customer field:

    • Type C → Suggestions appear
    • If no exact match exists, it shows similar names
    • Example: Typing “Cri” may show Cristian

    This works perfectly for large datasets.
    Avoid dropdowns when you have hundreds of rows—autocomplete is the correct approach.

    4. What’s Next? Visibility Conditions

    Now that customer selection works, the next step (in a future tutorial) is adding conditional fields.

    For example:

    • Show address fields only after a customer has been selected
    • Reveal a section only when the customer is new

    We will configure visibility based on the selected customer’s ID or property values.

    ✨ Final Thoughts

    In this tutorial, you learned how to:

    ✔ Import CSV data into a Pega Data Type
    ✔ Map and validate records during import
    ✔ Build an auto-complete search field using a Data Page List
    ✔ Capture the selected record’s unique ID
    ✔ Test your search functionality in the User Portal

    These skills are essential for building real-world Pega applications using best practices.

  • How to Create a New Application in Pega Constellation

    How to Create a New Application in Pega Constellation

    What Is Pega?

    Pega is a low-code platform designed to help organizations build applications that automate business processes, manage workflows, and make intelligent decisions using AI and rules. It’s widely used across industries like banking, insurance, healthcare, and government to increase efficiency and improve customer experiences.

    Creating a New Application in Pega

    To create a new application using Dev Studio, follow these steps:

    1. Start the Application Wizard

    1. Log in to your Pega environment.
    2. Click Application → New Application.

    You’ll be presented with two options:

    • Build from scratch
    • Select an existing application type from Pega’s out-of-the-box (OOTB) offerings

    If you click Search all types, you’ll see a list of available applications. Since the Personal Edition includes fewer preloaded apps, we will proceed with Build from scratch.

    2. Choose the Application UI Architecture

    Pega provides three UI frameworks you can build your app with:

    • Traditional UI
    • Cosmos (modern, flexible, dynamic)
    • Constellation (the latest React-based, component-driven UI model)

    For this example, we’ll select Traditional UI, then click Next.

    3. Name and Create the Application

    Enter a name for your application and proceed to create it.

    You will then be prompted to define:

    • User types
    • Roles

    For now, we will skip this step and click Done.

    4. Why You Don’t See the App Immediately

    After creating the application, you might notice that it doesn’t appear in your Application menu.

    This is expected.

    When Pega creates a new application, it also generates required system assets—one of those is an Access Group. Access Groups determine:

    • Which applications a user can access
    • What permissions and roles they have

    Since your operator ID does not yet include the access group for the new application, you cannot access it.

    5. Assign the Access Group to Your User

    To add access to the new application:

    1. Click your operator name in the lower-left corner.
    2. Select Operator → Application Access.
    3. Search for the Access Group created for your new app.
    4. Add it to your user profile.
    5. Log out and log back in.

    After logging in again, your new application will now appear in the Application menu.

    Your application is ready! From here, you can start configuring case types, data objects, UI components, and more. Let me know if you want a follow-up tutorial on building your first case type or setting up data structures.

  • SOAP Integration in Pega from scratch

    SOAP Integration in Pega from scratch

    1. Launching the SOAP Integration Wizard

    In Dev Studio, go to:

    Configure → Integration → Create SOAP Integration

    This opens the SOAP Integration Wizard.

    The first step is to provide a WSDL URL, which defines the structure of the web service.
    For this example, we will use:

    http://www.dneonline.com/calculator.asmx?WSDL

    Click Next to continue.

    2. Reviewing Service Metadata

    After loading the WSDL, the wizard displays:

    • Service name
    • Port name
    • Endpoint
    • Available operations

    You can test operations from this screen. Once testing is done, click Next.

    3. Integration Layer Configuration

    The wizard now shows:

    • The integration class
    • The ruleset
    • The context where the integration assets will be created

    Click Preview Records to see all rules the wizard will generate. This modal displays the rule types and quantities.

    When clicking Create, you may encounter an error. This happens because Pega sometimes does not automatically create the integration class for SOAP services.

    If this occurs, manually create the class where all integration assets will be stored. After creating the class, click Create again.

    This time, the SOAP connector will be successfully generated.

    You’ll see:

    • Class name
    • Ruleset
    • WSDL
    • All created data sources
    • Option to Undo Generation, which removes all generated rules if needed

    Click Close when finished.

    4. Reviewing the Generated Connector

    Navigate to the integration class:

    App Class → Calculator → Integration-Connectors → Connect SOAP

    Here you’ll find one connector rule per operation defined in the WSDL.

    Inside each connector you can verify:

    • Endpoint details
    • Error handling
    • Processing options
    • Simulation settings

    Connector Request & Response

    Under the Request tab, you’ll find:

    • SOAP headers (if any)
    • Request parameters
    • The XML Stream rule (e.g., AddParameters) responsible for request mapping

    The Response tab includes the same structure for mapping outputs.

    5. Creating the Data Page

    Next, create a data class to hold the response from the service.
    Then create a Data Page that will invoke the SOAP connector.

    Configuration:

    • Source type: Connector
    • Connector type: SOAP
    • Connector name: Add (for this example)

    You can try the other operations later as practice—feel free to leave a comment if you have issues.

    6. Request Data Transform

    Create a Request Data Transform that passes two parameters:

    • intA
    • intB

    Make sure these parameters exist both in the Data Page and in the Data Transform.

    Map the two variables to the fields expected by the SOAP service.

    7. Response Data Transform

    Pega automatically generates a boilerplate Response Data Transform, but you can customize it.

    Important note:
    If the connector response returns a page, you must create the corresponding property in your data class and map the values one-to-one.
    If your data page runs successfully but the response appears empty, it’s usually because this mapping step was missed.

    8. Testing the Integration

    To test the integration:

    1. Open the connector rule
    2. Scroll to the bottom
    3. Click Test Connectivity

    If the service fails, Pega will show the error details.

    To test the Data Page:

    1. Open the Data Page
    2. Click Actions → Run
    3. Enter parameters (intA and intB)
    4. Validate the results and response status

    If any errors occur, they will appear in the results panel.

    Summary — Complete Integration Steps

    1. Obtain the WSDL
      Example: http://www.dneonline.com/calculator.asmx?WSDL
    2. Validate required headers or authentication (Postman helps with this).
    3. Go to
      Configure → Integration → Create SOAP Integration
      and follow the wizard.
    4. Verify generated classes and rules.
    5. Test connectivity in the connector.
    6. Create:
      • Data class
      • Data Page
      • Request Data Transform
      • Response Data Transform
      • Any needed properties
    7. Map request and response values.
    8. Run the Data Page and validate that the service works end-to-end.

    You can watch the full step-by-step demonstration in the accompanying video.
    Feel free to leave questions or comments—happy integrating!

  • 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.