SR-D3947 · Issue 461241
Cross-site scripting security added to GET Request Work-DeleteAttachment activity
Resolved in Pega Version 8.1.6
Security has been improved against a potential Cross-site scripting vulnerablity on GET Request Work-DeleteAttachment Activity.
SR-D9922 · Issue 481403
Case Notes view has proper line wrapping in Google Chrome
Resolved in Pega Version 8.1.6
When case notes were opened in the Google Chrome browser, the view did not wrap. This was traced to a style attribute for white space which caused the line breaks to be collapsed in Google Chrome, and has been resolved by modifying the DisplayNote HTML to handle the wrap use case.
SR-D13880 · Issue 483331
Support added for using WorkPage class for FieldValue evaluation
Resolved in Pega Version 8.1.6
The Instructions provided under the Assignment details section of an assignment shape were not evaluating the FieldValue for the work object's audit history entries unless the field value was defined only at @baseclass. This was due to WorkPage class not being considered while evaluating a FieldValue, and has been resolved by modifying the InstructionsLookup control to use work class instead of the hard coded @baseclass.
SR-D15242 · Issue 486126
Removed unneeded TrackSecurityChanges warning for Field Level Auditing
Resolved in Pega Version 8.1.6
When creating a TrackSecurityChanges data transform for Field level Auditing and providing the text in the source, the system produced warnings such as "The source 'Number of covered objects' is ambiguous and is being treated as text. If it is a page, add it to the Pages and Classes tab." These warnings were generated by pzIsAmbiguousSource when a rule modified to check for Top.pyModelName did not equal pyTrackSecurityChanges. Because the way the system processes the data transform for field level auditing is not the same as that used for the usual data transform, this warning is not necessary. To avoid confusion, the system has been updated with a check so warnings of the source being ambiguous will be ignored when the DT name is pyTrackSecurityChanges.
SR-D15425 · Issue 487887
Removed extra space from feld value in Audit History
Resolved in Pega Version 8.1.6
A space was seen for a Field value that was referenced in the instructions Audit History. This was traced to the control adding an extra space if any gaps were present in the code, and has been resolved.
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.