INC-138348 · Issue 599770
Added parameter skipPropertyEvaluation to handle CSS in email HTML
Resolved in Pega Version 8.5.2
While sending an email with custom HTML appended to the email body, a "+" sign in the body was causing the correspondence generation to fail. Investigation showed that if there were CSS classes with braces in the message body, the braces were being removed and replaced via "+" symbol in step 21 of CorrCreate activity. To resolve this, a new Boolean parameter skipPropertyEvaluation has been added in the CorrCreate activity to handle the decision to either evaluate the logic or not, and the pre-requisite will be to resolve all the property references before calling this activity so custom CSS braces { } will be honored when the message body is sent.
INC-141751 · Issue 596136
DragAndDrop attaching large file properly disables 'X'
Resolved in Pega Version 8.5.2
When a large file was attached using the DragAndDrop feature, the 'X' icon/button was not disabled. This made it possible to click 'X' and perform other actions during the upload, which caused the screen to freeze and required a browser refresh to continue the work. This was traced to incomplete work done on large file uploads, and has been resolved by ensuring the busy Indicator shown will be applied to the complete screen to avoid any other actions being performed.
INC-142660 · Issue 595390
Pega API system management launches correctly from Help
Resolved in Pega Version 8.5.2
The Pega System Management API did not work when launched from help window, although other APIs such as Case Management were working fine. This has been resolved by updating the basePath in pzSystemManagementDocumentation.
INC-143861 · Issue 597557
pzIsScalar 'when' rule updated for Value list and Value group
Resolved in Pega Version 8.5.2
When using the GET/Cases/{ID} API to fetch details about a case, an intermittent HTTP 500 error appeared. This was traced to the 'when' condition pzIsScalar being returned as true for the ValueList property types and trying to set the value on the summaryData embedded page. This has been resolved by updating the pzIsScalar 'when' rule to better handle Value list and Value group.
INC-144358 · Issue 601012
Localization added for "Automatically" and "Manually" field values
Resolved in Pega Version 8.5.2
The Dutch translation of "Child case [Case_type] [Case_id] has been [Instantiation_mode] instantiated" used the hard-coded English expression "manually". This has been resolved by adding the "Automatically" and "Manually" field values to localization.
INC-146339 · Issue 600744
ViewID parameter passed as part of DX API response payload for level 5 applications
Resolved in Pega Version 8.5.2
Recent work to not consider production level and always pass 'viewID' parameter as part of DX API response payload was not working for cases where the APIProductionLevel was 5. This was a missed use case based on a condition that remained on the ViewID parameter, and the condition has now been removed.
INC-146564 · Issue 607856
DX API returns application specific validation messages
Resolved in Pega Version 8.5.2
When trying to validate the input swagger details with application specific conditions, the create case DX API did not return the validation messages from application but instead returned a "500 Internal Server Error". Investigation showed that the error parameter was not set on validation fail, and this has been corrected.
INC-146780 · Issue 602023
Updated ArchivedCaseHistory visibility
Resolved in Pega Version 8.5.2
After enabling case archiving on Pega Cloud, it was possible to search the cases from case manager studio, but the audit details were missing. Previously Audit History was directly displayed based on whether archival was enabled or not. As part of Field Level Audit, a new property called pyHistoryViewType was introduced which is a prompt list with ALL and FIELD as its values. This property checks whether FLA is enabled or not, and based on that value ALL is set. In this case, because FLA was not enabled, the pyHistoryViewType property was empty and the HISTORY tab was not shown. To resolve this, the pyArchivedCaseHistory section table 2 visibility condition has been updated.
INC-147658 · Issue 604684
Handling added for Top and Primary page references in flow action
Resolved in Pega Version 8.5.2
Handling added for Top and Primary page references in flow actionAfter upgrade, if a flow action had a class of the section which was different from the class of the flow action, the DXAPI code retrieved the section as the same class of the flow action and not the class defined in the flow action. In flow action, the section was configured be rendered in the context of page reference as Top, however, this was not handled so the section was resolved in the context of primary page. This has been resolved by adding the missing handling for Top and Primary page references in flow action.
INC-148817 · Issue 604969
Added check for ABAC policy to getassignmentdetailsinternal
Resolved in Pega Version 8.5.2
When an attribute based access control (ABAC) policy was defined on a particular class, the policy was properly applied when browsing instances of the class and directly opening the work object. However when an associated assignment was processed via the DXAPI (using the assignments service) the security was not applied and users who should not have access were able to progress the case. This has been resolved by adding a check in the pzgetassignmentdetailsinternal activity to check for work object opening security.