SR-113830 · Issue 164768
Smoothed handling of rulesets with duplicate names
Resolved in Pega Version 7.1.7
When doing a "Save As" of a rule, the ruleform converts the entry in the description field to uppercase. If there is already a previous version of the rule with a name in lowercase, it was possible for the rule to exist with both a lowercase and uppercase name. While Rule Resolution worked, this case difference could cause a scenario where not all versions of the rule were visible when doing a rule search, viewing rule history, or looking up previous versions of the rule. The rule retrieval logic previously used RuleName; to ensure proper rules are being picked up, this has been changed to use the rule ID.
SR-114109 · Issue 164313
Corrected Connect-Java ability to run in parallel
Resolved in Pega Version 7.1.7
Using connect-java in RunInParallel mode was failing with the error "couldn't resolve the required java object". This was found to be an error in copying objects from the primary page in RunInParallel mode that did not properly retain the references for the Java wrapper objects. There was a workaround to use the "If possible, use a valid object handle" option, but this error has been fixed.
SR-114154 · Issue 162063
Enhanced keyboarding accessibility
Resolved in Pega Version 7.1.7
Several enhancements were made to improve accessibility. While developing an application for visually impaired users who use the keyboard (rather than mouse) to navigate the screen, it was found that certain input elements did not correctly receive focus under IE8 when tabbing. One issue was that when an element is focused and the parent element is scrollable, the focused element was not being displayed if it was beyond the scroll area. Additionally, some elements were not receiving visual focus with WAI ruleset enabled upon focus. To aid in keyboard navigation, if the WAI ruleset is used, an element receiving focus will also be made visible by scrolling to its position. When the accessibility ruleset is enabled, all elements will now properly receive visual focus. In order to enhance the accessibility of dropdowns in Audit windows, Filter panel width has been increased in Accessibility Mode to display all the dropdowns in the window at once without requiring use of the scroll bar. Furthermore, Accessibility mode for Audit windows has been updated to include the use of the spacebar to toggle settings in the checkboxes.
SR-114154 · Issue 169785
Enhanced keyboarding accessibility
Resolved in Pega Version 7.1.7
Several enhancements were made to improve accessibility. While developing an application for visually impaired users who use the keyboard (rather than mouse) to navigate the screen, it was found that certain input elements did not correctly receive focus under IE8 when tabbing. One issue was that when an element is focused and the parent element is scrollable, the focused element was not being displayed if it was beyond the scroll area. Additionally, some elements were not receiving visual focus with WAI ruleset enabled upon focus. To aid in keyboard navigation, if the WAI ruleset is used, an element receiving focus will also be made visible by scrolling to its position. When the accessibility ruleset is enabled, all elements will now properly receive visual focus. In order to enhance the accessibility of dropdowns in Audit windows, Filter panel width has been increased in Accessibility Mode to display all the dropdowns in the window at once without requiring use of the scroll bar. Furthermore, Accessibility mode for Audit windows has been updated to include the use of the spacebar to toggle settings in the checkboxes.
SR-114154 · Issue 170194
Enhanced keyboarding accessibility
Resolved in Pega Version 7.1.7
Several enhancements were made to improve accessibility. While developing an application for visually impaired users who use the keyboard (rather than mouse) to navigate the screen, it was found that certain input elements did not correctly receive focus under IE8 when tabbing. One issue was that when an element is focused and the parent element is scrollable, the focused element was not being displayed if it was beyond the scroll area. Additionally, some elements were not receiving visual focus with WAI ruleset enabled upon focus. To aid in keyboard navigation, if the WAI ruleset is used, an element receiving focus will also be made visible by scrolling to its position. When the accessibility ruleset is enabled, all elements will now properly receive visual focus. In order to enhance the accessibility of dropdowns in Audit windows, Filter panel width has been increased in Accessibility Mode to display all the dropdowns in the window at once without requiring use of the scroll bar. Furthermore, Accessibility mode for Audit windows has been updated to include the use of the spacebar to toggle settings in the checkboxes.
SR-114184 · Issue 162116
Withdrawn non-empty classes caused JVM restart issues
Resolved in Pega Version 7.1.7
After withdrawing non-empty classes, attempting to restart the JVM system resulted in a null pointer exception due to the system trying to map the withdrawn classes. The system has now been updated to prevent the deletion of a class if it is not empty.
SR-114543 · Issue 163265
Withdrawn non-empty classes caused JVM restart issues
Resolved in Pega Version 7.1.7
After withdrawing non-empty classes, attempting to restart the JVM system resulted in a null pointer exception due to the system trying to map the withdrawn classes. The system has now been updated to prevent the deletion of a class if it is not empty.
SR-114312 · Issue 174692
Check added to handle invalid input in the year field for datetime
Resolved in Pega Version 7.1.7
Previously, when a date time property was provided with an invalid year containing more than four characters (such as 20142014), the date defaulted to 12/20/8963 when the form was submitted. A check has been added to catch dates of more than four digits when attempting validation.
SR-114353 · Issue 166997
System scanner performance enhanced
Resolved in Pega Version 7.1.7
When working with a large number of hotfixes, the system scanner can become very slow. Performance enhancements have been incorporated to increase speed by changing how ID and key comparisons are performed.
SR-114438 · Issue 168461
Inbound mail processing for work creation refactored for subject line checking
Resolved in Pega Version 7.1.7
Some issues were found with the handling of inbound emails for work object creation. The activity CreateAndManageWorkFromEmail was incorrectly checking for an email subject line pre-condition and creating a new work object if the condition was not met. The CreateAndManageWorkFromEmail function has been refactored to correct this.