LinkedIn
Copied!

Required Pega Customer Decision Hub and Pega Marketing hotfixes

The following tables list required hotfixes for the Pega Customer Decision Hub™ and Pega Marketing™ applications.

To request a hotfix:

  1. Go to your account on My Support Portal.
  2. Click New Request > For something I need, and then select Service request > Existing hotfix.
  3. Fill out the case creation form, and then click Finish.

Import each type of hotfix in the listed order during the Pega Customer Decision Hub or Pega Marketing installation or upgrade:

  • Apply Pega Platform hotfixes immediately after the Pega Platform installation or upgrade.

  • Apply Pega Customer Decision Hub or Pega Marketing hotfixes just after you complete the application bundle import.

  • Optional: If you use Pega Customer Decision Hub for Financial Services or Pega Marketing for Financial Services, apply the hotfixes listed on the Pega Customer Decision Hub for Financial Services hotfixes page.

  • Apply Pega Next-Best-Action Advisor hotfixes just after you complete the application bundle import.

  • Optional: If you use Pega 1:1 Operations Manager, apply the hotfixes listed on the Pega 1:1 Operations Manager hotfixes page.

To see the required hotfixes for your version of the Pega Customer Decision Hub or Pega Marketing application, click the appropriate link:

To see hotfix installation details, see the readme that is included in the hotfix.

Pega Customer Decision Hub 8.5

Required Pega Customer Decision Hub 8.5 hotfixes

Hotfix Number Observed Behavior
HFix-68885 The application wizard can be run on production environments.
HFix-69284 Volume constraint-enabled outbound runs that write directly to an output template fail to write to the specified database template destination.
HFix-70153 Next Best Action associated with real-time events duplicated.
HFix-70161 Next Best Action Designer upgrade fails after adding a new context in Context Dictionary.
HFix-70192 Contact policies (suppressions) not working as expected in multi-level configurations.
HFix-80085 This hotfix is dependent on HFix-70196. In order to support adaptive models running in multi-level decisioning mode, the managed strategies that recreate the customer Context (ModelImpl) strategies need to be regenerated using OriginalSubjectID instead of pySubjectID.
HFix-70196 This hotfix is dependent on HFix-80085. In order to support adaptive models running in multi-level decisioning mode, the managed strategies that contain Context shapes need to be regenerated with Is Possible Recipient unchecked.
HFix-80140 Paid actions are incorrectly competing with the other outbound channels, causing real-time events to not trigger actions.
HFix-67882 Strategy generation issues caused by very long taxonomy names.
HFix-68364 Issue with action and treatment status after creation.
HFix-68670 Taxonomy changes in Next-Best-Action Designer result in rules being moved to a new ruleset.
HFix-67266 Required hotfixes for Next-Best-Action Designer.
HFix-67276 Unnecessary XML serialization.
HFix-67968 TopOfferOrBundleForOutbound strategy filters out all bundle members for an action bundle and only passes the bundle parent through.
HFix-67845 Next-Best-Action Designer does not render and shows an error.
HFix-68956

Upgrade the Facebook Marketing API to v9.0. This is a mandatory fix that needs to be applied if your Facebook App is pointing to API version v9.0 or if it is pointing to an API version that is already deprecated.

The API version deprecation schedule can be found here.

 

Pega Marketing and Pega Customer Decision Hub 8.4

Required Pega Marketing and Pega Customer Decision Hub 8.4 hotfixes

Hotfix Number Observed Behavior
HFix-70078 Paid media processing is triggered even when paid destinations are not configured, causing failure in processing.
HFix-80041 ADM service does not automatically update adaptive models.
HFix-80190 Contact policy is not applied if volume constraints are enabled.
HFix-68583 Backward chaining enabled by Pega Customer Decision Hub during strategy execution.
HFix-68640 Taxonomy changes in Next-Best-Action Designer result in rules being moved to a new ruleset.
HFix-66738 Contact policy suppressions do not work as expected.
HFix-66625 The Unsubscribe link shows an error if clicked twice in a browser session.
HFix-65456 Next-Best-Action Designer fails to render, or the Save action for the Channels tab fails.
HFix-67186 Unnecessary XML serialization.
HFix-68388

Upgrade the Facebook Marketing API to v9.0. This is a mandatory fix that needs to be applied if your Facebook App is pointing to API version v9.0 or if it is pointing to an API version that is already deprecated.

The API version deprecation schedule can be found here.

HFix-63073 Ignore Case option for Eligiblity Criteria may not be applied at runtime.
HFix-63159 Next-best-action simulation, with outbound treatments and model maturity turned off, fails when run.
HFix-62140 Contact Policy constraints are not applied at Issue level.
HFix-61158 Error while saving the Context Dictionary.
HFix-62064 Duplicate table error when editing new database templates.
HFix-62061  Event actions configured in Next-Best-Action Designer do not progress after waiting.
HFix-61115 Group-level contact policies and simulations sometimes return unexpected results.
HFix-61159 Real-time containers do not pass the required data when generating click-through URLs.
HFix-61160 New treatments do not show on the Action rule form.

 

Pega Marketing 8.3

Required Pega Marketing 8.3 hotfixes

Hotfix Number Observed Behavior
HFix-56305

Data-Admin-Product-Framework rule is missing for Pega Marketing 8.3.

This hotfix must be imported manually and is a pre-requisite for using the Hotfix Manager with Pega Marketing 8.3 hotfixes.
HFix-67187 Unnecessary XML serialization.
HFix-63812

Upgrade the Facebook Marketing API to v7.0. This is a mandatory fix that needs to be applied if your Facebook App is pointing to API version v7.0 or if it is pointing to an API version that is already deprecated.

The API version deprecation schedule can be found here.

HFix-57057 Paid Media jobs start but do not finish.
HFix-57821 Cannot restart a campaign run if the customer key property and column differ.
HFix-59577 Segments with Paid Sync fail to run recurring schedule.
HFix-59405 Incorrect SmoothedPropensity calculation.
HFix-59130 Contact policy suppressions not working at Group level.
HFix-58226 For revision management, changes done to an action rule are not available if the user who made the changes reopens the action before submitting the change request.
HFix-57837 Incorrect filter condition in the Next-Best-Action strategy framework; top actions filtered by constraints.
HFix-58450 Applicability and suitability not included in Next-Best-Action action overrides.
HFix-56949 Next-Best-Action Designer contact policy suppressions not working as expected.
HFix-56491 Combined Next-Best-Action Designer strategy framework fixes, including Arbitration strategy, ActionOutcomesForThePast07Days IH Summary, and ActionOutcomesForThePast30Days IH Summary.
HFix-57594 Volume constraints initiate duplicate actions in some cases.
HFix-56244 APNs feedback service agent leaves idle database connections.
HFix-55978 MKTID cookie is not decrypted in a container call.

 

Pega Marketing 8.2

Required Pega Marketing 8.2 hotfixes

Hotfix Number Observed Behavior
HFix-66774 Unnecessary XML serialization.
HFix-62772 Submitting change requests with multiple actions leaves Action rule checked out.
HFix-57831 Partition key handling has runtime inconsistencies.
HFix-58664

Real-time containers do not return valid cookies when using GET.

HFix-60845 The RunHandleResponsesDF agent is rendered in an exception state, which causes the pxHandleResponses realtime dataflow run to be managed improperly.
HFix-56357 For revision management, changes done to an offer rule are not available if the user who made the changes reopens the offer before submitting the change request.
HFix-54887 Segment creation fails due to lack of database connections.
HFix-56245 APNs feedback service agent leaves idle database connections.
HFix-53974 Facebook Ads SDK upgraded from 3.2.0 to 3.3.0.
HFix-52156 Addresses the issues related to segment and real-time paid synchronization for different actions and statuses. Also addresses the issues related to the customer payload calculation for Facebook Ads destinations.
HFix-52113 Offer eligibility artifacts created in wrong ruleset.

 

Pega Marketing 8.1

Required Pega Marketing 8.1 hotfixes

Hotfix Number Observed Behavior
HFix-57578 BadClass error while running a real-time event enabled campaign.
HFix-54634 Multiple hand-off flows initiated for one Field Marketing offer.
HFix-48518 Enable transactional Segment refresh.
HFix-49170 Segment issue when using multiple string criteria with the Include missing values option.
HFix-49429 Field Campaign performance degradation.
HFix-49484 Master segment view creation issue.
HFix-49709 Strategy Builder generation issues.
HFix-51858 Resilience issues with outbound file and database processing.
HFix-51954 DF_Wait data flow does not run in distributed mode for Volume Constraint campaigns.
HFix-50909 The RunHandleResponsesDF agent is rendered in an exception state which causes the pxHandleResponses realtime dataflow run to be managed improperly.
HFix-48691 Create Google Ads destination settings to support OAuth2 authentication.
HFix-48767 New Facebook accounts created will no longer work with Facebook Marketing API version 3.1.1. Use the 3.2.0 version of the Facebook Marketing API.

Google AdWords API version 3.14.2 is deprecated since September 18, 2018. Use the 4.1.0 version of the API
(Google AdWords API version is v201809).
HFix-48622

Incorporated the changes according to the latest Google Ads libraries and Facebook Ads library.

HFix-48767 must be installed before installing HFix-48622.

 

Pega Marketing 7.4

Required Pega Platform hotfixes for Pega Marketing 7.4

Pega Platform Version Hotfix Number Observed Behavior
7.4 HFix-46690 Code changes show as not installed in the hotfix manager.
HFIX-43798 Bundled email treatments do not display referenced properties.

Required Pega Marketing 7.4 hotfixes

Pega Platform Version Hotfix Number Observed Behavior
7.4 HFix-47827 Deleting batch output table uses full table scan.
HFix-48524 Enable transactional Segment refresh.
HFix-49509 Segment issue when using multiple string criteria with the Include missing values option.
HFix-52082 Data flow process throws unhandled exception.
HFix-46520 Enable Pega Marketing 7.4 for streamlined upgrade to Pega Marketing 8.
HFix-46350 DF_Wait dataflows fail to run for Real-Time Events.
HFix-46121 Campaign seed list test completes with error if the offer contains a Wait shape.
HFix-46007 Incorrect SQL generated for sub-segments after upgrading to Pega Marketing 7.4.
HFix-45972

Upgrade activity fails for certain configurations.

HFix-45693 Campaign seed list test does not work.
HFix-45688 Segment filters do not work correctly for distribution tests.
HFix-45971 The pyGroupID property is not populated during segment refresh.
HFix-43970 Hotfix ruleset versions for Pega Marketing rules are missing.
HFix-43702 Progressing Offers from Microsites after upgrade causes errors.
HFix-44662 Identity Matching is not working as expected with MKTID cookie value.

 

Pega Marketing 7.31

Required Pega Platform hotfixes for Pega Marketing 7.31

Pega Platform Version Hotfix Number Observed Behavior
7.3.1 HFix-38936 In a cluster with multiple Pega Visual Business Director (VBD) nodes, a data flow can fail to complete after a VBD node is ungracefully terminated.
HFix-38950 Abstract Push Engine throw the following error: Portal Name could not be retrieved from request.

Required Pega Marketing 7.31 hotfixes

Pega Platform Version Hotfix Number Observed Behavior
7.4 HFix-53930 Addresses the issue which causes PEGA0042 alerts in logs while real-time container execution is triggered for Campaigns.
HFix-43974 Cumulative fix for Pega Marketing 7.31 on Pega 7.4.
HFix-39836 This hotfix resolves a performance issue with running an offer in a Pega Marketing Campaign.
7.3.1 HFix-53930 Addresses the issue which causes PEGA0042 alerts in logs while real-time container execution is triggered for Campaigns.
HFix-48578 Enable transactional Segment refresh.
HFix-48491 New Facebook accounts created will no longer work with Facebook Marketing API version 3.1.1. Use the 3.2.0 version of the Facebook Marketing API.

Google AdWords API version 3.14.2 is deprecated since September 18, 2018. Use the 4.1.0 version of the API
(Google AdWords API version is v201809).
HFix-48492

Incorporated the changes according to the latest Google Ads libraries and Facebook Ads library.

HFix-48491 must be installed before installing HFix-48492.
HFix-41402 Encountered error while adding data association in PegaMkt7.31.
HFix-42307 Upgrading segments can fail if backing database class does not exist.
HFix-39276 Upgrades to Pega Marketing 7.31 experience an SQL scripting issue.
HFix-39478 For the first group in the segment, if the option ‘Exclude” has been selected, the segment displays the option, 'Start with'.
HFix-39836 This hotfix resolves a performance issue with running an offer in a Pega Marketing Campaign.
HFix-40241 Segment criteria not upgraded properly to Pega Marketing 7.31.
HFix-40356

Emails sent by Pega Marketing have an empty header entry.

 

Pega Marketing 7.22

Required Pega Platform hotfixes for Pega Marketing 7.22

Pega Platform Version Hotfix Number Observed Behavior
7.3 HFix-36204 Pega Platform 7.3 users with DB2 environments can see Decision Strategy Manager page failures.
HFix-36236 Decision tables throw the following exception: java.lang.UnsupportedOperationException.
HFix-36951 A campaign fails because its generated Data Flow is deleted before its execution is complete.
7.2.2 HFix-31671 The DSM clipboard contains an unsupported operation exception: hasValidValue.
HFix-31622 The Connect Rest service does not correctly parse Boolean properties.
HFix-31717 ClipboardAdapter reverts page-list items to the obj-class defined on the property, instead of original class.
HFix-31168 Report definitions are unable to pass parameters to data flows using the pxOverwriteSource property.
HFix-31361 You cannot validate data flow when you over ride it using a report definition with a different key.
HFix-31661 Existing Simple Question rule with Rich text is not working.
NOTE: Required only when Pega Survey 7.22 is installed.
HFix-31960 You cannot format headers in repeating grids to be right-justified.
HFix-35529 Wait and volume constraint data flows fail with an SQL error.
HFix-37145 Logs contain errors even after an item is purged.

Required Pega Marketing 7.22 hotfixes

Pega Platform Version Hotfix Number Observed Behavior

7.3

HFix-32290 Default Home page does not show the Manage NBA widget.
HFix-34963 Outbound SMS messages are missing originator address, Type of Number (TON), and numbering Plan Indicator (NPI).
HFix-35647 (supercedes HFix-35164) Emails are not delivered after upgrading to Pega Platform 7.3.
HFix-35648 The dataflow status function uses older data flow status names.
HFix-35663 Marketing profile User Interface (UI) does not display the interaction details.
HFix-35668 History tab of list segments are not displayed after upgrading to Pega Platform 7.3.
HFix-35681 Next Best Action Designer does not show Real-Time containers after an upgrade to Pega Platform 7.3.
HFix-35376 The V2 container service does not evaluate cookie values.
HFix-35489 The purge agent does not work for campaigns configured to use a direct database template.
HFix-35683 Pega Marketing 7.22 requires changes for the Revision Management functionality to work in Pega 7.3.
HFIX-36137 Redundant SQL query slows the Pega Marketing campaign user interface.
7.2.2 HFix-32290 Default Home page does not show the Manage NBA widget.
HFix-34963 Outbound SMS messages are missing originator address, Type of Number (TON), and numbering Plan Indicator (NPI).
HFix-35164 Email sends fail (554 error code) when configuration does not use port 25.
HFix-35376 The V2 container service does not evaluate cookie values.
HFix-35489 The purge agent does not work for campaigns configured to use a direct database template.
HFIX-36137 Redundant SQL query slows the Pega Marketing campaign user interface.

 

Pega Next-Best-Action Advisor 7.22

Required Pega Platform hotfixes for Pega Next-Best-Action Advisor 7.22

Pega Platform Version Hotfix Number Observed Behavior
7.2.2 HFix-31622 The Connect Rest service does not correctly parse Boolean properties.
HFix-31960 You cannot format headers in repeating grids to be right-justified.

Required Pega Next-Best-Action Advisor 7.22 hotfixes

Pega Platform Version Hotfix Number Observed Behavior
7.2.2 HFix-33515 You cannot display or run service tasks from the Retail Composite view.

 

Pega Marketing 7.21

Required Pega Platform hotfixes for Pega Marketing 7.21

Pega Platform Version Hotfix Number Observed Behavior
7.2.2 HFix-31671 The DSM clipboard contains an unsupported operation exception: hasValidValue.
HFix-31622 The Connect Rest service does not correctly parse Boolean properties.
HFix-31717 ClipboardAdapter reverts page-list items to the obj-class defined on the property, instead of original class.
HFix-31168 Report definitions are unable to pass parameters to data flows using the pxOverwriteSource property.
HFix-31361 You cannot validate data flow when you over ride it using a report definition with a different key.
7.2.1 HFix-28476 Resaving a Java™ database connectivity instance causes an auth failure.
HFix-29155 'Reserve space when hidden' invalidates visibility condition.
7.2 HFix-26354 Opening the Visual Business Director (VBD) planner hides landing page headers.
HFix-26883 When importing a RAP (Rule-Admin-Product) with a view into a DB2 10.1 LUW database, GRANT statements fail due to invalid syntax.
HFix-27369 The Checkout to Branch option fails and displays a dialog box with no branches found.
HFix-27521 Clicking "Select Values" on a Segment screen fails to return values.
HFix-29521 Report definition validation prevents the joining of numeric and string columns.

Required Pega Marketing 7.21 hotfixes

Pega Platform Version Hotfix Number Observed Behavior
7.2.2 HFix-29252 There are missing Help files.
HFix-31226 Changes are required to support Pega 7.2.2 (revision management).
HFix-31507 Data flow shapes are truncated in Pega Marketing portal.
HFix-31536 The Case Designer "Configure View" popup does not display correctly.
HFix-34269 For the encoding of its application URLs, Pega Marketing does not use Unicode Transformation Format (UTF-8) formatting; instead, it relies on the system's default encoding standard format.
7.2.1 HFix-28520 Changes are required to support microsites without prGateway.
HFix-28466 Add support for Pega 7.2.1 encrypted datasource password and Java Naming and Directory Interface (JNDI).
HFix-28512 Formatting of non-CustomerID column issues are seen with Segments on Postgres database systems.
HFix-28915 Changes are required to support Pega 7.2.1 (revision management).
HFix-29252 There are missing Help files.
HFix-29342 Pega Marketing on Mobile can incorrectly format html-type emails.
HFix-30452 A PRPC Flow rule that includes a Wait shape cannot saved.
HFix-30624 Program distribution tests that includes volume constraints can incorrectly initiate offers.
HFix-37046 Email processing can take a long time as the last batch is single threaded.
7.2 HFix-27318 Outbound database templates incorrectly use requestor counts.
HFix-28359 An offer becomes unavailable to a customer if it is sent a second time when initiated from an event.
HFix-29252 There are missing Help files.

80% found this useful

Have a question? Get answers now.

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