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-B78077 · Issue 364120

Documentation updated to assist in fixing UnresolvedAssemblyErrors when resolving RUF rules

Resolved in Pega Version 8.1

To address UnresolvedAssemblyErrors resolving RUF rules, the following help topics have been updated: Selecting-import-file-tsk Importing-cli-tsk Importing-cli-web-tsk To include the following cautions: * Review the archive contents to better understand which rule sets are capped and to determine the relatives risks and benefits of running uncapped rule sets. * Do not import an archive into an active runtime instance of Pega Platform because the archive can overwrite rules in use.

SR-C34516 · Issue 388567

Dynamic layout for pxDiscoverableItemsCount split to better handle individual 'when' conditions

Resolved in Pega Version 8.1

After upgrade, each report definition was showing a huge space under the filter section when using dynamic layout in the pxDiscoverableItemsCount section. If the layout format was changed from inline to any other layout format, the space did not appear. This was an issue with the custom styling for the Inline format that led to the Discovery item in reports taking up space even though it was hidden. This has been resolved by breaking the dynamic layout into two dynamic layouts so the 'when' condition could be on the individual dynamic layouts. If nothing is displayed within it, the dynamic layout markup won't be included.

SR-C45786 · Issue 384511

WO details saved to D_pyUserWorkList when finishing assignment offline

Resolved in Pega Version 8.1

When using the mobile app in offline mode, creating a new case and submitting it while offline saved the details in the WO. However, when trying to display the cases which were submitted offline there were details that needed to be shown but that were not updated in the D_pyUserWorkList until after synchronization. This caused WorkList to not show the data updated in newAssignPage and pyWorkPage when moving to the worklist after finishing the case. Previously, the updateWorkJoinProperties method of AssignList_Utils was setting pyCompletedOffline to false by default when it was called from saveWorkAndAssignment method. To ensure the data needed is available, the system will put work and assignment properties into D_pyUSerWorkList item for every finishAssignment by calling updateWorkItemInAssignmentList from saveWorkAndAssignment.

SR-C11241 · Issue 355607

Support added for secured Connectors to use "Keystore location"

Resolved in Pega Version 8.1

Support was recently added for "External keystores" on the Keystore ruleform, seen in the new "Keystore location" drop-down at the top of the form, but Connectors were not able to use the new Keystore types (File reference and data page) for HTTPS connections. This ability has now been added by modifying SSLUtils.java and KeyStoreUtilsImpl.java to support the file reference keystore.

SR-C11241 · Issue 360907

Support added for secured Connectors to use "Keystore location"

Resolved in Pega Version 8.1

Support was recently added for "External keystores" on the Keystore ruleform, seen in the new "Keystore location" drop-down at the top of the form, but Connectors were not able to use the new Keystore types (File reference and data page) for HTTPS connections. This ability has now been added by modifying SSLUtils.java and KeyStoreUtilsImpl.java to support the file reference keystore.

SR-C18936 · Issue 358807

API added to customize properties used in checksum calculation

Resolved in Pega Version 8.1

In order to provide a way to customize certain system properties from a checksum calculation, an API has been added to set a list of properties to be excluded.

INC-132169 · Issue 584759

NativeSQL will use inline rule resolution for core components

Resolved in Pega Version 8.5.1

After upgrade, nodes were going down with a heartbeat error. This was traced to issues with NativeSQL taking a very long time to generate queries due to the overhead in calling multiple complex functions to resolve rules. To correct this, updates have been made to resolve the standard set of functions used by core components inline in NativeSQL function resolution.

SR-C29742 · Issue 386203

Added check for JSON array when setting context for data transform

Resolved in Pega Version 8.1

When incoming JSON for a data transform had a null property, the data transform failed with a Null Pointer Error. This was due to the system assuming the root context to be null, which works for JSON but not for an Array of JSONs. To correct this, a check for topLevelArray has been added to ensure the system has the correct context of the current JSON Object.

SR-C32739 · Issue 372485

Credentials sanitized when logging exception for invalid primary page name

Resolved in Pega Version 8.1

Whenever an invalid primary page name was passed along with credentials in queryString, the credentials were logged without sanitizing or masking. Current standard behavior is that flows are run in an authenticated session that would not be passing this information, but this scenario was traced to legacy code for a very corner case that was not transitioned to the more secure method. The error information will now be properly sanitized on logging an exception.

SR-C32911 · Issue 373513

Submit button no longer shows <u> tag when accessibility enabled

Resolved in Pega Version 8.1

When a user was accessibility enabled and there was a custom filter section for a report, the Submit button in the pzRRDisplayCustomFilterSection section incorrectly showed "<u>S</u>ubmit" as its label. To correct this, the button has been updated to a new Auto-Generated button and script on click has been added.

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