SR-119376 · Issue 179579
Resolved checkout conflicts with discarded rule edits
Resolved in Pega Version 7.1.8
After a private edit of a work flow rule in the tenant layer, discarding that rule and then trying to do another Private Edit on the same rule generated the error "Status: **Check out failed. A checked out version with the same keys already exists. Please check-in that record first. This was traced to an issue with the clipboard retaining the discarded rule, and has been corrected.
SR-119715 · Issue 178060
Corrected Microsoft Internet Explorer horizontal scroll bar access within large list views
Resolved in Pega Version 7.1.8
If the data present in the list view is huge (2000+ characters), selecting the filter option caused the horizontal scrollbar to not be visible in Internet Explorer. As a result, the apply button was not accessible. This was caused by a lack of overflow settings to handle the excessive width for that browser, and has been fixed.
SR-119762 · Issue 176867
Case Manager search accessibility enhancement
Resolved in Pega Version 7.1.8
The 'Search' field in CaseManager has been enhanced to be more informative for end users to perform tasks and includes information that the follow-on menu holds options for 'search by' criteria. In addition, the 'Landmark Menu' has been provided with a search field for quick navigation and accessibility.
SR-119780 · Issue 175524
Added accessibility for CalendarViewGadget's month switch
Resolved in Pega Version 7.1.8
The CalendarViewGadget's month switch arrow buttons/icons have been updated to support navigation with the keyboard and respond to the TAB key, allowing full access to this function within the accessibility framework.
SR-120324 · Issue 179256
Corrected DateTime controls in GroupBy
Resolved in Pega Version 7.1.8
Specifying any of the DateTime-* controls (e.g., DateTime-Short) in the Format field of the Group By property in a summary view was not working with the out-of-the-box settings; the DateTime property would be displayed in DateTime (GMT) format. This was found to be a field name hard coded to a value with a data type of text, causing the selected control to be ineffective, and has been changed.
SR-120381 · Issue 179868
TopLevelClass updated to accept a hyphen in the name
Resolved in Pega Version 7.1.8
Previously, the new application wizard Top-Level class did not support the use of a dash between two ruleset classes. An enhancement has been added to allow this format.
SR-120518 · Issue 180099
Corrected error handing on"Post Action on Click Away"
Resolved in Pega Version 7.1.8
When an assignment in a screen flow was configured to use the "Post Action on Click Away" setting, it was not possible to go back if there were validation messages on the screen. Without the "Post Action on Click Away" setting, the click back worked and the validation message was cleared by the jumpToTask activity. This work flow issue has been fixed by clearing the page error messages before calling performflowaction.
SR-120566 · Issue 181231
Bulk Actions filtering error resolved
Resolved in Pega Version 7.1.8
In Bulk Actions, if a filter was renamed from "Assigned to Operator" to something else, ex "Application ID", the filter was not being applied. If the "Assigned to Operator" filter was deleted and a new one added, the filter was applied correctly. This was found to be an issue with the filters "Assigned to Operator" and "Assigned to Workbasket" setting the flag pyUsage = operator on the filter condition, causing a custom SQL to be generated. This has been corrected.
SR-120585 · Issue 182421
Work object history corrected for failed flow action submissions
Resolved in Pega Version 7.1.8
If a a flow action is submitted which encounters errors and generates Page-Messages, correcting the errors and re-submitting the flow action created duplicate entries in the work object history that included entries for the failed flowaction submission. This was caused by improper rollback of the addhistory when the commit of the WO is rolled back, and has been corrected.
SR-120586 · Issue 179198
Assignment dependencies with child cases now properly resolve
Resolved in Pega Version 7.1.8
Using a dependency on an assignment based on a child case can case an error. This was due to the obj class being wrongly populated, and has been resolved.