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-132494 · Issue 201073

Exposed 'style' parameters for Workbasket and Operator dropdowns

Resolved in Pega Version 7.1.9

The ShowAllOperators and WorkBasketGadget out-of-the-box controls defaulted to in-line styles even when alternate styles were provided. To correct this, 'style' is now an exposed parameter for both Workbasket and Operator dropdowns.

SR-132896 · Issue 202844

Added handling for customized flows using "different work item" subprocess

Resolved in Pega Version 7.1.9

After upgrade, customized flows using the "different work item" choice on the subprocess for calling work flow from embedded data page work objects generated the error "'On Another Work Item' was specified yet the same object was supplied." This was traced to a missing pzInsKey for this use case, and the LaunchFlow RUF has been updated to handle this customization.

SR-133048 · Issue 202946

Enhancement added to filter list of bulk processing operators

Resolved in Pega Version 7.1.9

When opening Case Manger portal > Open bulk Actions, selecting the Filter condition as 'Assigned To Operator' showed all operators in the autocomplete list. An enhancement has been added to create the extension activity 'pyGetListOfOperators' for RD which can be updated as per the user requirement to filter the list of operators to be shown in the Bulk Processing Search.

SR-133048 · Issue 202342

Enhancement added to filter list of bulk processing operators

Resolved in Pega Version 7.1.9

When opening Case Manger portal > Open bulk Actions, selecting the Filter condition as 'Assigned To Operator' showed all operators in the autocomplete list. An enhancement has been added to create the extension activity 'pyGetListOfOperators' for RD which can be updated as per the user requirement to filter the list of operators to be shown in the Bulk Processing Search.

SR-133545 · Issue 206691

Closed potential vulnerability in (deprecated) pyNote attach function

Resolved in Pega Version 7.1.9

In order to close a potential vulnerability with pyNote executing a script that is embedded in the note, the handling has been replaced with 'richtext'. However, while the Notes feature is still included in the system for backwards compatibility, please note that Notes has been deprecated and replaced by Pulse.

SR-133183 · Issue 205535

Fixed flow line distortion in Process Modeler

Resolved in Pega Version 7.1.9

When clicking through to a subprocess from a parent flow (by clicking the + sign in the blue subprocess shape), flow lines in the subprocess were shown in a distorted fashion. When opening the same flow in a separate tab (by right clicking the blue subprocess shape and selecting Open Flow) the flow lines were correctly painted. This was an issue caused by the different renderings of the flow depending on whether there was a click through to it (with the + on the parent flow?s subprocess shape), or the subflow was opened in a separate tab (with open Flow). After the Process Modeler saved and checked-in the flow, the connector lines were re-drawn in ways that were non-intuitive and hard to interpret due to the edge routing in PM being calculated off incorrect input data that was taking into account shapes that were not represented on the screen. To fix this, the system now ensures the edges are routed without taking into account any shapes not represented on the canvas.

SR-133184 · Issue 203710

Fixed flow line distortion in Process Modeler

Resolved in Pega Version 7.1.9

When clicking through to a subprocess from a parent flow (by clicking the + sign in the blue subprocess shape), flow lines in the subprocess were shown in a distorted fashion. When opening the same flow in a separate tab (by right clicking the blue subprocess shape and selecting Open Flow) the flow lines were correctly painted. This was an issue caused by the different renderings of the flow depending on whether there was a click through to it (with the + on the parent flow?s subprocess shape), or the subflow was opened in a separate tab (with open Flow). After the Process Modeler saved and checked-in the flow, the connector lines were re-drawn in ways that were non-intuitive and hard to interpret due to the edge routing in PM being calculated off incorrect input data that was taking into account shapes that were not represented on the screen. To fix this, the system now ensures the edges are routed without taking into account any shapes not represented on the canvas.

SR-A1538 · Issue 209276

prvisiointerface.cab unblocked

Resolved in Pega Version 7.1.9

Effective with earlier ML versions of Pega7, several OCX functions were intentionally deprecated and replaced with Silverlight functions: Prbatchscanning prDeveloper prpackagecominterface prvisiointerface. However, it was found that there are two Word features around the embed merge function requiring prvisiointerface.cab that will produce some visual problems on the screen referring to the missing cab break if the files are ported from an earlier version of PRPC and prvisiointerface.cab is unavailable. Therefore, prvisiointerface.cab has been unblocked and restored for use.

SR-A2027 · Issue 205651

Reworked decision table conflict check logic for combined rows

Resolved in Pega Version 7.1.9

In a decision table, using expressions like property-property caused the decision table to report a non-existent logic conflict because there was another column with different data present. This has been fixed by adding a new property pyColumnDataType for Decision tables which will hold the data type of the expression/function/property mentioned in the column during FUAssembly, and then using it in the testConsistency code instead of the existing design.

SR-A204 · Issue 205451

Resolved sporadic NPE on TransferAssignment

Resolved in Pega Version 7.1.9

A null pointer exception was sporadically being being generated by the pxTransferAssignment activity. This was found to be an issue where a previous step to open the work object failed and the TransferWorkPage was therefore not created, followed by the absence of that page leading to the failure of the WHEN condition that was using the Rule-Utility-Function hasMessages. The handling has been updated to avoid this issue.

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