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-129714 · Issue 198126

Added ability to access operator with deleted division/org

Resolved in Pega Version 7.1.8

When an operator as associated with a division and that division was deleted, the existing operator record could not be opened in the developer portal due to a validation error (in this case, associated with a missing division). While there are validation checks associated with deleting organizational units and divisions that safeguard against deletion, it was still possible to delete a non-empty division directly. When this occurred, the operator ruleform could not be opened due to being in an invalid state. Handling for this has now been added, and an operator record can be opened in DS even if the corresponding org/org unit/div has been deleted.

SR-129722 · Issue 197103

Removed extra white space in Microsoft Internet Explorer 8

Resolved in Pega Version 7.1.8

When using the Microsoft Internet Explorer 8 browser, extra white space appeared above the 'next' button when declare expression was fired in a screen flow which grew with each declare firing. This has been corrected by updating the last condition to check for the 'display' property.

SR-129723 · Issue 200683

Added ability to customize pyMessageKey column of a history record

Resolved in Pega Version 7.1.8

In order to allow customization of the pyMessageKey column of a history record, it is now possible to call the extension activity pyAddWorkHistoryDefaults in Flowvwhen the work page is not null.

SR-129725 · Issue 198663

Enhanced SLA reporting available

Resolved in Pega Version 7.1.8

In order to facilitate detailed reporting on bad SLA items, the following rules have been added: 1. Class to EMBED-QUEUEERRORDETAILS to contain error properties. 2. Page list type property .pxQueueErrorDetails in System-Queue- class. 3. Text type property pxErrorMessage in EMBED-QUEUEERRORDETAILS class. 4. Datetime type property PXERRORDATETIME in EMBED-QUEUEERRORDETAILS class.

SR-129733 · Issue 199324

Enabled word wrap for RD export to PDF

Resolved in Pega Version 7.1.8

After export to PDF from RD, values were getting truncated or being displayed under the column and the column alignment was disrupted. Word wrap has been enabled to fix this display issue.

SR-129768 · Issue 200019

Resolved error saving to lower version unlocked ruleset

Resolved in Pega Version 7.1.8

An error was encountered when attempting to save a rule in an unlocked lower version if a higher level locked version existed. This has been corrected by removing a redundant post condition in the activity Rule-RuleSet -> pzGetOpenRulesetVersions.

SR-129876 · Issue 198152

Modified filename verification for Pulse

Resolved in Pega Version 7.1.8

A problem was encountered when uploading files from Pulse if the filename contained special characters. A legacy verification method existed that tested the validity of the filename by creating and then deleting a test file, but that encountered errors when the file system was not writable. To avoid this issue, the validation method has been updated to check for special characters in the file and then decide the file name validation.

SR-129891 · Issue 198738

Reworked decision table cnflict check logic

Resolved in Pega Version 7.1.8

In a decision table, using expressions like property-property caused the decision table to report a non-existent logic conflict because there was another column with different data present. To void this, the system will skip the conflict check for Columns if the property type cannot be determined, eg: column type contains expressions.

SR-129892 · Issue 196786

Error handling improved for BIX extraction called by an agent

Resolved in Pega Version 7.1.8

Running BIX extract from an agent (which calls activity runExtract) caused the BIX logfile to grow to enormous size due to an infinite loop after encountering a JDBC 'connection reset' error. Handling for this error has now been added to ensure smooth extraction from an agent.

SR-129898 · Issue 197990

Error handling added for ConnectJava wizard

Resolved in Pega Version 7.1.8

A null check has been added to resolve a null pointer error generated by the Connect-Java Wizard -> GenerateJPForConnect.

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