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-119095 · Issue 174195

TagCloud rendering corrected

Resolved in Pega Version 7.1.7

When opening pxTagCloudViewGadget it generated the error: 'Unable to open an instance using the given inputs: pxObjClass = "Rule-Obj-Report-Definition", pyClassName = "", pyStreamName = ""' . The tag cloud gadget reported "Can not render @baseclass.pxTagCloudInit", and when run or included in a section, it did not render any tags. This was found to be a design time error in Obj-Open of the report definition, and has been fixed.

SR-119538 · Issue 177397

Detection added for custom work history tables

Resolved in Pega Version 7.1.7

In order to fully embrace mobile capabilities, columns were added to the work history tables to allow actions to be tracked as a geographical map where each history event is a numbered locale indicator on a map instead of a row of entries. From lat/long it is also possible to call a Google service and get the street address as well. However, this functionality caused some issues post-migration with if there were customized pc_history_work tables mapped to custom classes. To remedy this, a check has been added to only query for pxlatitude/pxlongitude if columns are exposed and shown, and that will detect if the columns aren't present.

SR-119869 · Issue 176176

Access Role Editor link errors fixed

Resolved in Pega Version 7.1.7

When using IE11 or Google Chrome, clicking on the hyperlink to a privilege associated with a class in Access Role Editor created issues that prevented changes from being made or saved. In some cases, after clicking 'Remove Checked' in the popup dialog, the developer portal loaded in the popup. This was caused by the forms-based role selection not being converted for cross-browser support, and has been fixed.

SR-117114 · Issue 171740

Added localization formatting for date values (YYYY-MM-DD)

Resolved in Pega Version 7.1.7

In Sweden, dates are given with a hyphen "-" and not slash "/" as the date separator as per ISO-8601. The SV localization has been changed to follow this style.

SR-118567 · Issue 167257

Enhanced task queue handling for custom applications

Resolved in Pega Version 7.1.7

In some situations, a custom agent would periodically fall over when processing a large backlog of queued items. This was caused by an exception thrown when placing a task in the queue when it is already present. The system has been updated to better handle this situation and allow agents to continue to execute with the present schedule when a duplicate task is found.

INC-174435 · Issue 659479

Survey Complex Question Definition properly displayed

Resolved in Pega Version 8.4.6

Selecting any Complex Question to look at the definition displayed a blank screen. This was traced to an issue with the ruleformtabs properties for the layout group used by complex questions, and has been resolved by changing the Layout Group display type from "Default" to "Tab".

INC-175533 · Issue 678911

Improved Page compare for page groups

Resolved in Pega Version 8.4.6

Field level auditing on embedded properties sporadically did not report the "old" value when a property was modified even though the page was listed as "Modified". This has been resolved by adding logic to the pxComparePages algorithm to treat Lists and Groups differently. Now Page and Value Groups will use pxSubscript as the primary way to detect add and deletes.

INC-180603 · Issue 661739

Added protections for GetSiblings

Resolved in Pega Version 8.4.6

Cross-site scripting protections have been updated for the GetSibling activity.

INC-182248 · Issue 665782

Added logic to handle manual validate rule creation

Resolved in Pega Version 8.4.6

Manually creating a Validate rule with conditions and then opening the configure view with conditions caused the validation rule to be removed from the flow action rule along with the validation conditions in the validation rule referred in flowAction rule. This has been resolved by updating the logic in the Condition Builder to handle this use case.

INC-191567 · Issue 676158

New application wizard security updated

Resolved in Pega Version 8.4.6

Security around displaying and running the new application wizard has been enhanced.

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