INC-201981 · Issue 697633
Added check for StageHistory page
Resolved in Pega Version 8.7.1
After update, the pyDisplayStages section was not visible in pyCaseMainInner due to the 'when' condition pxHasStages not being satisfied. This was traced to a customization for the pyStartCase flow in one of the case types which resulted in a blank pxStageHistory page being set under pyWorkPage, and has been resolved by adding a 'when' condition to check whether pxStageHistory page exists so the step will only execute if the pxStageHistory page is present.
INC-203595 · Issue 700595
Updated retainLock for DoClose activity
Resolved in Pega Version 8.7.1
After sending an external email notification from a case, attempting to use the "close" button resulted in an access denied error. This was traced to a missed use case for recent security improvements which resulted in not setting the required parameter retainLock for the DoClose activity, and has been resolved.
INC-204676 · Issue 699112
Localization added to subject line for SendEmailToAssigneeOnGoalTime
Resolved in Pega Version 8.7.1
When a Callback case was created and the assignee notified by email, the subject line was not localized. This has been corrected.
INC-207320 · Issue 701083
Email Approver shown in audit
Resolved in Pega Version 8.7.1
Email Approver activity was not being shown in Audit. This was traced to the queue instance primary page missing the necessary pyInboundEmail page property from pyCreateAndManageWorkFromEmail, and has been resolved by updating the listener activity to copy the needed value to a property called pyEmailFrom which will be used to record the events in the audit.
INC-183706 · Issue 685830
Added null check for DynamicAppenders
Resolved in Pega Version 8.7.1
Null pointer exceptions were seen for Pulse. This has been resolved by adding a null check in the DSS save/update process.
INC-185117 · Issue 680899
Check added to disable offset support for older versions of Oracle
Resolved in Pega Version 8.7.1
An ORA-00933 error was generated after upgrading from Pega 7.1 to Pega 8.5. This was traced to a conflict between Oracle 11g and the Pega 8.5 platform related to an OFFSET statement being added to a query for a version of Oracle that doesn't support it. The preferred solution is to upgrade Oracle to address this, but in order to support backwards compatibility a check has been added which will disable offset support in Oracle if productversion <=11.
INC-202677 · Issue 698989
Handling added for missing expose.accessGroup property
Resolved in Pega Version 8.7.1
After exposing an existing page group and page list properties along with single value properties using a declare index, running the Column Populator tool prpcServiceUtils to populate the historical data resulted in the single value properties being updated in the exposed column properly, but the page group and page list properties were not updated in the declare index table. On new case creation the declare index tables were updated. This was traced to the default expose.accessGroup not being set for the user, and has been resolved by adding a check and handling that will add the missing property in prpcserviceutils.properties defining the access group for the Rule-Declare-Index of the classes being exposed if it is not present.
INC-173068 · Issue 654066
HTML tags escaped in Audit History field values
Resolved in Pega Version 8.5.6
The case narrative section was showing case statuses with encoded special characters such as % or ( ), resulting in entries such as "Status changed to Complete &# 40;approved& #41; !@##$: %^& amp;*&# 40;&# 41;_&# 43;.</div>". This has been resolved by updating the PyMemo field from type Text Input to DisplayAsLiteral for case narrative, which matches the setting for case history.
INC-178650 · Issue 673547
Cross-site scripting protections updated
Resolved in Pega Version 8.5.6
Cross-site scripting protections have been updated around the DisplayAttachment function.
INC-180275 · Issue 666454
Collaboration control hidden if data type is delegated
Resolved in Pega Version 8.5.6
When collaborating using a customized CaseManager portal with some delegated data types, the admin user refreshing the Data Type view changed the collaborator's view from the portal to show the Data Type tabs, allowing the second person to open rules (properties, Data Pages, etc) and see the configuration even though they could not make any changes. This has been resolved by updating pzDataTypeDelegated to display the collaboration control only if pzDelegation is false.