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.

SR-C8702 · Issue 349662

Fixed cataloging for framework hotfixes with non-java code

Resolved in Pega Version 7.4

The system was unable to catalog Strategic Application hotfixes that included non-java code instances (e.g. .xml or .properties files) due to Framework hotfixes using a different version format that caused validation failure. To correct this, the system will bypass redundant release version validation for Strategic Application hotfixes so that it can catalog non-java code instances.

SR-C8702 · Issue 344809

Fixed cataloging for framework hotfixes with non-java code

Resolved in Pega Version 7.4

The system was unable to catalog Strategic Application hotfixes that included non-java code instances (e.g. .xml or .properties files) due to Framework hotfixes using a different version format that caused validation failure. To correct this, the system will bypass redundant release version validation for Strategic Application hotfixes so that it can catalog non-java code instances.

SR-B47858 · Issue 304348

Access Group Guardrail warning removed from password change

Resolved in Pega Version 7.4

Changing the password for the '[email protected]' operator generated the warning: 'The same Access Group should not be shared by Operators and Requestor Types. Access group PRPC:Agents was also referenced by Requestor Type DATA-ADMIN-REQUESTOR PRPC!BATCH'. The password change did take effect as expected. This guardrail warning was shown if the Access group used by the [email protected] operator, i.e. PRPC:Agents, was specified in any of Data-Admin-Requestor instance, and has been resolved by removing the unnecessary check.

SR-B96972 · Issue 343423

Specification rule save-as loads requirements

Resolved in Pega Version 7.4

While doing 'Save As' of a Specification rule from a locked ruleset version to a higher unlocked version of the ruleset, the linked Requirements were not shown in the Requirements section under the Details tab. Sometimes a refresh would show the requirements, but intermittently an exception would be generated. This was traced to the system not auto-populating the requirements list on 'save as' of the specification, and code has been added to PostActionSaveAs of the 'Rule-Application-UseCase' class to populate the Requirements link on 'save as' of this rule.

INC-147654 · Issue 642186

Updates to displaying embedded images in cases

Resolved in Pega Version 8.3.6

Sending an email with an embedded image to the email ID associated with the email listener successfully created the interaction case, but the embedded image was not displayed when the case was opened from the work-basket. A rule-not found exception was seen in the tracer for pyGetImageDisplay, the rule responsible for displaying the images in the ET pane. Investigation showed that when URLObfuscation was turned on, the decryption of the URL was not successful because "&" had been encoded to '& amp;'. This has been resolved by calling the activity pyGetImageForDisplay using URLMapping instead. An additional issue was seen with displaying images in the email interaction pane where the additional empty new lines moved the image outside the intended place. This was traced to a customization for the reply area which used the pyHighlightedMessage property and converted newlines to br tags even in HTML mode. To resolve this, pyHighlightedMessage has ben modified to convert newlines to br tags only if the mode is plain text.

INC-152776 · Issue 621243

Check added for HTML and linefeed combined in email

Resolved in Pega Version 8.3.6

In the Interaction right hand pane Email triage widget, additional line breaks were seen when displaying email message data that contained table tags. This was a missed use case for email which contains both HTML and '\n', which resulted in the system replacing '\n' with < / br >. This has been resolved by adding a check whether the content has HTML tags which will avoid the replacement.

INC-165188 · Issue 635774

Third-party links allowed to pass target attribute in anchor

Resolved in Pega Version 8.3.6

Attempting to connect to Docusign, a third party application, via Email in an interaction portal was not working, and the error "account.docusign.com refused to connect" appeared. This was caused by the HTML data being sanitized so the attribute 'target' was not allowed to pass and the application could not open in a new tab. To resolve this, an update has been made that will allow the target attribute for an anchor tag.

INC-167311 · Issue 646477

Updated upgrade handling for migrating work objects

Resolved in Pega Version 8.3.6

After upgrading from Pega 6.2 to 8.3, the work migrated work objects were missing SLAs due to missed entries in the assignment tables (PC_ASSIGN_WORKLIST/ PC_ASSIGN_WORKBASKET) . The SLA was firing, but the processing failed due to the fact the runtime could not resolve a 'AddHistoryPage' library function. In this case, multiple upgrades of the application dating back to Pega 4 resulted in the runtime context containing older ruleset versions in higher ruleset versions, hiding the underlying Pega 8 version of the rule. For releases prior to Pega 7.3, Rule-Application was stored in pr4_rule and will be migrated to pr4_rule_application during upgrades. However, since Context Upgrade is run before Optimize Newly Exposed Columns, the pyDependsOnName won't always be populated. To resolve this, the system will filter based on the value in the blob rather than the exposed column so there will be a value regardless of the upgrade-from version.

INC-172675 · Issue 649451

Configuration added for extending queue processor timeout

Resolved in Pega Version 8.3.6

Alerts for queue processor (QP) items which took more than 15 minutes to run could result in the system marking the node as 'unhealthy'. In environments with Pega Health Check enabled, this would shut down the node gracefully. It was not possible to change this default as it was hardcoded. In order to support systems that may have custom processes that run beyond 15 minutes, a a new setting has been exposed that allows configuration of the interval after which a node with long-running queue processor is marked as unhealthy and is restarted. By default this remains 900000 milliseconds / 900 seconds / 15 minutes, but it may be adjusted up to 24 hours to avoid premature node shutdown. The stale thread detection mechanism will take that setting into account and use the provided value or default to 15 minutes if the value was not provided. In addition, the threshold's units in the UI have been changed from ms to seconds.

INC-147654 · Issue 642189

Updates to displaying embedded images in cases

Resolved in Pega Version 8.7

Sending an email with an embedded image to the email ID associated with the email listener successfully created the interaction case, but the embedded image was not displayed when the case was opened from the work-basket. A rule-not found exception was seen in the tracer for pyGetImageDisplay, the rule responsible for displaying the images in the ET pane. Investigation showed that when URLObfuscation was turned on, the decryption of the URL was not successful because "&" had been encoded to '& amp;'. This has been resolved by calling the activity pyGetImageForDisplay using URLMapping instead. An additional issue was seen with displaying images in the email interaction pane where the additional empty new lines moved the image outside the intended place. This was traced to a customization for the reply area which used the pyHighlightedMessage property and converted newlines to br tags even in HTML mode. To resolve this, pyHighlightedMessage has ben modified to convert newlines to br tags only if the mode is plain text.

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