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 update your bookmarks. This site will be discontinued in Dec 2024.

Pega Platform Resolved Issues for 8.1 and newer are now available on the Support Center.

SR-115313 · Issue 164520

BIX execution history did not update all Extracted rules

Resolved in Pega Version 7.1.7

If a BIX (Business Intelligence Exchange) extract was run with two extracts from the same shell script, the execution history was updated for only one of the extract rules. This was caused by the entry in the execution history (pr_log) is being overridden when the -i command line option is used. To ensure complete logging, the system has been updated to add a new entry to pr_log for every value when invoking the -i option.

SR-115378 · Issue 168818

Corrected horizontal scroll bars for listviews with custom searches

Resolved in Pega Version 7.1.7

Horizontal scroll bars were not appearing when using custom search section in a list view. This error was caused by missing logic for resizing the window width, and has been corrected.

SR-112785 · Issue 166486

Flow Action support tuned for MenuBar keyboard navigation

Resolved in Pega Version Pega Platform, Resolved in Pega Version 7.1.7

Using the' MenuBar' setting to display the flow actions for pyActionArea was not working as expected with keyboard navigation within the "other actions" menu: the Up/Down keys moved the cursor, but pressing the Enter key did not fire any actions because a mouseclick was expected. An enhancement has been added to the logic to support an enter key event for menu items. In addition, the "other actions" menu was not accessible with keyboard navigation from the Resolve Flow action. This has been corrected.

SR-115387 · Issue 166507

Flow Action support tuned for MenuBar keyboard navigation

Resolved in Pega Version 7.1.7

Using the' MenuBar' setting to display the flow actions for pyActionArea was not working as expected with keyboard navigation within the "other actions" menu: the Up/Down keys moved the cursor, but pressing the Enter key did not fire any actions because a mouse click was expected. An enhancement has been added to the logic to support an enter key event for menu items. In addition, the "other actions" menu was not accessible with keyboard navigation from the Resolve Flow action. This has been corrected.

SR-115392 · Issue 164192

Added customization for PDF page numbers

Resolved in Pega Version 7.1.7

Previously, it was not possible to designate the initial page number in the PDF generated by HTMLToPDF activity. Two parameters have been added to allow for greater customization: "header" activates page number support in the document header, and "startPage" is used to set the initial page number for the document. The "startPage" parameter can be used for both the header and footer.

SR-115492 · Issue 169327

Obj-save and commit working for fully-exposed classes

Resolved in Pega Version 7.1.7

If an exposed class was implemented by creating an underlying database table, trying to perform an Obj-Save (or commit) on an exposed class generated errors regarding some properties not having corresponding database columns. This happened when one of the Page names was also the beginning part of a name of one of the simple types, and was caused by a flaw in the logic used to determine if the property is an embedded reference. This has been corrected.

SR-115511 · Issue 168772

Application Express Wizard updated to correctly bind rulesets

Resolved in Pega Version 7.1.7

New Rule-Access-Role-Obj (RARO) rules created using Application Express wizard were being bound to specific ruleset versions vs. ruleset names. This caused failure to any modification to those RAROs, since modifying a RARO with a ruleset version would mean the save-as would fail if the validation found a RARO already present for that ruleset. In order to ensure proper binding and aid migration, a RARO with ties to a ruleset version will have that the version information removed automatically upon saving of the RARO.

SR-115521 · Issue 166317

Repeat Grid navigation enhanced for 'Expand Pane' edit mode

Resolved in Pega Version 7.1.7

If a Repeat Grid in a section was set to 'Expand Pane' as the Edit Mode , the 'previous' and 'next' buttons on the modal dialog were not working. The logic was missing for the Next and Previous APIs when using 'Expand Pane', and has been inserted to fix this issue. In addition, the Next and Previous APIs were enhanced to be appropriately disabled when the first and last rows are reached.

SR-115687 · Issue 165814

Vertical scrollbar fixed for expandable rows in Repeating Grids

Resolved in Pega Version 7.1.7

When using a Repeating Grid layout with pagination, expandable rows, a fixed size, and frozen header, expanding the row during run time caused the vertical scrollbar to disappear. The API has been updated to properly display the scrollbar for this setting combination.

SR-115711 · Issue 165363

Flow Action class correctly retrieved for subprocesses

Resolved in Pega Version 7.1.7

When running a Process Flow in a Data- class that is called from a Work- process flow via a SubProcess, the error "Failed to find a 'RULE-OBJ-WHEN' with the name 'CANMAINTAINCASEREPORT'" was being generated. This was caused by incorrect handling for the class: the flow action and WHEN rule are in a WORK class, but when the sub-flow is executed it looks in the DATA class of the embedded page instead of the WORK class relevant to the overall case. There was a workaround of saving the WHEN rules into the Data- classes, but the system now uses workPage instead of interestPage for localcase to ensure the correct class is retrieved.

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