SR-B51449 · Issue 308503
Property Record localization added for Pega Marketing
Resolved in Pega Version 7.3.1
Localization has been added for Property Record Configuration text in the Pega Marketing application.
SR-B51450 · Issue 308504
Property Record localization added for Pega Marketing
Resolved in Pega Version 7.3.1
Localization has been added for Property Record Configuration text in the Pega Marketing application.
SR-B51450 · Issue 313658
Property Record localization added for Pega Marketing
Resolved in Pega Version 7.3.1
Localization has been added for Property Record Configuration text in the Pega Marketing application.
SR-B51450 · Issue 313738
Property Record localization added for Pega Marketing
Resolved in Pega Version 7.3.1
Localization has been added for Property Record Configuration text in the Pega Marketing application.
SR-B43400 · Issue 307258
Localization added for field value used in 'Enter a Short Description' validation message
Resolved in Pega Version 7.3.1
Localization was failing for the 'Enter a Short Description' validation message when using a Field Value due to the message rule containing spaces. To fix this, a new message rule has been created without spaces in the same ruleset so that it is available for override use in the ruleset.
SR-D32991 · Issue 504129
Email Discussion Thread retains Formatting
Resolved in Pega Version 8.3.1
CSS styles were not being retained in the discussion thread when replying to InboundCorrespondence cases. This was traced to a missing value in Param.latestReply activity pzCreateExternalPostFromMail, and has been resolved by setting an initial plain text value to the param.latestReply before it is set with the HTML value. This prevents having a blank parameter value if the incoming HTML value is empty.
SR-D28342 · Issue 504970
ChatMashup loading issue with IDP resolved
Resolved in Pega Version 8.3.1
When using a harness containing chat scripts via Mashup that called an activity to set parameters, attempting to launch the Mashup from an external application failed on the first attempt: an incorrect URL was generated and the activity was not triggered, resulting in an empty harness. The second attempt to launch the Mashup worked as expected. This was seen when using an IDP initiated Login with query string - pyActivity= classname.ActivityName, and there was a workaround to use SP initiated login or to use the activity URL directly on the IDP portal. Investigation showed that the resourcePath was coming as http in SSL enabled system, but the reqURI was still https. To correct this, the system has been updated so that if the reqContextURI starts with https and the requestURL starts with http, then the requestURL will be converted to https.