Skip to main content

Resolved Issues

View the resolved issues for a specific Platform release.

Go to download resolved issues by patch release.

Browse release notes for a selected Pega Version.

NOTE: Enter just the Case ID number (SR or INC) in order to find the associated Support Request.

Please note: beginning with the Pega Platform 8.7.4 Patch, the Resolved Issues have moved to the Support Center.

INC-174045 · Issue 650735

DSS added to control merge strategy

Resolved in Pega Version 8.5.5

The activity page merge option takes merge strategy as input and supports different merge strategy options like 'Replace', 'Update' etc. Previously, V1 DX APIs defaulted to REPLACE as the merge strategy; this has been updated to support both 'REPLACE' and 'UPDATE' merge strategies which can be controlled with the new DSS "v1MergeStrategy". The DSS to customize the merge strategy for v2 APIs is 'v2MergeStrategy', which also takes the values 'REPLACE' and 'UPDATE', which are for merge strategy '1' and '3' respectively. The default strategy from Pega 8.6 forward is 'UPDATE' and any other value other than the above two values will be considered as 'UPDATE'.

INC-174267 · Issue 657129

Wait action persists when using Urgency Adjustment

Resolved in Pega Version 8.5.5

When using the Urgency Adjustment (pyAdjustAssignmentsla standard local action), once a case reached the wait action and the goal and deadline were updated the previous pyWaitAction was not being stored. This has been resolved by ensuring the previous pyWaitAction will be stored and passed to the AddAssign activity.

INC-174511 · Issue 653620

Attachment errors correctly triggered for subsequent copies of the same file

Resolved in Pega Version 8.5.5

After attaching a file larger than 4MB and triggering a dirty popup error, uploading the same file again did not trigger the error. This was traced to the onChange event of the File Input Tag not being triggered when the same file is attached again, and has been resolved by adding handling for attaching the same file in error scenarios (File Max Size,File Size Zero).

INC-175151 · Issue 658699

Bulk Actions filter working for embedded date properties

Resolved in Pega Version 8.5.5

For Embedded DateTime properties, the pyStringType was returned as "Date Time" instead of "DateTime", causing a mismatch in the filter criteria for Bulk Processing. This has been corrected.

INC-175630 · Issue 653862

Application selections only announced when visible

Resolved in Pega Version 8.5.5

The elements of the application switcher were being announced by the NVDA screen reader even when toggled off, i.e. not visible. The issue was occurring because the focus was remaining at the search bar even after closing the app switcher window, and has been resolved by adding the necessary logic to switch the focus.

INC-175882 · Issue 658640

Updated bulk action audit history logic and security

Resolved in Pega Version 8.5.5

After update, using the standard bulk action feature did not record an audit history entry for the SLA action on a case. This was traced to changes made around authorization for opening worklists when using pzBulkProcessItem that limited the audit history to reassign, transfer or transfer assignment, and has been resolved by updating the login the Work-pzBulkProcessItem activity. In addition, the Require authentication to run checkbox has been enabled on the Security tab of the activity, and the Allow invocation from browser checkbox has been disabled.

INC-188469 · Issue 714844

Updated retainLock for DoClose activity

Resolved in Pega Version 8.6.5

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-208394 · Issue 713554

Error handling updated for Data-Work-Attach-File

Resolved in Pega Version 8.6.5

If a file is uploaded which has the same name as an existing case attachment or if any issue happens during file attachment, the attachment will fail and an error message is displayed with an option to cancel the operation. However, even if the upload was not successful the related Data-WorkAttach-File instance was created and persisted in the Workattach table. Investigation showed this was caused by the process for persisting the Data-WorkAttach-File record occurring prior to the process that returns the errors, and this has been resolved.

INC-209404 · Issue 710406

MultiFilePath supports file upload with leading special character

Resolved in Pega Version 8.6.5

Updates have been made to the pzMultiFilePath control in order to support uploading a file with a special character such as "%" at the beginning of the name.

INC-210787 · Issue 710393

Multiple child case assignments open correctly in Ajax container

Resolved in Pega Version 8.6.5

After configuring two cases with a parent-child relationship, the child case was configured with a parallel process with two assignments. When trying to open the child case assignments in an Ajax container, only the first assignment would open. Investigation showed this was caused by the "reloadAlways" parameter not being sent to openAssignment due to a custom control being used. To resolve this, the reloadAlways has been added as an argument to the OpenAssignment function call in pyAssignmentsLabel.

We'd prefer it if you saw us at our best.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us