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.
INC-149823 · Issue 608352
DX API returns properly referenced icon class for embedded page
Resolved in Pega Version 8.5.2
When using the DX API to build an Angular JS UI, the response returned from the GET /cases/{ID}/actions/{actionID} api did not return the iconStyle for an icon class that uses a property reference when the flow is on an embedded page. This has been resolved by adding code to set the correct context for pzAPICreateJsonForModes and pzAPICreateJsonForField Rule-Utility-Function.
SR-D18725 · Issue 488208
OrgUnit delete works as expected
Resolved in Pega Version 8.4
After creating two organization units such as Unit1 and Unit11 on the same level and mapping one operator to Unit11, attempting to delete Unit1 resulted in an error indicating the operator had to be deleted first even though unit1 had no operator associated with it. This was traced to Obj-List performing a 'like' check instead of exact match check for the deletion, and has been resolved by updating the ValidateDelete activity to do obj-browse instead of obj-list.
SR-D19999 · Issue 488268
Logic updated for displaying email attachments
Resolved in Pega Version 8.4
Once an Email had been sent with attachments, additional attachments could be added to the work object at a later time and would show up when the work object was opened as if they had been part of the original transmission of the message. This was traced to the logic not accounting for for the state of the data-corr-email object and showing all the work object attachments as sent as part of the email irrespective of when the attachment was added. To resolve this, the system has been updated to save all the attachment keys that are sent as part of the email on the data-corr-email instance and use that property while retrieving the list of attachments sent on the email. If the attachment is deleted, no hyperlink will be shown but instead a message on hover on the attachment memo will note that the attachment was deleted and not available for download.
SR-D22415 · Issue 493442
Enhancement added to expose BrowserAttachmentTypeTable
Resolved in Pega Version 8.4
By default, the inline view of PDF files appears with the thread name visible. An enhancement has been made to expose pzBrowserAttachmentTypeTable as a py rule: when the DT is overridden such that return is false for PDF, the inline view is not displayed but instead the PDF is downloaded when clicked.
SR-D23723 · Issue 503089
pxGenerateExcelFile updated for handling blank dates
Resolved in Pega Version 8.4
When using a custom template for exporting to Excel, blank DateTime property column values defaulted to the current date or to 1/1/1970. To resolve this, the pxGenerateExcelFile activity has been updated to ensure that an empty date will be exported as blank and that given dates will appear in the correct datetime format.
SR-D24470 · Issue 494628
Custom attachment category parameter passed to dropdown
Resolved in Pega Version 8.4
Attempting to use the out-of-the-box “Attachments control” which was configured at design time to use a custom category where both the custom category and the section class were in the same work class resulted in the attachment category dropdown defaulting to “File” instead of the custom category. Investigation showed that the custom attachment category name configured on the control was missing in one of the pre-processing activities sequence. To resolve this, the activity Work-.pzInitAttachContent and the initAttachmentPage activity have been updated to pass the custom attachment category parameter.
SR-D24651 · Issue 495766
Proper assignment instructions sent when transferring
Resolved in Pega Version 8.4
Assignment instructions were not getting added properly when transferring to Workbaskets. Because both .pyInstruction and Param.InstructionNote are set in call Reassign (to workbasket), the same instruction value was being given twice. To resolve this, step 8 (Call Reassign) of Work-.pyReassignAssignment has been modified and will not send the InstructionNote param as instruction is already updated on the newassign page with the instruction value on reassign page in the previous step (step 7).
SR-D24950 · Issue 494567
Added explicit step page to resolve null-pointer exception with custom error message
Resolved in Pega Version 8.4
A null pointer exception was generated during case run time harness refresh after a custom error message was inserted. This was traced to a blank step page related to the custom message, and has been resolved by adding a primary step page at step 10 of the New(Work-) activity to prevent the null-pointer exception on harness reload.