SR-128261 · Issue 192779
Corrected accessibility for buttons assigned a menu role
Resolved in Pega Version 7.1.8
With JAWS accessibility active, navigating to a menu button titled "Other Actions" causes JAWS to read "Menu. To move through items press up or down arrow...O." If the JAWS instructions are followed, it reads out the caption/title of the next field rather than actually reading out the options in the menu. This was caused by JAWS not reading the label of a button which has popover window on click action and has the 'menu' role added to it. To resolve this, if there is a role in the button generation RUF, its value has been set to "menu".
SR-128430 · Issue 194956
Pagination removed from OwnersList to facilitate large category lists
Resolved in Pega Version 7.1.8
After having created a large number of categories from the "Reporting" landing page, the list of available owners was not the expected one when creating a new shortcut. The owner drop down list is generated by the ListView called "Rule-Category.pzGetCategoryOwnersList." Unfortunately this ListView is a FINAL rule and paging was enabled with a default count of 50 entries. In order to allow for customizations like the above, OwnersList has been modified to disable paging.
SR-128696 · Issue 195043
Fixed alignment of columns and headers in RD scroll headers setting
Resolved in Pega Version 7.1.8
If "Do not scroll header" was checked in Report Definition, there was an alignment issue with the header and report Data. This has been fixed by updating "GenerateCellContent" to generate the CSS classes in the markup, and the CSS style was added to "pyReportEditorStyling" and is commented to make it available there if desired.
SR-129117 · Issue 196578
Resolved agent/tenant parent/child access for disabled agents
Resolved in Pega Version 7.1.8
When a shared system had an agent which was disabled, doing a "Save As" of the agent into the tenant env (to different application / RS) by logging into the tenant and enabling the agent failed with the error "No such Access group." This happened because the agent rule (created in the tenant) was running in the context of the shared system instead of the tenant system and could not find the access group. The issue was that the runActivityAsTenant function was not working as expected in the case of a child requestor trying to use the parent requestor's authorization, and this has been fixed.
SR-130147 · Issue 196723
pxCWOptionsMenu now localized
Resolved in Pega Version 7.1.8
Localization has been added for the section pxCWOptionsMenu.
SR-130208 · Issue 198155
Handling added for step page call to DeleteAssignment
Resolved in Pega Version 7.1.8
After upgrade, the pxDeleteAssignment with step page Assign-Workbasket was not working as expected. The error was traced to the 'DETERMINELOCKSTRING' activity being available in Work- class while the local customization was passing the Assign- page as the steps page. Handling has been added for cases when the activity gets called on a page other than primary work page.
SR-130224 · Issue 200002
Fixed class pickup when Ticket Urgency is used as reference
Resolved in Pega Version 7.1.8
It was not possible to convert a summary report to a list report if the report had Ticket.Urgency as a reference and Ticket was a single page pointing to data class type property in the work class. This was traced to the drill down picking up the Urgency property from the work class, and has been resolved.
SR-130249 · Issue 199071
Resolved validation error for modal window with right tabs
Resolved in Pega Version 7.1.8
Validation errors in a modal window could cause the user session to hang when the content of the modal window was configured to use a tab group with tabs positioned to the right. This was a div ordering error in the API, and a check was added for tab position right.
SR-130269 · Issue 197947
SmartInfo call updated for Listview in standards mode
Resolved in Pega Version 7.1.8
After upgrade, instances of SmartInfo configured on listview showed improper styles. This was due to the older version of the SmartInfo control being used when the document was in standards mode. The listview function has been updated to use the updated SmartInfo control for proper rendering.
SR-130345 · Issue 199748
Added qualification to validation queue page creation
Resolved in Pega Version 7.1.8
After migration, executing custom business logic validation generated the error "There was a problem getting a list". This was due to the JS code generating an unqualified QueuePage, and has been resolved.