SR-128720 · Issue 193408
Fixed CSS styling for buttons in repeating layouts with refresh
Resolved in Pega Version 7.1.8
Buttons in repeating layout are meant to have incremental IDs to make each distinct for actions applied per row, but if an onClick > refresh this section was applied the DOM that was given after the refresh was no longer distinct and the triggering of CSS styling was affected. This was a problem in repeating layouts where the field control's ID was not incremental but was only pointing to the property name. This has been resolved with unique generation of input IDs and labels for attributes.
SR-128823 · Issue 193672
Added localization for CategoryActions navigation rule
Resolved in Pega Version 7.1.8
The CategoryActions navigation rule has been made available for localization.
SR-128861 · Issue 195852
Corrected temp directory for upgrade file extraction
Resolved in Pega Version 7.1.8
On upgrade, the extractedfiles directory was being written to the java.io.tmpdir location instead of to the Web-tier temporary path, i.e.. the temp location of the application server. This was incorrect, and the web temp directory is now set as the default temp directory in PRPC.
SR-128883 · Issue 195834
Fixed button contrast when using accessibility
Resolved in Pega Version 7.1.8
The "Select Values" button in the dialog to edit report filter had a low contrast ratio when accessibility was enabled. This was caused by the unintentional application of the repeat layout CSS to the button, and has been fixed.
SR-128895 · Issue 193902
LDAP authentication password issue resolved
Resolved in Pega Version 7.1.8
After reopening and saving an Authentication Service rule, the Test Connectivity failed due to a credentials problem. This was due to the password field being modified (increased) on a refresh/reopen of the record. This issue was caused by a double-encryption flaw on refresh, and has been corrected.
SR-128932 · Issue 194789
Added support for -x and -y parameters to ApplicationBundle import
Resolved in Pega Version 7.1.8
Previously, the use of the -x and -y parameters in the command line utility prpcUtils only worked with PegaArchives and not ApplicationBundle archives. In order to facilitate automation, the app bundle command line import command now honors the -x (override) and -y (skip) import parameters, and these options will be passed along to any nested par files.
SR-128945 · Issue 197784
Ensured compliance for localization checkbox on RadioButtons control label
Resolved in Pega Version 7.1.8
In RadioButtons control, it was seen that a label was localized without regard to the status of the localization checkbox checked at the section level. This has been fixed.
SR-128970 · Issue 194366
Added logic for base class missing a hyphen
Resolved in Pega Version 7.1.8
When using connector and Metadata Wizard, if a base class was provided that doesn't end with '-', then the generated class name were appended into the base class name. To correct this, logic has been added to append a hyphen to baseclass if one is not present.
SR-128986 · Issue 194639
Accessibility Report function removed
Resolved in Pega Version 7.1.8
The accessibility report required Quirks mode in order to render properly and be functional. This meant a modern browser such as Microsoft Internet Explorer 10/11 had to run in compatibility mode. This was not desirable behavior, as it meant the report was not compatible with non-Microsoft Internet Explorer browsers such as Google Chrome/Firefox and the Quirks mode requirement directly conflicted with the new requirement to use Standards mode in Designer studio and native Pega 7 developed apps. Therefore, the Accessibility Report has been deprecated and removed and developers are encouraged to use third party tools such as FireEyes to assess their application from an accessibility compliance perspective.
SR-128987 · Issue 195605
Dynamic Layouts incorrectly shown as not accessible
Resolved in Pega Version 7.1.8
Dynamic Layouts were incorrectly shown as not accessible in the Accessibility Report. This has been corrected. However, please note that the report's requirement to run in Quirks mode to render properly and be functional made it incompatible with modern browsers, and the Accessibility Report has been deprecated and removed. Developers are encouraged to use third party tools such as FireEyes to assess their application from an accessibility compliance perspective.