INC-194594 · Issue 684714
Parameter handling updated for cloned environment
Resolved in Pega Version 8.7
The Editable data page parameters were not getting set in a cloned environment. This has been resolved by adding code to detect the use case ('append and map to action' with 'a new page' relation) and let it fallback to legacy code generation.
INC-142569 · Issue 597899
CORS headers added for Health check URL
Resolved in Pega Version 8.5.2
Pega Health Check URLs were throwing CORS error when invoked for application Health checks. This has been resolved by adding CORS headers for pingService responses.
INC-170950 · Issue 652332
Handling added for datetime set by relative reference
Resolved in Pega Version 8.7
When initializing a datetime property contained within .pxPages() in a data transform rule, if the property being set applied to @baseclass it was initialized as decimal string while all other properties were handled as normal GMT-based Pega date time strings. Investigation showed that the decimal value was set when the target page was given by a relative reference like .pxPages(TEXT) which was also defined on Pages & Classes. This has been resolved with an update to detect relative reference as page name in Pages & Classes tab and fall back to the old assembler.
INC-177353 · Issue 658727
Debug logging improved for LibraryRuntime
Resolved in Pega Version 8.7
No error logs were generated when an access group was pointing to a base ruleset with different major version from that of the system. This has been resolved by improving the debug logging for the following classes: LibraryRuntime LibraryMetadataCache .findTripletForCurrentRulesetList
INC-135720 · Issue 594791
Case link shows in Social messages for the old cases
Resolved in Pega Version 8.5.2
After upgrade from v7, the case link was not visible for the cases that were created in the old platform version. In Pega 7.1.7, metadata was stored in .pyPrivacyContextor while the later versions are using .pxContextType for Case type to show the related data. To resolve this, new properties have been implemented to hold the Case ID link
INC-189811 · Issue 679935
Updated XMLDataToPage privilege
Resolved in Pega Version 8.7
Cases were not being created or moved due to a privilege issue on EndUser portal after update. This was traced to the XmlDataToPage activity now including the OpenDeveloperForm privilege, which end user operator profiles do not have. This was a missed use case, and has been resolved by updating XMLDataToPage so it requires authentication but not privilege to run.
INC-161214 · Issue 640893
Push notification of shape-created child case opens correct case
Resolved in Pega Version 8.7
In a scenario with two cases, CaseA and its child case, CaseB, when CaseB was created from CaseA with a standard shape and a push notification was sent right after creation, the "Custom message" notification received on a mobile device opened CaseA instead of CaseB. If CaseB was created as a standalone case, the push notification opened it properly. This was traced to an edge case where the Primary.pzInsKey was empty because the child case was not available in database when the push notification payload was created by push shape, leading to the CaseID retrieved by getInstanceHandleFromPage to fetch the parent Case ID instead. This has been resolved by modifying the process to get the pzInsKey from the step page.
INC-172692 · Issue 650615
InsID will be derived from handle if null for upgrade
Resolved in Pega Version 8.7
Upgrade from Pega 7 to Pega 8 failed with a null pointer exception in the “Upgrade Context” target. This was traced to a rule where the pxInsID was null. To resolve this, an update has been made to derive the InsID from handle when needed.
INC-183485 · Issue 681360
Updated background refresh for off-screen worklist
Resolved in Pega Version 8.7
After update, performance impacts were seen on the field service mobile app. This was traced to Worklist refresh, and has been resolved by adding an update which will postpone the refresh when the worklist webview is in the background (not visible on the screen).
INC-175000 · Issue 657006
Handling added for Address Map control in Microsoft Internet Explorer 11
Resolved in Pega Version 8.7
Microsoft Internet Explorer 11 does not support Class, async, await and arrowed functions due to not implementing the necessary EC6 features. This caused Address Map Control to not work in this browser because pypega_map_googlegis js creates a js class. To resolve this issue, alternate methods have been added for use with Microsoft Internet Explorer 11.