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 update your bookmarks. This site will be discontinued in Dec 2024.

Pega Platform Resolved Issues for 8.1 and newer are now available on the Support Center.

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-169824 · Issue 655331

Handling added for response command beginning with "call"

Resolved in Pega Version 8.5.5

There was an issue if a response command in a web chatbot channel started with the word "call". This was due to the storage and handling of the commands in the decision table. There was a workaround of avoiding the use of "call" to start a command, but the issue has been resolved by adding quotes around the decision table result to support this response command structure.

INC-170135 · Issue 652522

Rich HTML handling added for outbound email

Resolved in Pega Version 8.5.5

The HTML content was visible in the received email when replying from the email pane in the existing email interaction. This has been resolved by adding logic to handle rich HTML for outbound email.

INC-173193 · Issue 660938

Resolved exception from isArchived

Resolved in Pega Version 8.5.5

After update, the message "ERROR - Could not retrieve the database time" was seen. This was traced to the interactions of the isArchived API with a version of Oracle, and has been resolved by adding code to skip the isArchived() API call if pzIsPegaCloud is set to false.

INC-178990 · Issue 663786

Added handling for reloading portal while ChatBot is active

Resolved in Pega Version 8.5.5

An issue was seen with UI rendering when a customer tried to reload the portal where the chatbot is deployed. Investigation showed that this was caused by the screen going to pyCreate harness instead of ChatPerform harness due tot he unexpected refresh, and has been resolved by updating the handling for the Chat Work page and the business case so that pyWorkPage is always Work-Channel-Chat.

INC-179722 · Issue 659283

Added handling for legacy HTML formatting in Email Manager Bot

Resolved in Pega Version 8.5.5

When implementing Email Manager Bot features, pyBody fields were removing the additional spaces and causing the NLP model to not extract the correct data. Investigation showed HTML formatting from older version of Microsoft Outlook created nbsp; instead of space. This has been resolved by ensuring nbsp is replaced with spaces before calling JSoup clean.

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