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-D28985 · Issue 498017

Improvements made to Excel data import handling for decision tables

Resolved in Pega Version 8.4

On importing an Excel file into a decision table, the values modified in Excel were getting updated even though the rule was checked in after the import. Investigation showed that the API which handled converting the imported Excel file for use on the clipboard was defaulting to save actions if the rule was not checked out or in private edit before the import. In order to prevent future issues, the following changes have been made in this area: The "Import" button will be enabled only after clicking on checkout button, and discarding the checkout will also discard any imported values. When checkout for the rule set is disabled, only the save option will be displayed on the decision table. When the import button is visible and enabled, imported values will not be preserved if Actions -> Refresh is used before saving. When rulesets are disabled, the decision table can only be private edited and at that time the save and import buttons will be visible. When private edit is visible, the import button will be in a disabled state.

SR-D28996 · Issue 520717

External Mappings set for History Rule tab of class display

Resolved in Pega Version 8.4

After creating a class rule with external mapping columns and saving the rule, attempting to restore the previous saved snapshot from the full history of the class rule resulted in the external mapping tab being displayed with empty rows. This was traced to "External mappings" not being set when displaying the History Rule, and has been resolved by adding a call to RULE-OBJ-CLASS!OPENDEFAULTS to set the mapping properties.

SR-D33214 · Issue 514024

Added safeURL encoding for Japanese characters in attached filenames

Resolved in Pega Version 8.4

It was not possible to preview a Japanese-titled PDF file attached on a work object. Investigation showed that in case of Japanese characters, file names were not being correctly encoded during the fetch request when JBoss was used. The retrieval worked correctly under Tomcat. In order to ensure consistent encoding, the safeURL API will be used for constructing the URL and for the activities DisplayAttachFile and pzDownloadFromRepository which add the ContentDisposition header.

SR-D33359 · Issue 505774

SelectAll properly applied to only the page selected

Resolved in Pega Version 8.4

In repeating grid, applying SelectAll on one page resulted in it being applied to the next page as well even though all records in the other page were not selected. Investigation showed that on change, the 'when' condition added to refresh the list was always false. To resolve this, the condition in section pzBulkProcessingCheckbox which refreshes the list once the checkbox is changed has been removed.

SR-D36636 · Issue 503462

Check added to resolve WrongModeException in Work-.Reassign

Resolved in Pega Version 8.4

An agent was failing due to a WrongModeException specific to the out-of-the-box activity "Work-.Reassign". Investigation showed that in the activity "Work-.Reassign" step no 15, there was an assumption that if the property pxFlow existed then newAssignPage.pxFlowName must also exist: if it didn't, invalid pages were created in pyWorkpage.pxflow. To resolve this, a check for the existence of newAssignPage.pxFlowName has been added.

SR-D38306 · Issue 507992

Deleted operator details stored in history table

Resolved in Pega Version 8.4

Pegaunit automation has been added for the pxAddHistoryToTempObject activity to allow the retrieval of detailed operator records in the pr_history_data table.

SR-D40053 · Issue 517528

GetNextWork will use pyID to create unique thread name

Resolved in Pega Version 8.4

After creating three cases, for example D-1, D-2 and D-3 in application 'App1', and then moving to application 'App2' using Switch Application, the GetNextWork function was displaying unexpected behavior. Clicking on 'get next work' three times picked up the three cases (D-1, D-2, D-3) as expected, but when a case was closed manually the last case's lock was removed from the table. For example, closing D-2 manually resulted in the lock instance for the last case ID (D-3) being removed instead of D-2. This was traced to the Get Next Work API creating the thread with the access group name, which meant that if multiple assignments were accessed through 'get next work' it was always cleaning the already opened assignment threads and only the last assignment thread was available. To resolve this, Instead of creating the thread name with accessgroupname, the system will use the work object's pyID to create the thread using a unique key.

SR-D43173 · Issue 508612

Filter logic updated for Warning Summary guardrail report

Resolved in Pega Version 8.4

After scheduling a Guardrail report for Warning Summary, the warning summary reports received in email were blank irrespective of the filter criteria. The logic filters have been modified to resolve this issue.

SR-D43397 · Issue 510331

Force order added to inner join when running a Rules Resolution filter

Resolved in Pega Version 8.4

After upgrade, D_getResolvedWorkStatuses was not loading properly due to a Report Definition that used a Filter by Rule Resolution option timing out on the SQL Server. When the Filter by Rule Resolution option is selected in RD, it will generate a rule resolution query with an inner join which can cause a time out on the SQL Server while it tries to find out the join order for tables with multiple joins. To resolve this, the SQL server will provide a Force order, merge inner join hint option by way of an added DSS reporting/useForceOrderHint. Additionally, reporting/useMergeHintForRRquery should be set on Pega-Reporting to set things up for using the Merge Inner join hint in the query.

SR-D43627 · Issue 509801

Keyboard tab support added added for Focus on Date control

Resolved in Pega Version 8.4

It was not possible to use the Tab key to move to a section with date control to launch it, and hitting enter when on a calendar did not open it. To resolve these, tabindex has been added for date/time focus and the calendar will open on enter.

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