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-201410 · Issue 695844

Updated handling for Navigation Breadcrumb DisplayFlag

Resolved in Pega Version 8.6.3

On hitting 'previous' the old breadcrumb was visible instead of the expected flowaction. This was a missed edge case for having 'when' conditions before a subprocess shape, and has been resolved by having the pyDisplayFlag be considered conditionally so that even when the display flag for the top level subprocess is false, if the current flow action / assignment belongs to the subprocess, the system will show the breadcrumb for the same.

INC-201981 · Issue 697634

Added check for StageHistory page

Resolved in Pega Version 8.6.3

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-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.

INC-213654 · Issue 726002

Logic added to skip FLAudit class during compliance check

Resolved in Pega Version 8.6.5

An application compliance error was seen related to classes starting with FLAudit, which are created as part of field level audit history for the classgroup validation. This has been resolved by adding an extra condition to the Rule-Obj-Class-.Validate activity to check if inheritance is from "FLAudit-" class, and if so to skip them as their purpose is similar to History- classes which are ignored for the class group validation.

INC-215354 · Issue 712665

Data- flow actions working in Bulk Process

Resolved in Pega Version 8.6.5

When trying to render a flow action whose 'applies to' class was inherited from Data-, an error was generated indicating that the flow action could not be found. This was traced to non Work- flow actions not being correctly populated, and was an inadvertent side effect of work done to set class for inheritance if Work- is not present. This has been resolved by updating the pzPreBulkProcessModal activity to set the TempWorkPage class to Work- only if .pyActionName is pyTransferAssignment.

INC-215499 · Issue 714489

Assignment routing updated for swimlanes

Resolved in Pega Version 8.6.5

Routing options were not working for workbasket routing when using swimlanes. Investigation showed that when an assignment was added inside the swimlane, the assignment type value was defaulting to Worklist on submit of the assignment property panel. Manually changing it to workqueue did not make the routing section visible. This has been resolved by adding a 'visible when' condition to the "Route To" field to check if the assignment is not in the swimlane. The same check has been added to a 'disable when' condition for the 'Assignment type' drop down.

INC-216406 · Issue 723284

Attachment preview works for filenames with special characters

Resolved in Pega Version 8.6.5

Attempting to preview attachments from the file and attachments view was not working if the file name had special characters. The browser console showed errors complaining that an unrecognized character was present. This has been resolved by adding crossScriptingFilter to sMemo to allow special characters in the attachment preview filename.

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