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-D3788 · Issue 437778

Corrected temp page reference for save-as in CreateAndManageWorkFromEmail

Resolved in Pega Version 8.3

Attempting to save-as pyCreateAndManageWorkFromEmail was failing due to a missing reference to TempCurrentPage in Pages and Classes. This has been corrected.

SR-D22594 · Issue 437875

Fallback handling added for Cryptographic exceptions

Resolved in Pega Version 8.3

Cryptographic Exceptions were being generated while decrypting query parameters. This occurred when a node restart happened before passivation time out: the existing encryption keys are lost and new encryption keys are generated on node restart, resulting in any requests encrypted with previous keys (before node restart) to fail decryption. This issue did not occur when a requestor was passivated or nodes were quiesced, only when a node was abruptly shutdown. To resolved this, handling has been added which will fallback and decrypt with an older key if an exception is encountered when decrypting with the current key.

SR-D1458 · Issue 437893

Property name mapping moved to DSM side to ensure consistent results

Resolved in Pega Version 8.3

If a Data Set rule was used to retrieve the records of the Data Class, the property names appeared to be changing randomly in the OperationResult Clipboard Page when the name exceeded 30 characters. This was traced to NativeSQL trimming and hashing any aliases that were longer than 30 characters, and has been resolved by moving the mapping back of property names to the DSM side.

SR-D1716 · Issue 438107

Fixed expand when issue on dymanic layout with custom header

Resolved in Pega Version 8.3

After upgrade, a Dynamic layout with collapsible type Container setting which included a custom section to show the text and image in place of text had an 'expand when' condition applied that caused the entire dynamic layout to be malformed and show the raw HTML code if there was an error. This was traced to the system rendering the dynamic layout in non-template form if the header has a JSP section include, leading to the expandable layout header div HTML elements getting mixed up with the custom header sections HTML code due to the aria-label attributes. This has been resolved by removing the section stream from aria-label in RUF - GridHeaderElements.

SR-D3036 · Issue 438137

Password change error message clarified for invalid characters

Resolved in Pega Version 8.3

When an operator updated their password and and included special characters other than those specified in the security policies, an error appeared that was not easy to understand. This message has been updated to clearly indicate that the password attempt includes invalid characters and needs correction.

SR-D564 · Issue 438145

Removed job for column population when it is not needed

Resolved in Pega Version 8.3

While optimizing the data type class properties, the column population job failed with the exception "ERROR - Exception in column population ... column pc1.pzinskey does not exist". Although there was no impact from this error, the SQL exceptions in logs could cause confusion. This has been resolved by updating the system so that if the table has no pzinskey or stream columns, no job will be queued for column population.

SR-D3144 · Issue 438160

Corrected agent scheduling issue for different server time zone

Resolved in Pega Version 8.3

When a server timezone and the agent schedule used different time zones, a server restart with cleared extract marker resulted in BIX agents no longer running automatically due to the next run showing as scheduled in the past. This was traced to the method used to compare start date time, and has been resolved.

SR-D2788 · Issue 438260

Stale transaction error resolved for Robot Manager deletions

Resolved in Pega Version 8.3

The UI was hanging and displaying a stale transaction error after multiple entities were deleted from the Robot Manager UI. This has been resolved by adding clientFrame handling for SPA cases separately in the pega_ui_modaldialog js file.

SR-D5079 · Issue 438379

Handling added for empty UILabel in grid fields

Resolved in Pega Version 8.3

When using a Datetime property with a default format, opening the filter popup and clicking on the 'select all' check box caused the format of the values to break. This was traced to ".pyUILabel" being passed as empty, and handling has been added for that in "pzUniqueValuesGridFields".

SR-D2796 · Issue 438392

Corrected Recents list resize issue in IE

Resolved in Pega Version 8.3

When using IE, opening the Pega Developer Studio to the landing page correctly resized the Recents list unless another tab was open. If there is another tab, the the resizing did not work and the scroll bar only allowed movement to the left. This has been corrected by setting the position to absolute for iframe(designer studio tabs) for IE.

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