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-A95151 · Issue 268672

Logic added to convert UTC Date for REST clipboard mapping

Resolved in Pega Version 7.3

An error was generated while mapping UTC format Date fields to the clipboard in REST. This was traced to the DateTime properties in the JSON response not being converted to Pega-supported datetime format, and the necessary parsing logic has been added.

SR-A95291 · Issue 272970

Role Ruleform documentation updated to reflect new privilege behavior

Resolved in Pega Version 7.3

The documentation for the role ruleform has been updated to reflect that decision tables are not given the OpenDeveloperForm privilege necessary to edit the ruleform when "add to favorites" is used instead of "delegate". If an attempt is made to open a "Favorite" decision table delegated rule from the portal's My Rules screen, a blank-looking screen will be displayed instead of the rule form.

SR-A95291 · Issue 273018

Role Ruleform documentation updated to reflect new privilege behavior

Resolved in Pega Version 7.3

The documentation for the role ruleform has been updated to reflect that decision tables are not given the OpenDeveloperForm privilege necessary to edit the ruleform when "add to favorites" is used instead of "delegate". If an attempt is made to open a "Favorite" decision table delegated rule from the portal's My Rules screen, a blank-looking screen will be displayed instead of the rule form.

SR-A96514 · Issue 275326

Updated encryption logic for URL obfuscation

Resolved in Pega Version 7.3

If URL obfuscation was enabled and the incoming URL had non-ASCII characters (or UNICODE) characters in it, the encryption process was failing due to the incorrect length of byte array formation in padding logic. This logic error has been corrected.

SR-A97323 · Issue 266550

XSS filtering added to pzDisplayModalDialog

Resolved in Pega Version 7.3

XSS filtering has been added to the pzDisplayModalDialog to improve security.

SR-A98230 · Issue 271051

Revision management GET logic revised

Resolved in Pega Version 7.3

When the revision manager creates a new revision, the second step is to add rules (strategies/data transforms etc.) into that revision so that a strategy designer can work on that. However, it was found that if one of the HTTP requests was of GET method, selecting the rules and hitting 'submit' constructed an oversized URL which listed all the rules listed on the Revision page and the browser would hang due to the GET exceeding the character limit. To avoid this, the logic used to create the post body has been modified to creating avoid long parameter values.

SR-A99678 · Issue 272068

Chart clipboard page unloaded properly in tab refresh

Resolved in Pega Version 7.3

When a portal tab containing a chart was refreshed due to use of the "refresh when active" tabbed layout checkmark, the old chart clipboard pages remained. This was due to a missed use case, and has been fixed.

SR-B10018 · Issue 280365

Null pointer resolved for change events

Resolved in Pega Version 7.3

On a section where a grid had at least one column cell with the visibility condition configured to be run on client, each data change event on other controls inside the same section raised a JavaScript error which disabled all of the following actions configured to be executed on the change event. These script errors were due to the improper usage of the findCell API call, resulting in the second parameter always being sent as null. To correct this, the getElementRowPageRef of pega_ui_doc_eventsConditionChaining.js has been updated to pass the grid parent table properly for findCell to avoid a null pointer.

SR-B10051 · Issue 279714

Agent management detail corrected to show all nodes

Resolved in Pega Version 7.3

Drilling down to the agent detail from the Agent management page was showing only the current node when agents from the other nodes should have been displayed as well. This was caused by an error in the DataAgentIndex function, and has been corrected.

SR-B10051 · Issue 279523

Agent Management updated for long NodeNames

Resolved in Pega Version 7.3

Drill down to the agent detail from the Agent management page was only showing the current node. This was traced to a failed join when a very long "pyNodeName" DB line was encountered in pr_index_data_agents, and has been fixed.

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