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-133681 · Issue 206951

Added handling for two declare index rules on two pagelist properties in the same work class

Resolved in Pega Version 7.1.9

Given two declare index rules on two pagelist properties in the same work class, the second declare index was working while the first declare index was behaving inconsistently. It was found that even though there were two records for the property, at run time only the second record was getting inserted because only one insert command fired for Accounts Pagelist and the Declare index did not update even after using pzReindex is true. To ensure proper function firing, the system has been updated so when pzReindex is true, the existing pzIndexes page group value will not be considered.

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-132637 · Issue 203591

Added path checking to FirstLogCreationTime.log

Resolved in Pega Version 7.1.9

FirstLogCreationTime.log was being written to a temp folder using hard-coded logic to use a relative path within the install directory. This caused errors if the installer was trying to write the logs in an absolute path. FirstLogCreationTime.log should be written to the same directory as the rest of the logs, and this issue has been fixed by adding a condition in LogDeleteUtil.getLogCreationTimeFile() method to check for absolute paths.

SR-132987 · Issue 205014

Enhanced Expression Builder icon availability

Resolved in Pega Version 7.1.9

Previously, the Expression Builder gear icon was only available for text type properties: this has been updated to make the EB icon visible for all property types.

SR-133079 · Issue 202877

Repaired column header labels in Decision Table

Resolved in Pega Version 7.1.9

Clicking on a column header and opening the property changer, then closing it using the X in the top-right corner of the popup caused the label to change to the label of the rightmost column. This was traced to incorrect behavior by the modal dialog where closing the window did not return the correct value from the previous launch. This has been corrected.

SR-133382 · Issue 205956

Updated paragraph styles in Security policy

Resolved in Pega Version 7.1.9

Using ie, the History tab and Policy Definition tab had incorrect content while viewing Security policy rules. This was found to be an issue with the styles present in the paragraph rule 'pzScriptSrcDescription', and the styles have now been updated.

SR-133382 · Issue 205957

Updated paragraph styles in Security policy

Resolved in Pega Version 7.1.9

Using ie, the History tab and Policy Definition tab had incorrect content while viewing Security policy rules. This was found to be an issue with the styles present in the paragraph rule 'pzScriptSrcDescription', and the styles have now been updated.

SR-133538 · Issue 205317

Smart Prompt fixed for DT column headers

Resolved in Pega Version 7.1.9

Smart Prompt was not working when configuring Decision Table column headers. The Decision table rule (including the smart prompt control and pages&classes tab) was updated as part of rule form conversion from form-based to harness-based. However, the smart prompt is loaded in a separate frame and did not have the necessary access to the decision table rule which contained page&classes values. While there was a workaround of manually typing in and saving the 'page.propertyname', this has been corrected.

SR-133538 · Issue 204972

Smart Prompt fixed for DT column headers

Resolved in Pega Version 7.1.9

Smart Prompt was not working when configuring Decision Table column headers. The Decision table rule (including the smart prompt control and pages&classes tab) was updated as part of rule form conversion from form-based to harness-based. However, the smart prompt is loaded in a separate frame and did not have the necessary access to the decision table rule which contained page&classes values. While there was a workaround of manually typing in and saving the 'page.propertyname', this has been corrected.

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