SR-A19104 · Issue 237289
Ability added to set TTL on data sets
Resolved in Pega Version 7.2.1
An enhancement has been added to Data Flow datasets to allow setting the Time To Live (TTL) on DDS stores from the canvas. This allows setting an expiry date on cached data, which is essential when working with large streams of data.
SR-A19297 · Issue 237347
Added ability to set custom HTTP security headers
Resolved in Pega Version 7.2.1
XSS protections were interfering with the ability to set custom HTTP headers. To enable this, the system will use dynamic system settings from http/responseHeaders and add them to every HTTP response.
SR-A19355 · Issue 235876
Landing page Header correctly displays VBD Planner
Resolved in Pega Version 7.2.1
The Pega Marketing portal header was overlapped by the VBD Planner header, creating problems accessing the buttons on the portal header. The newly developed VBD Planner client, running as a control, did not take portal layout into consideration, and the header has been adjusted so the portal header is exposed properly.
SR-A20073 · Issue 238485
Corrected runtime handling for List Utility functions inside strategies
Resolved in Pega Version 7.2.1
When the List Utility functions 'IsInPageListWhen' and 'IndexOfPageList' were used inside strategies, the functions worked in the API(webservice) request but generated UnsupportedOperationException errors in the Program run. This was traced to a missing implementation of DSMClipboardProperty.indexOf(), which has now been added.
SR-A20073 · Issue 235672
Corrected runtime handling for List Utility functions inside strategies
Resolved in Pega Version 7.2.1
When the List Utility functions 'IsInPageListWhen' and 'IndexOfPageList' were used inside strategies, the functions worked in the API(webservice) request but generated UnsupportedOperationException errors in the Program run. This was traced to a missing implementation of DSMClipboardProperty.indexOf(), which has now been added.
SR-A20470 · Issue 240001
Twitter harvesting enhanced
Resolved in Pega Version 7.2.1
Data recovery has been improved for Pega Customer Service Social Engagement customers harvesting Twitter streaming data. If a steaming data set fails for any reason, whether due to disconnecting of the API for a short period, server failure, or for any other scenario where Tweets are not ingested in real time, the data recovery capability will fetch missed Tweets within a given set time window of recent Twitter historical data. This is done through an activity to create a Twitter search data set which can then be used to work act as a data source for the data flow. Additionally, logic has been added to identify the appropriate language for short inputs (one or two words).
SR-A21081 · Issue 242397
Strategy rule information added to tracer
Resolved in Pega Version 7.2.1
A tracer invoked with SOAP service --> Activity --> Flow --> Interaction rule --> Strategy was only showing the the executed components in its (reversed) execution order and did not show the execution strategy path. This has been fixed.
SR-A21378 · Issue 245075
Resolved Interaction Portal unexpected close
Resolved in Pega Version 7.2.1
In Google Chrome, launching a secondary portal and encountering a Content Security Policy issue relating to an image caused the secondary portal to automatically close and the developer portal to be refreshed. This was an issue with a mismatch in the pyrequestor token, and has been corrected.
SR-A21756 · Issue 244285
defined-on class error resolved
Resolved in Pega Version 7.2.1
A defined-on class error was being generated when attempting to add strategies to the overlay that referenced a decision rule defined on an SR class with a space in the name. This has been fixed.
SR-A21756 · Issue 243206
defined-on class error resolved
Resolved in Pega Version 7.2.1
A defined-on class error was being generated when attempting to add strategies to the overlay that referenced a decision rule defined on an SR class with a space in the name. This has been fixed.