SR-119160 · Issue 176869
Accessibility enhancement added to case manager portal
Resolved in Pega Version 7.1.8
Some key areas incuding the search field were missing ARIA roles when the landmark menu on the case manager portal was brought up while using NVDA / JAWS screen reader. To remedy this, the landmark menu has been provided with a search field to quickly navigate to search field in Case Manager portal in accessibility mode. A future enhancement is planned for adding ARIA roles to auto generated sections.
SR-119213 · Issue 178963
Updated flow default for SAE-I course
Resolved in Pega Version 7.1.8
The PRPC: System Architect Essentials I training course shows how to create draft process outlines. An SAE exercise where Stage "Decision" has steps "Background Check" and "Assess Candidate" which run in parallel was not working as expected. The first step is an assignment, and the second is a multi-step process with a decision shape which points to a decision tree. If that decision shape referenced an undefined decision record, the process would not execute and there was no way to proceed with the case. This was traced to the DRAFTMODECHOICE flow rule in which "Process commander internal flow" was checked by default. This was not the preferred work flow behavior, and the default is now to leave "Process Commander Internal Flow" unchecked so the flow is not marked as internal. In addition, the instructions for DraftModeChoice assignment were modified to reflect this change.
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-119707 · Issue 178023
All results shown by default for database searches
Resolved in Pega Version 7.1.8
Previously, when performing a database search by using the "old:" keyword prefix and some of the results were removed by the pyTransform activity due to the number of matches exceeding the Initial Results Limit, the "Show All Results" option would not appear in the footer information. This behavior has been changed and such commands will automatically search and display all results.
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-119810 · Issue 178693
Filtering options removed for RepeatGrid columns to ensure consistent results
Resolved in Pega Version 7.1.8
When creating a RepeatGrid with Filtering option enabled, applying the filter on the JUSTIFMicrosoft Internet ExplorerD? field's True/False property was returning variable results in the Application Guardrails "All Warnings" report depending on whether the column filter was set to JUSTIFMicrosoft Internet ExplorerD NO or JUSTIFICATION was left blank (the top choice on the filter dropdown). This was found to be an issue where toggling the filter criteria wasn't filtering out the warnings from rules residing in Pega- rulesets. Until this can be properly addressed within the application's scope, the filtering option on columns has been removed.
SR-120083 · Issue 179048
Expression Builder updated to suggest proper value tokens
Resolved in Pega Version 7.1.8
When defining an input column in a Decision Table rule to evaluate the result of an expression, the Expression Builder suggested that the token '' could be used to plug in the value from the current row of the column into an expression. This was an incorrect recommendation, and would not return the correct values. The correct token to use is . This error was due to the JavaGenerateAPIVersion property missing in the rule data after Rule-form was upgraded to Harness. This property is used to determine the substitute keyword ( or ) based on the version, and is present to support or upgrade decision table for work flow rules prior to 05-02-01. It does not impact the functionality of the feature, but has been changed to give the correct suggestion for .
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-120455 · Issue 184325
Toolbar enhanced for large decision tables
Resolved in Pega Version 7.1.8
An enhancement has been added to decision table columns to change the toolbar to floating if there are many columns to display.