LinkedIn
Copied!

Table of Contents

Application update scenarios for the Pega Express methodology

Version:

Only available versions of this content are shown in the dropdown

To start planning your Microjourney in a user-friendly, transparent, and holistic way, first update your application. As a result, you can visualize the key elements of your cases – case types, personas, and data – on one screen, so that you can improve your understanding of the needs of your customers.

You only need to update your existing applications that you created in Pega Platform 8.3 or earlier. All new applications that you create in Pega Platform 8.4 and later support the Pega Express methodology by default.

The update proceeds in the following order:

  1. When you open your existing application in App Studio, a prompt to update your application is displayed.
  2. After you accept an update, your application creates rules corresponding to data objects and personas. Your application uses an unlocked ruleset or a branch to store the rules.

    By default, your application uses logic to choose the best unlocked ruleset. If you want to specify a ruleset to store the new rules, specialize the pySetUpgradeRuleSet data transform. For more information, see Data transforms.

  3. When the update is complete, you need to merge the new personas and data objects rules.

    For more information about merging rulesets, see About the Ruleset Maintenance wizard.

    For more information about merging branches, see Merging branches into target rulesets.

If your application includes built-on applications, update the built-on applications first. If you update your built-on applications first, when you update your current application, it only references the data objects from your built-on applications.

By updating your current application first, it creates the data objects that it uses from the built-on applications. If you update your built-on applications later, it duplicates the data objects. As a result, when you start by updating your built-on applications, you save time and resources.

Update without built-on applications

During the update, your application performs the following tasks:

  • Creates new data objects that correspond to all the data types that are present in your application.
  • Creates personas that correspond to all the access groups in your application that do not have access to Dev Studio, App Studio, Admin Studio, or Prediction Studio.
  • Matches releases with color-coded symbols, if your application includes releases. If your application does not include any releases, it creates new releases.

Update with built-on applications

During the update, your application performs the following tasks:

  • References existing data objects from the built-on applications to avoid duplicating items, if you update the built-on applications first.
  • Creates personas that correspond to all the access groups in your current application and built-on applications that do not have access to Dev Studio, App Studio, Admin Studio, or Prediction Studio.
  • Matches releases with color-coded symbols, if your current application or built-on applications include releases. If your application does not include any releases, it creates new releases.

What to do next: After you update your application, start planning your Microjourney. See Adding case types to organize work.

For relevant training materials, see the Defining a customer Microjourney module on Pega Academy.

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.