SR-D76943 · Issue 541371
SmartInfo icon functional for reports
Resolved in Pega Version 8.2.6
After enabling Smart Info for a list Report definition, the activity was not getting called and section was not getting displayed. Investigation traced this to encryption added in an earlier version which caused the SmartInfo API to receive a parameter in an unexpected format. Because this incompatibility would affect all APIs not compatible with the encryption, this encryption for the API has been reverted.
INC-167139 · Issue 658620
Functions are packaged with "--" suffix
Resolved in Pega Version 8.5.5
Validation rules were not executed as expected. Investigation showed this was caused by functions referenced in the validate rule through a function alias being packaged without the "--" suffix (for example isNameInvalid--(String) was packaged as isNameInvalid). This has been corrected.
INC-200877 · Issue 693824
Functions supported in Authorization Service
Resolved in Pega Version 8.6.3
An enhancement has been added to support operator page context evaluation with a Rule-Utility-Function during property mapping evaluation.
INC-200877 · Issue 693823
Functions supported in Authorization Service
Resolved in Pega Version 8.7.1
An enhancement has been added to support operator page context evaluation with a Rule-Utility-Function during property mapping evaluation.
INC-193071 · Issue 686647
Find by ID functionality repaired
Resolved in Pega Version 8.5.6
After update, the Find by ID Functionality was not working as expected. This was an unintended side effect of work done around the inheritance of default values when the portal pyPortal.pyDesktopType was set to Composite, and has been resolved by modifying the previous work to move the check to verify if the pxCurrentWorkPool== "" to a later step.
SR-120556 · Issue 180535
Dirty prompts functioning with JAWS
Resolved in Pega Version 7.1.8
When a dirty work object is closed, you are warned with a dirty prompt. When this dirty prompt is sourced via the modal/section pyDirtyCheckConfirm, JAWS did not gain focus to read this prompt and a manual click on this was required to read any elements. This was an issue where JAWS wasn't reading the dialog because there was no role attribute attached. This has been corrected.
SR-123235 · Issue 183263
Additional localization for attachments functions
Resolved in Pega Version 7.1.8
Localization has been added in the attachments section for the "Attachment" link, "Attach URL", 'Add new party" in the work parties modal, and the "Save Draft" button.
SR-128986 · Issue 194639
Accessibility Report function removed
Resolved in Pega Version 7.1.8
The accessibility report required Quirks mode in order to render properly and be functional. This meant a modern browser such as Microsoft Internet Explorer 10/11 had to run in compatibility mode. This was not desirable behavior, as it meant the report was not compatible with non-Microsoft Internet Explorer browsers such as Google Chrome/Firefox and the Quirks mode requirement directly conflicted with the new requirement to use Standards mode in Designer studio and native Pega 7 developed apps. Therefore, the Accessibility Report has been deprecated and removed and developers are encouraged to use third party tools such as FireEyes to assess their application from an accessibility compliance perspective.
SR-129611 · Issue 197287
Corrected CheckPrivilege function in BulkAssign
Resolved in Pega Version 7.1.8
The RUF pxCheckPrivilegeInWorkClass (called from OpenAndLockWork) was changing the name of the newAssignPage, causing downstream failure of pzBulkProcessItems. The error occurs when a Bulk Transfer operation is performed and the user does not have the proper Role, resulting in a call to the canPerform Access When Rule that then led to pxCheckPrivilegeInWorkClass changing the name of the step page. To fix this, the parameter will be assigned to the "newAssignPage" or primary page in the OpenAndWorkLock activity.
SR-B77272 · Issue 326822
TransformerFactory security functions reverted
Resolved in Pega Version 7.3.1
Export to Excel was broken in the IBM environment. This was related to compatibility with security updates which were not consistently implemented by TransformerFactory installations. To resolve this condition, those security changes have been removed from the following functions: DCOdocumentToBytes DCOnodeToString DCOgetStringFromDocument