SR-129239 · Issue 200337
Added handling for Flow not at Task error
Resolved in Pega Version 7.1.8
Flow not at task and flow removed errors were appearing sporadically. This happened when the trigger fired off the commit inside the post-processing called CorrUpdateNoWO and returned a stale copy of the Workobject, and was complicated by an assumption that was trying to iterate over "pzInternalCaseFlow". This has been addressed in the CORRUPDATENOWO activity.
SR-132880 · Issue 201431
Design time clarification for radio button configurations
Resolved in Pega Version 7.1.8
Previously, it was possible to configure an on-click event on a radio button in a repeating grid. This configurability was an error - although it was possible to set it up, the actions would not actually fire as intended due to the way the radio buttons work. In order to remove confusion, the actions tab for radio buttons has been removed from design time and checkboxes should be used if on-click actions are desired.
SR-130352 · Issue 199182
Corrected Microsoft Internet Explorer error for opening harness in a popup
Resolved in Pega Version 7.1.8
Configuring a button click to launch a harness in a pop-up with the Microsoft Internet Explorer 11 browser caused the error "Internet Explorer cannot display the webpage." The cause was an errant space included in the pega.u.d.url for this browser, and the GenerateHarnessHTML and GenerateLayout RUFs have been updated.
SR-131217 · Issue 199744
Stopped unexpected trigger caused by attaching note with gadget
Resolved in Pega Version 7.1.8
Declarative rules were being fired every time a note was attached to a work object using the "Notes" gadget (not advanced notes link). To fix this, the pxAttachNote activity has been updated to not trigger the declarative chaining in this scenario.
SR-131269 · Issue 200188
Fixed Harness buttons and screen resize issue
Resolved in Pega Version 7.1.8
Harness buttons were not fixed, and the screen was resizing to unviewable height on changing to screen layout. To resolve this, CSS changes have been applied to the pzbase-browser - CSS and pzbase-ie9 - CSS files to include selector for dynamicContainer div inside workarea div in not size to content mode. The rule applied is position: absolute.
SR-108805 · Issue 149539
Help updated to explain When Rule "ALL" Evaluation behavior
Resolved in Pega Version 7.1.7
A 'when' rule evaluating all pages in page list will only evaluate the properties on pages in the list that contain that property. This may cause a "true" result that does not match customer expectations. The hover help has been clarified to explicitly state that the evaluation results apply only for those pagelist entries where the property exists and not for all the page list entries.
SR-108838 · Issue 154989
Increased limit for Rule_Obj_CaseType
Resolved in Pega Version 7.1.7
Previously, Rule_Obj_CaseType was encountering a byte limit of 65535 in the JVM that impeded the ability to create a desired large number of coverable work types (54+). The system code has been modified to store the rule types differently to avoid generating extra lines of java code for each coverable case type.
SR-109455 · Issue 172370
CSS generation fixed for attaching files after validation failure
Resolved in Pega Version 7.1.7
After a validation had failed, uploading a file (through the filePath Control) and submitting the flow action resulted in the page loading with no CSS applied. This has been corrected by changing how the uploading wrapper is applied in cases of validation failure.
SR-112147 · Issue 162872
Missing buttons from modal dialogues after manual resize
Resolved in Pega Version 7.1.7
After a launching a modal dialog from a local action and manually resizing it to make it smaller, selecting another layout from the dropdown menu was causing the re-size icon and OK/Cancel buttons to disappear. To eliminate this problem, the system has been modified to properly reset the height and width of the modal container before displaying the second layout was displayed.
SR-112203 · Issue 156906
Corrected 'Top Performers' report
Resolved in Pega Version 7.1.7
The "Top Performers" report in the Case Manager portal was returning incorrect values in the 'Avg. Velocity' column due to an incorrect calculation based on the number of days in the selected period. This has been corrected.