SR-D29114 · Issue 499932
Added handling for bulleted text insert triggering audit
Resolved in Pega Version 8.1.6
When a bulleted text (copied from an email or rich text ) was used in the text area property, the audit considered it as a change even when there was no change. This was tracked to the field value 'pyHistoryMemo • ChangeTrack_Add' in @baseclass which is being used to get the localized value for audit memo: the field value accepts only 2 parameters, but the inserted text area input contained the '\t' that is used for parameter translation. To resolve this, the system will call the addMemoForSecurityChangeTracking utility method to replace all \t's present in both the Current Value and Previous value with 'empty' such that no '\t' characters are available in either of the string parameters.
SR-C97046 · Issue 485717
Added restriction to limit environment sending multiple OTP emails
Resolved in Pega Version 8.1.6
Multiple One Time Password (OTP) Emails were being sent for a single requestor on a change password screen when the password was expired. This was caused by the environmental settings refreshing the changepassword harness, and has been resolved by adding a restriction against sending multiple OTPs for a requestor to whom an OTP has been successfully sent once.
SR-C96456 · Issue 436308
Autocomplete grid scroll bar fixed for large DataPage results
Resolved in Pega Version 8.1.6
When autocomplete (default setting) was present inside a grid and the result popup had < 20 results, the scrollbar was not coming up in Google Chrome. This has been resolved by modifying the fixGridWidthIfRequired API to set set vertical scroll to auto.
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.