Issue: Hotfix

Your application is missing critical hotfixes that you need to apply before starting an update. Request and apply the required hotfixes:

1. Go to My Support Portal and log in to your account.
2. Click Create, and then select Request Type Existing Hotfix Request.
3. Enter and verify the details of the hotfix that you need, and then click Submit.
4. After you receive the requested hotfixes, apply them to your application.

Issue: Locked artifact ruleset

Before you update, unlock the rulesets that contain rules to be updated.

Allow the system to modify rules during an update by unlocking the owning ruleset:

1. Log in to Dev Studio with a user account that is associated with an access group for which the locked ruleset is configured as the default destination ruleset.
2. In the navigation pane of Dev Studio, click the Operator icon, and then click Access group.
3. Click the Advanced tab.
4. In the Design time configuration section, click the Open icon next to the Default destination ruleset field.
5. On the Versions tab, click the arrow next to the ruleset version that you want to unlock.
6. Optional: In the Effective Start Date field, click the Calendar icon to set a later date for the unlock to take effect.
7. Click Unlock and Save.
8. In the Unlock RuleSet Version window, enter your password, and then click Submit.

Note: If the default destination ruleset is blank, it will be listed under the General Issues category, as in the following figure:

Issue: Batch Output tables

If the number of batch output tables and classes exceeds the recommended threshold of 1,000, an update might time out or take a long time. Reduce the number of batch output tables and classes by modifying the purge parameters used by the ProcessPurging agent:

• Setting the age of purged records
• Setting the maximum number of purged records

Setting the age of purged records

Purge a greater number of records at a time by decreasing the number of days that the system waits to purge records:

1. Log in to your application as an operator with access to App Studio.
2. In the navigation pane of App Studio, click SettingsApplication.
3. On the Configuration tab, in the Delete campaign data older than field, enter the number of days that the agent waits to purge a record.
4. Click Save.

Setting the maximum number of purged records

Purge records faster by increasing the maximum number of records that the system removes at a time. By default, the maximum number of purged records is set to 100. To change the default value, you first need to add this setting to the Dynamic System Settings list, and then set the new maximum number:

1. Log in to your application as an operator with access to Dev Studio.
2. In the navigation pane of Dev Studio, click RecordsSysAdminDynamic System Settings.
3. Add the MKTPurgeMaxRecords setting:
   1. On the Dynamic System Settings tab, click Create.
   2. On the New tab, enter a short description of the dynamic system setting.

      Example: Maximum number of records purged at a time.

   3. In the Owning Ruleset field, enter PegaMKT-Engine.
   4. In the Setting Purpose field, enter MKTPurgeMaxRecords.
   5. Click Create and open.
4. On the Settings tab, in the Value field, enter the new maximum number, and then click Save.

   For more information about the ProcessPurging agent, see agents.

Issue: NBAM:Agents Access Group

Ensure that the NBAM:Agents access group points to the correct application before the update. You can compare the access group with the name of the current application visible in the Application menu of Dev Studio.

1. Log in to your application as an operator with access to Dev Studio.
2. In the navigation pane of Dev Studio, click RecordsSecurityAccess Group.
3. Search for PegaNBAM:Agents.
4. Take note of the application to which the access group points in the Name field.

Issue: External Mappings

You must map the pyEmail and pyFullName properties to your customer class for the proper functioning of the application:

1. Log in to your application as an operator with access to Dev Studio.
2. In the navigation pane of Dev Studio, click App.
3. In the Class drop-down list, find your customer class.
4. On the External mapping tab, check whether the pyEmail and pyFullName properties are properly mapped to a column in the database table.

Issue: pyDescription Column

If you are updating from Pega Marketing version 7.13, in the PR4_RULE table, update the pyDescription column, if it exists, to a length of 1000. This will help mitigate errors during the update process.

The PR4_RULE table is located in the database schema under the PegaRules schemapr4_rulepyDescription.

Issue: Deprecated rules

If your application contains rules that a later version of Pega Marketing or Pega Customer Decision Hub deprecates, the rules will no longer be available after the update. Review the deprecated rules and take necessary action before updating. Currently, the Pre-Upgrade Check displays the following deprecated rule instances:

• Passbooks
• Non-visual segments
• Analysis projects
• Samples

Passbooks

The Passbook functionality has been fully removed from Pega Customer Decision Hub.

Non-visual segments

Update the deprecated non-visual segment in Visual mode before the update.

1. Log in to your application as an operator with access to Dev Studio
2. In Dev Studio, open a deprecated non-visual segment by searching for it or by using the Application Explorer.
3. Make a note of the rule configuration.
4. In the header of the rule form, click Check out.
5. Click the Visual Mode icon.
6. Recreate the configuration in Visual mode.
7. Click Save, and then click Check in.

Analysis projects

The Analysis project functionality is deprecated and will be removed in future releases of Pega Customer Decision Hub. Further use of this feature is not recommended.

Samples

The Samples functionality is deprecated and will be removed in future releases of Pega Customer Decision Hub. Further use of this feature is not recommended.

Issue: Customized rules

If your application has customized rules that override Pega Marketing or Pega Customer Decision Hub rules, an update will not take effect on the overridden rules. Review the customized rules and withdraw or re-baseline them if necessary.

Withdrawing a rule

If multiple instances of the customized rule exist in earlier versions of the same major-version ruleset, withdraw the customized rule. By withdrawing the rule, you exclude the rule and all its instances with the same name that exist in lower rulesets from rule resolution. Through a system update, you add an updated version of the rule to your Pega Customer Decision Hub application.

1. Log in to your application as an operator with access to Dev Studio.
2. In Dev Studio, open a customized rule by searching for it or by using the Application Explorer.
3. In the upper-right corner, click Check Out.
4. In the header of the form, next to the short description, click the rule availability label.
5. In the Availability list, select Withdrawn, and then click OK.
6. In the upper-right corner, click Check in.

Rebaselining a rule

If only one instance of the customized rule exists in your application, you can rebaseline the rule. Through rebaselining, you delete the rule, update your Pega Customer Decision Hub application, and then recreate the rule by using its updated version as the new baseline. If multiple instances of the customized rule exist in lower rulesets, withdraw the rule instead. Deletion excludes only the latest instance of the rule from rule resolution, and an earlier version instance becomes available for resolution. As a result, you cannot update the customized rule.

1. Log in to your application as an operator with access to Dev Studio.
2. In Dev Studio, open a customized rule by searching for it or by using the Application Explorer.
3. Make a note of the configuration that is used for the rule and keep the note for later use.
4. On the tab of the rule name, click Delete.
5. In the Delete window, enter a reason for the deletion, and then click Delete.
6. After you update your application, recreate a customized rule by using the configuration from step 3.