SR-C86952 · Issue 428816
Viewing screen capture attchments no longer requires Microsoft Internet Explorer/Silverlight
Resolved in Pega Version 8.3
Previous versions of the Pega Platform required the use of the Microsoft Internet Explorer browser with Silverlight to access old attachments added using the screen capture feature. In order to support multibrowser compatibility, the system has been updated to use javascript functions to display these images so IE/Silverlight are not required.
SR-D15747 · Issue 486019
CSP policy added to login page
Resolved in Pega Version 8.3
CSP policy was not being added to the login page as expected. This was due to the application context not yet being established for the session because the login had not occurred yet. To resolve this, the functionality has been enhanced to set the CSP headers for the login page by getting the application list information from pxSecuritySnapshot.
INC-138954 · Issue 591835
Logic updated for deepMergeObj API
Resolved in Pega Version 8.6
Issues with the embedded page values being removed when navigating from a flow action and inconsistent localization of labels and captions in a mobile app were traced to the deepMergeObj API; the logic for the API has been revised to ensure the pxObjClass property is not removed from embedded pages during the doSave function.
SR-C80948 · Issue 421766
ProfileLink control updated to resolve opening issue
Resolved in Pega Version 8.1.4
The profile was not opening when the Operator Profile link was clicked. This was traced to certain functions having been moved to javascript files that were not included by default in the ProfileLink control. To correct this, the control has been modified to include the needed javascript files and the appropriate references have been updated to match.
SR-C80948 · Issue 421765
ProfileLink control updated to resolve opening issue
Resolved in Pega Version 8.2.1
The profile was not opening when the Operator Profile link was clicked. This was traced to certain functions having been moved to javascript files that were not included by default in the ProfileLink control. To correct this, the control has been modified to include the needed javascript files and the appropriate references have been updated to match.
SR-C86952 · Issue 428815
Viewing screen capture attchments no longer requires Microsoft Internet Explorer/Silverlight
Resolved in Pega Version 8.2.2
Previous versions of the Pega Platform required the use of the Microsoft Internet Explorer browser with Silverlight to access old attachments added using the screen capture feature. In order to support multibrowser compatibility, the system has been updated to use javascript functions to display these images so IE/Silverlight are not required.
INC-135159 · Issue 580675
Logic updated for deepMergeObj API
Resolved in Pega Version 8.5.1
Issues with the embedded page values being removed when navigating from a flow action and inconsistent localization of labels and captions in a mobile app were traced to the deepMergeObj API; the logic for the API has been revised to ensure the pxObjClass property is not removed from embedded pages during the doSave function.
INC-131991 · Issue 583041
Logic updated for deepMergeObj API
Resolved in Pega Version 8.5.1
Issues with the embedded page values being removed when navigating from a flow action and inconsistent localization of labels and captions in a mobile app were traced to the deepMergeObj API; the logic for the API has been revised to ensure the pxObjClass property is not removed from embedded pages during the doSave function.
SR-118144 · Issue 171689
Corrected date display in graphs
Resolved in Pega Version 7.1.7
The incorrect date was being displayed in graphs after using the Month function alias to get the first day of the month. The grid displayed when running the show data option in the graph contained the correct date. This was caused by a problematic time conversion in graphs for a specific time zone, and has been fixed.
SR-A70596 · Issue 259237
Property validation message does not include property ID and rule name
Resolved in Pega Version 7.2.2
The property ID and rule names were being displayed in inline error messages due to them not being generally localized. This has been resolved by adding Field values to replace the static string used to show error messages for all the components and updating the error message generation in all the functions.