INC-153801 · Issue 625946
Modified handling for updating SLA on Bulk Agent items
Resolved in Pega Version 8.6
While transferring SLA-configured assignments to the work basket using the Bulk Agent in background processing, the assignment handle of the SLA item was not getting updated to the work basket assignment handle. The error "duplicate key value violates unique constraint" was logged. This was due to the system not being able to dequeue the SLA item while it was locked by the Queue Manager as part of the background bulk processing, preventing the assignment handle from being updated on the SLA item. To resolve this, the system will perform a direct database open of the SLA item so the assignment handle is updated.
INC-154189 · Issue 617245
Harness used to determine read-only for button/text input
Resolved in Pega Version 8.6
If a button/text input was configured to always be editable in a section by using the /v1/cases/{ID}/pages/{pageID} API (say i.e PageID as Review), the button/text input was always returned as readonly. This was due to the API being hardcoded to return readonly info, and has been resolved by updating pzGetPageDetails to not force read-only and let the harness configuration decide the behavior.
INC-154778 · Issue 620907
Bulk actions filtering works in Spanish locale
Resolved in Pega Version 8.6
Filtering by only case type did not return any results when using the Bulk Transfer functionality with the Spanish locale. Investigation showed that the filter value case type had a field value set, but the localized value was not being checked in the pzPostFilterOperation in step 1 'when' condition. This has been resolved.
INC-154826 · Issue 614817
Enhanced handling for screen/non-screen/screen flow movement
Resolved in Pega Version 8.6
When using a screen flow where the last screen had a link to launch a section, a cancel button in the section that was configured with a data transform and a 'Finish Assignment' intended to move back to the screen flow did not work as expected. If a browser refresh was performed and then the cancel button was clicked, the Finish Assignment / return was triggered as expected. Because this configuration navigated to a non-screen flow, the attachOnLoad function did not load the parameter needed for maintaining error messages. This has been resolved by updating the navigation to handle this use.
INC-155469 · Issue 616910
Attach Documents Control updated for busy indicator timing
Resolved in Pega Version 8.6
When using the standard control - Attach content - to attach documents for processing in the application, selecting multiple files for upload and then clicking on the attach button before the busy indicator started resulted in not all files being uploaded. Investigation showed that the busy indicator was not set to display as soon as the attachments were added, giving an opportunity to click "Attach" before all the documents could be successfully added to the process. As part of the resolution for this issue, the busy indicator will be displayed immediately upon file selection.
INC-155559 · Issue 617503
GoToStage property marked as non-transient
Resolved in Pega Version 8.6
When refreshing or reopening the flow, the pzRuleParamsHolder did not display the gotostage property in in the change to stage shape even though the property was present in the clipboard and the flow switched correctly. This was traced to pyGoToStage being marked as transient, which caused the value to not be saved to the database. To resolve this, the pyGoToStage property is now marked as non-transient.
INC-155587 · Issue 621841
Handling added for controls applied directly to parameters
Resolved in Pega Version 8.6
After upgrade, the section displayed by the out of the box flow action pyDisplayRolesOfApplication was not displaying the role count and application name, instead highlighting values as null. Beginning with Pega 8.4, completely templated mode changes were introduced to repeating dynamic layouts. This led to parameter values which should have been passed to the field parameter to be missed because a control was added to the parameters explicitly. This has been resolved.
INC-155648 · Issue 617395
Corrected reference of PropertyExists in pyAdjustSLAPostAction
Resolved in Pega Version 8.6
The PropertyExists function was returning incorrect results. This has been resolved with the addition of a 'property exists' check in pyAdjustSLATimes.
INC-159334 · Issue 626763
Handling added for custom attachment method
Resolved in Pega Version 8.6
When sending a correspondence using the standard SendSimpleEmail activity, choosing only one attachment from the multiple attachments in the work object by passing the pxLinkedRefTo property from the clipboard page to the AttachmentKeysToSend parameter instead of passing the value to the AttachmentCategoriesToSend parameter successfully sent the message and attached it to the work object. However, opening the correspondence attached to the work object showed the attached file as blank even though the attachment was present in the receiver’s email. Research showed that during the comparison of keys in place of pxLinkedRefTo, pzinskey was used. This caused the comparison to not register as true and the attachments display was skipped. This has been resolved by updating the Data-Corr-Email.Show Html rule to use the pxLinkedRefTo field to find the right attachment. The URL encryption was also updated to ensure the links are functional and attachments can be downloaded.
INC-159807 · Issue 629187
Corrected bulk transfer status display for localized systems
Resolved in Pega Version 8.6
The transfer processing status was not displayed after performing a bulk action transfer using the French locale. Investigation showed that during bulk processing, the status whether the item processing was successful/failed/queued etc was maintained in pyBPNotes property and localized, but due to the localization it failed the check in the visibility condition. To resolve this, the pzBulkProcessItemsInHarness activity has been updated to not localize the value and set it in pyBPNotes so the visibility check runs as expected.