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.

SR-C34597 · Issue 375837

ShowLogoffTimer displays properly in Microsoft Internet Explorer

Resolved in Pega Version 8.1

The Log off time out warning pop-up was not displaying properly in Microsoft Internet Explorer and showed an unexpected scroll bar. This was due to legacy table-based markup structure that is no longer supported by Microsoft Internet Explorer , and it has been removed from ShowLogoffTimer.

SR-C34654 · Issue 374524

XSD files sent to the correct shared path

Resolved in Pega Version 8.1

XSD files were not sent to correct shared path. This was traced to the creation of the zip file missing XSD when getAllProperties is true, and has been fixed by adding logic to not skip the XSD when generateXSDForGetAllProperties DSS is enabled.

SR-C35027 · Issue 377314

Subject field of file attachment expanded to 96 characters

Resolved in Pega Version 8.1

Previously, the description text (Subject field) of a file attachment was limited to 64 characters. In order to support longer fields, the truncation at 64 characters has been removed, the property-set pyNote has been moved to Step 11, and the attachment name will be validated Database pyMemo column size (96 characters) and truncated if the length is more than db memo size.

SR-C35036 · Issue 374126

AttachmentCategoriesToSend in CorrNew fixed

Resolved in Pega Version 8.1

When calling CorrNew and passing a value to "AttachmentCategoriesToSend", the attachments in the provided category were not added to the email being sent. This was caused by a step-order error introduced when the activity was refactored, and has been corrected.

SR-C35119 · Issue 373848

Decision Table evaluation logic repaired

Resolved in Pega Version 8.1

A logic flaw was found when doing the division of nPropRowLimit with 1000. If nPropRowLimit was 30, i.e. 1000%30=10, 10 rows were missing when evaluating the decision table. The logic has now been modified to correctly evaluate the right row from the decision table.

SR-C35144 · Issue 376873

Mobile autocomplete control displays after being cleared

Resolved in Pega Version 8.1

When displaying the autocomplete list in full screen on mobile devices, attempting to clear the auto complete field using the "x" icon caused the text in the field to be cleared, but the auto complete list then did not display and instead only the last selected value was displayed until at least one character was typed in. This has been fixed.

SR-C35144 · Issue 378584

Mobile autocomplete control displays after being cleared

Resolved in Pega Version 8.1

When displaying the autocomplete list in full screen on mobile devices, attempting to clear the auto complete field using the "x" icon caused the text in the field to be cleared, but the auto complete list then did not display and instead only the last selected value was displayed until at least one character was typed in. This has been fixed.

SR-C35187 · Issue 379225

Fixed sync lock following Work Object open

Resolved in Pega Version 8.1

On Pega Client for Windows, creating or opening any Work Object from WorkList caused the Sync to stop responding and the error "keepAliveSessionTimeout :: not implemented" appeared in the log. This was traced to actions not being properly unlocked upon "reset" from the server, and has been fixed.

SR-C35349 · Issue 374606

Excel retains null fields as null instead of changing to 0

Resolved in Pega Version 8.1

When exporting report data to Excel, any null numeric property values were being automatically changed to a ‘0’. This was caused by a faulty "if" check in Export to Excel, and has been fixed.

SR-C35440 · Issue 375917

Special characters in DR description/title properly display

Resolved in Pega Version 8.1

When trying to delegate the data type rule to the business users, special characters entered in the Description/Title of Delegated rule were not rendered properly in Edit mode. This was due to a missed use case for delegated view, causing labels with parameters from section parameters to be encoded for security. It has been resolved by updating DynamicLayoutCellTemplateMetaDataGeneratorImpl to send the value without encoding.

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