SR-A8496 · Issue 219309
Corrected page property setting for pxAddChildWork smart shapes
Resolved in Pega Version 7.2
The page property parameter was being ignored in favor of the WorkPage in the the pxAddChildWork activity. This should only have happened if the PageProperty Param was null or empty, but was occurring in scenarios where a child case was created using the Create Case smart shape. A check has been added to consider the top level page of the step page as the Primary Page parameter in order to prevent this issue.
SR-A10178 · Issue 219880
"ExportToExcel" activity updated to match Java API upgrade
Resolved in Pega Version 7.2
After upgrade, the "ExportToExcel" out-of-the-box activity was returning an error when clicking 'save as' on the rule in application ruleset. This was caused by the code in the activity not being upgraded after the Java API version was upgraded, and has been corrected by updating the "ExportToExcel" activity.
INC-170041 · Issue 655251
Check and error message added for filename containing "%00"
Resolved in Pega Version 8.7
At the time of file attachment or upload, if the file name contained % followed by two 0s (%00), the file upload mechanism distorted the UI and the Pega logo screen popped up. The file was saved properly in the ServiceExport directory, but while fetching the attachment info, the file was split in two because the engine considered %00 as a delimiter. This has been resolved by adding a file name check and a pyInvalidFileName field value to be used for an error message.
INC-161463 · Issue 638003
Case Dependency corrected for different access groups
Resolved in Pega Version 8.7
Creating a queue item as part of the case dependency was not working as expected when the access groups of the dependent cases were different. Investigation showed that in this scenario, the logic was looping differently and the DependencyList page in pxCheckFlowDependencies was getting removed. To resolve this, the DependencyList page has been moved so it is processed inside the DependencyList.pxResults loop.
SR-A6315 · Issue 215955
Parameters passed correctly by Data Transforms called on a Connector
Resolved in Pega Version 7.2
Data Transforms called on a Connector rule of a flow in Data- or Int- classes (other than work classes) set on the design tab were not passing parameters even when input parameters were defined in the data transform. This was caused by an error where the classname was not being taken from pyClassName and passed to the section pzRuleCallParams, and has been corrected.
SR-A8640 · Issue 219698
Display styling updated for Team Members Widget Counts
Resolved in Pega Version 7.2
In the out-of-the-box Team members widget, the counts displayed for each user sometimes appeared outside the container boundaries or displayed on top of other sections. This was due to the operator name length; even when truncated, the widget did not correctly account for the text. The styling handling has been updated to display the counts correctly.
INC-190819 · Issue 681999
Wrapper added to set correct bulk transfer context
Resolved in Pega Version 8.7
Bulk transfer was not working as expected when transferring an assignment from a flow defined in data class. Investigation showed the bulk transfer UI was getting picked from work- class while the post processing was running under data class context: this has been resolved by creating a wrapper activity in baseclass to call the post processing activity Work- .
SR-D33359 · Issue 505773
SelectAll properly applied to only the page selected
Resolved in Pega Version 8.2.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-A5588 · Issue 212799
Added check to halt case progression if open assignments present in parallel flow
Resolved in Pega Version 7.2
If "Launch On Re-entry" was unchecked and parallel flows were present in the current stage, it was possible to progress to the next stage even if open assignments were present in the current stage. In addition, all steps in the parallel flow were created if the open assignments in the activated flow were completed. To avoid this, the stage history will be checked for all the stages whether or not the 'Stage on Re-entry' check-box is in use. Previously, only the last stage was checked: with this update. if the requested stage has any unprocessed flow missed in previous visit then it will be considered.
INC-183947 · Issue 673733
Query split added to handle Oracle expressions limit
Resolved in Pega Version 8.7
The PXCHECKFLOWDEPENDENCIES activity was throwing the Oracle error message "ORA-01795: maximum number of expressions in a list is 1000" when a case had a very large number of sub-cases, causing a failure in trying to submit additional child cases which sent them into the broken process. This has been resolved by updating the pxCheckFlowDependencies rule to break down the query parameter into batches of 999 so they can be handled by Oracle.