Article

Pega Marketing hotfixes

The following tables list required hotfixes for the Pega Marketing application. To request a hotfix, go to your account on My Support Portal. Click +Create and select Request Type > Existing Hotfix Request. Enter and verify the hotfix details and click Submit.

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

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

  • Apply Pega Marketing hotfixes just after you complete the application bundle import.

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

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

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

Pega Marketing 8.1

Required Pega Marketing 8.1 hotfixes

Pega Platform VersionHotfix NumberObserved Behavior
8.1HFix-50909The RunHandleResponsesDF agent is rendered in an exception state which causes the pxHandleResponses realtime dataflow run to be managed improperly.
HFix-48691Create Google Ads destination settings to support OAuth2 authentication.
HFix-48767New 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.

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

 

Pega Marketing 7.4

Required Pega Platform hotfixes for Pega Marketing 7.4

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

Required Pega Marketing 7.4 hotfixes

Pega Platform VersionHotfix NumberObserved Behavior
7.4HFix-46520Enable Pega Marketing 7.4 for streamlined upgrade to Pega Marketing 8.
HFix-46350DF_Wait dataflows fail to run for Real-Time Events.
HFix-46121Campaign seed list test completes with error if the offer contains a Wait shape.
HFix-46007Incorrect SQL generated for sub-segments after upgrading to Pega Marketing 7.4.
HFix-45972

Upgrade activity fails for certain configurations.

HFix-45693Campaign seed list test does not work.
HFix-45688Segment filters do not work correctly for distribution tests.
HFix-45971The pyGroupID property is not populated during segment refresh.
HFix-43970Hotfix ruleset versions for Pega Marketing rules are missing.
HFix-43702Progressing Offers from Microsites after upgrade causes errors.
HFix-44662Identity 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 VersionHotfix NumberObserved Behavior
7.3.1HFix-38936In 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-38950Abstract Push Engine throw the following error: Portal Name could not be retrieved from request.

Required Pega Marketing 7.31 hotfixes

Pega Platform VersionHotfix NumberObserved Behavior
7.4HFix-43974Cumulative fix for Pega Marketing 7.31 on Pega 7.4.
HFix-39836This hotfix resolves a performance issue with running an offer in a Pega Marketing Campaign.
7.3.1HFix-48491New 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.

Note:HFix-48491 must be installed before installing HFix-48492.
HFix-41402Encountered error while adding data association in PegaMkt7.31.
HFix-42307Upgrading segments can fail if backing database class does not exist.
HFix-39276Upgrades to Pega Marketing 7.31 experience an SQL scripting issue.
HFix-39478For the first group in the segment, if the option ‘Exclude” has been selected, the segment displays the option, 'Start with'.
HFix-39836This hotfix resolves a performance issue with running an offer in a Pega Marketing Campaign.
HFix-40241Segment 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 VersionHotfix NumberObserved Behavior
7.3HFix-36204Pega Platform 7.3 users with DB2 environments can see Decision Strategy Manager page failures.
HFix-36236Decision tables throw the following exception: java.lang.UnsupportedOperationException.
HFix-36951A campaign fails because its generated Data Flow is deleted before its execution is complete.
7.2.2HFix-31671The DSM clipboard contains an unsupported operation exception: hasValidValue.
HFix-31622The Connect Rest service does not correctly parse Boolean properties.
HFix-31717ClipboardAdapter reverts page-list items to the obj-class defined on the property, instead of original class.
HFix-31168Report definitions are unable to pass parameters to data flows using the pxOverwriteSource property.
HFix-31361You cannot validate data flow when you over ride it using a report definition with a different key.
HFix-31661Existing Simple Question rule with Rich text is not working.
NOTE: Required only when Pega Survey 7.22 is installed.
HFix-31960You cannot format headers in repeating grids to be right-justified.
HFix-35529Wait and volume constraint data flows fail with an SQL error.
HFix-37145Logs contain errors even after an item is purged.

Required Pega Marketing 7.22 hotfixes

Pega Platform VersionHotfix NumberObserved Behavior

7.3

HFix-32290Default Home page does not show the Manage NBA widget.
HFix-34963Outbound 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-35648The dataflow status function uses older data flow status names.
HFix-35663Marketing profile User Interface (UI) does not display the interaction details.
HFix-35668History tab of list segments are not displayed after upgrading to Pega Platform 7.3.
HFix-35681Next Best Action Designer does not show Real-Time containers after an upgrade to Pega Platform 7.3.
HFix-35376The V2 container service does not evaluate cookie values.
HFix-35489The purge agent does not work for campaigns configured to use a direct database template.
HFix-35683Pega Marketing 7.22 requires changes for the Revision Management functionality to work in Pega 7.3.
HFIX-36137Redundant SQL query slows the Pega Marketing campaign user interface.
7.2.2HFix-32290Default Home page does not show the Manage NBA widget.
HFix-34963Outbound SMS messages are missing originator address, Type of Number (TON), and numbering Plan Indicator (NPI).
HFix-35164Email sends fail (554 error code) when configuration does not use port 25.
HFix-35376The V2 container service does not evaluate cookie values.
HFix-35489The purge agent does not work for campaigns configured to use a direct database template.
HFIX-36137Redundant 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 VersionHotfix NumberObserved Behavior
7.2.2HFix-31622The Connect Rest service does not correctly parse Boolean properties.
HFix-31960You cannot format headers in repeating grids to be right-justified.

Required Pega Next-Best-Action Advisor 7.22 hotfixes

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

Required Pega Marketing 7.21 hotfixes

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

 

Published April 13, 2016 — Updated February 13, 2019


100% found this useful

Have a question? Get answers now.

Visit the Pega Support Community to ask questions, engage in discussions, and help others.