SR-116936 · Issue 167898
Discarded threads set to properly clear on refresh or tab close
Resolved in Pega Version 7.1.7
When the browser was refreshed or an inactive recent tab was closed on the client side, the discarded threads were not getting properly cleared at the server end. To remedy this, the JavaScript has been updated to cleanly remove the threads.
SR-117173 · Issue 168365
Dynamic system settings for address map control updated
Resolved in Pega Version 7.1.7
Due to an error, the dynamic system settings for address map control had a value pre-set instead of a blank default. This has been corrected.
SR-117205 · Issue 171200
Corrected datetime calendar validation on forms with messages
Resolved in Pega Version 7.1.7
When messages were present on a form (validation, etc.) and the date selector was used, the screen blanked after selecting the date. This was caused by an error in the datetime calendar popover and has been resolved.
SR-117216 · Issue 168600
Validation corrected for Case Manager portal types
Resolved in Pega Version 7.1.7
After migration, changing the application header text for the Case Manager portal was throwing the error "pySkinType: ** You must specify a skin to use or select "Default to Application Skin" upon checkout. To correct this, the validation activity step has been updated with a 'when' expression to skip this validation for mobile portals
SR-117228 · Issue 168249
Resolved issues with Flow shapes distributed across Swim Lanes
Resolved in Pega Version 7.1.7
Pool size is maintained as both pixels and inches, but auto conversion was failing if the pool dimension was very large. This created an error where saving a flow rule could cause the pool to drastically shrink (for example, 20 inches becoming 20 pixels). In order to maintain the proper dimensions, a check has been added for pool and swimlane to ensure the proper inch/pixel conversions.
SR-117255 · Issue 174772
Required fields corrected for repeating grids in accessibility mode
Resolved in Pega Version 7.1.7
When using a repeat grid with required fields in accessibility mode, the field displayed multiple asterisk symbols instead of one. This problem was with workform_accessibility.CSS, and was resolved by changing the background image url to "transparent". The "REQUIRED" text was also not showing with IE8: this was noticed only in IE8 Standards mode, and an accessibility check was added to generate the span containing REQUIRED text in the html stream.
SR-117266 · Issue 173481
Prompt Select modified to properly handle XSS functions
Resolved in Pega Version 7.1.7
A selection made in Prompt Select was not retained after refresh when special characters were present in the selected value. This was caused by XSS filtering functions that compared an encrypted value with the prompt value and negated it when it wasn't equal. To fix this, PromptSelect has been modified to call the crossScriptingFilter API before appending strDefaultValue to the stream.
SR-117307 · Issue 171895
Improved submit flow for better accessibility with JAWS
Resolved in Pega Version 7.1.7
When the Create or Submit button on a flow action is clicked, dismissing the "You are about to change the current window" popup would sometimes cause JAWS to read extraneous messages such as "Create button unavailable" and "Main region end". This behavior was sporadic and depended on how quickly the popup was dismissed. In order to avoid this, the button function calls have been modified.
SR-117393 · Issue 171186
Accessibility expanded to cover out-of-the-box controls and dynamic layout
Resolved in Pega Version 7.1.7
Previously, out-of-the-box controls like DropDown, DateTime, and Icon were not marked as accessible. These controls have been updated to be included in the accessibility framework. In addition, the accessibility report was erroneously flagging dynamic layouts as not accessible: properties that only freeform layouts use, which would be legitimate reasons for flagging accessibility issues, are flagged for dynamic layouts if they happen to be present. This has been corrected.
SR-117836 · Issue 171042
Accessibility expanded to cover out-of-the-box controls and dynamic layout
Resolved in Pega Version 7.1.7
Previously, out-of-the-box controls like DropDown, DateTime, and Icon were not marked as accessible. These controls have been updated to be included in the accessibility framework. In addition, the accessibility report was erroneously flagging dynamic layouts as not accessible: properties that only freeform layouts use, which would be legitimate reasons for flagging accessibility issues, are flagged for dynamic layouts if they happen to be present. This has been corrected.