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-118036 · Issue 171165

Corrected column width auto expand issues in decision table

Resolved in Pega Version 7.1.7

Decision tables which have many columns (8+) will expand the width very wide automatically by just clicking on the resize cursor (no dragging is necessary). However, trying to resize it back to a more reasonable width caused it to keep getting wider and wider due to an error with the dynamic display logic. This has been fixed.

SR-118077 · Issue 170104

Excessive logging addressed in Pega Mobile 4.3

Resolved in Pega Version 7.1.7

In PegaMobile, the oLog debugging statements were generating excessive log files. This has been addressed in Pega Mobile 4.3.

SR-118125 · Issue 171188

Circumstance property value carried into dropdown options

Resolved in Pega Version 7.1.7

If a property of mode single value and type text was created with a defined local list of property values for the property, the value field was not automatically included in the dropdown options when attempting to use this property for circumstance/specialized flows. This was caused by an incorrect refresh section strategy used to determine when to reload the section for the circumstance by property, and has been corrected.

SR-118259 · Issue 173287

LookupList opened to unauthenticated requests

Resolved in Pega Version 7.1.7

When a list lookup was called from an unauthenticated service, it failed due to the lack of required authentication. The activity RULE-CIRCUMSTANCE-DEFINITION LOOKUPLIST has been modified to allow its execution by an unauthenticated requestor.

SR-118415 · Issue 172879

Ensured Application Document wizard captures all subflows

Resolved in Pega Version 7.1.7

The Application Document wizard was documenting only some of the flows that were expected to be included. This was caused by an incorrect null check on the input parameters which treated the subflows as duplicate flows, and has been updated.

SR-119030 · Issue 172922

Clipboard privileges tightened to enhance security

Resolved in Pega Version 7.1.7

Using standard browser development tools, it was possible to insert a client-side modification into a Pega-served HTML page to allow a customer to access partial clipboard inspection functionality. To correct this, starting activity privileges have been tightened.

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.

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