SR-D14591 · Issue 485931
Check added to resolve intermittent console errors
Resolved in Pega Version 8.1.6
An intermittent issue where an autocomplete control was hanging after repeated use has been addressed by adding an additional check (dispElem && dispElem.parentNode) to avoid console errors.
SR-D19083 · Issue 490403
Autocomplete list resets to top of scroll if selected data is deleted from the control
Resolved in Pega Version 8.1.6
If an autocomplete on Screen did not initially have any input, pressing the down arrow showed the popover data with the scrollbar on the top. Scrolling down and selecting an item from the autocomplete suggestions and then tabbing out closed the popover. If the data was then deleted from the control and the down arrow was pressed again, the popover suggestion showed the data in the last scrolled position instead of restarting from the top as expected. Investigation showed that when autocomplete used a list configuration, the popover div was not being updated if the data was deleted from the control. This has been corrected.
SR-D9482 · Issue 484739
Small delay added to autocomplete control
Resolved in Pega Version 8.1.6
When using an autocomplete control with minimum character search set to 4, every keystroke after 4 characters triggered a REST request to populate the control. This had a negative impact on performance. In order to smooth the request process, the timing logic has been updated to allow for a very small delay on the immediate event handler.
SR-D17825 · Issue 494703
PreSaveAs updated to set the correct ruleset value when saved into a different ruleset
Resolved in Pega Version 8.1.6
When using a BIX Extract rule already configured with properties and filter criteria, attempting to update the filter criteria system resulted in an "invalid property error" and inability to save the updated rule. This was traced to the extract rule being created from another extract rule with 'save as', resulting in the new extract existing in a different ruleset. Because the pxBixReportPage.pyRuleset had the value of the original ruleset instead of rule set in which it had been saved, the system was attempting to find the filter properties in the original ruleset. To resolve this, the Presaveas activity in rule-admin-extract has been modified to check and set the correct value when both the rulesets are not equal.
SR-D8467 · Issue 457337
Resolved false alarm exception for Cloud BIX extraction
Resolved in Pega Version 8.1.6
BIX Extraction on Cloud was intermittently throwing an exception even though the BIX Extraction was successful. This false alarm was triggered by inconsistencies in an API within the BIX extraction module used to determine if files existed on a Cloud S3 location post-extraction, and has been resolved by removing the file check.
SR-D10100 · Issue 465272
Bulk actions filter works properly when additional filters are added
Resolved in Pega Version 8.1.6
The Bulk Actions filter was not working if other filters were used in conjunction with it. Investigation showed that when 'assigned to operator' was given a value, the values were fetched properly. When an additional condition was added, the section 'pyBulkProcessingSearchSection' activity called 'pzDefaultOperators' which then set the 'pyUserIdentifier' value to null, and no results were returned. As the activity already had a step to check if the .pyUsage!="Operator" and only then property-set, pyUserIdentifier = "", the subsequent step to set the pyUserIdentifier = "" and override the previous step has been removed.
SR-D30993 · Issue 500221
Corrected retention of Operator routing assignment
Resolved in Pega Version 8.1.6
If an assignment routing option was directed to an operator and an operator was then selected, the system did not retain the operator ID upon submit and save. This has been resolved by removing an extra space in step 2 when condition of activity pyUpdateModifiers.
SR-D6555 · Issue 457241
Access When check added for pyStartCase privilege
Resolved in Pega Version 8.1.6
If a privilege was defined in the pyStartCase flow rule and the access role to object assigned a privilege based on 'Access When' (not production level), the user was not able to start a case. This was traced to the havePrivileges RUF passing an incorrect primary page to evaluate the privileges in combination with the 'access when'. To resolve this, the engine API will call tools.getAuthorizationHandle().havePrivilege for each privilege until it finds a match.
SR-D12511 · Issue 484664
Corrected error when resolving subcase from Review harness
Resolved in Pega Version 8.1.6
An error occurred when resolving a subcase if it was opened from the review harness. It was possible to resolve the subcase successfully if the local action was invoked from the Perform harness. Investigation showed that the update status was called twice, once from pyForcecaseclose and again from the update status of the activity. This has been resolved.
SR-D15154 · Issue 488069
CaseType picks up stage name correctly
Resolved in Pega Version 8.1.6
When adding a new stage in the Stages tab of a case type (pyDefault rule), the stages were shown as rule name instead label after saving and at runtime. Directly adding the Stages in the 'Workflow' tab of the case type showed the stage label as expected. This was traced to an issue with the current row of the table not being properly refreshed, leading to old data being submitted while saving. This has been resolved by adding an explicit "refresh current row" configuration on pyStageName under primary and alternate stage table layouts.