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.
SR-129011 · Issue 193996
Added space to pzGridModalTemplate
Resolved in Pega Version 7.1.8
The pzGridModalTemplate used as a pop-up to input data to a grid was missing a space between the "Previous"/"Add" buttons and "Ok"/"Cancel" buttons. This has been inserted.
SR-129015 · Issue 196408
Cleaned up section reload on change
Resolved in Pega Version 7.1.8
In a section with a drop down on which an onChange event was added and a refresh section is set as the action, the refresh section calls a data transform and no activity call. However upon execution, there was a pop up with the error message 'Illegal Argument Exception'. When the activity is cleared the section rule should remove the parameter, but the preactivity params were not cleared in the clipboard even after clearing the activity. This has been corrected.
SR-129075 · Issue 197719
Sorting corrected for mixed column types in virtual RD grids
Resolved in Pega Version 7.1.8
If a grid contained both dynamic and static columns, the sort icon did not change after clicking on a column to change the sort in a virtual report definition grid. This was due to a missing CSS style for the static columns in this scenario, and a check has been added to look for multiple column types.
SR-129080 · Issue 199016
Ensured correct clearing for error in DateTime control field
Resolved in Pega Version 7.1.8
If there was an error on the Datetime control field present in a repeat grid, correcting the value in that Date field and then adding another row that follows the one containing the error generated a popup error message and it was not possible to set the date. The issue was in the drop down display mode, which re-rendered an invalid field as empty but the corresponding input had the same invalid value. That caused the new submit with empty values (which is valid) to produce the same error due to the input present in the client. To resolve this, the invalid hidden input for will now also be reset.
SR-129101 · Issue 195816
Smoothed error handling for operator password change process
Resolved in Pega Version 7.1.8
After the password change error screen appeared, the error popup showed again after dismissal and the the operator-id edit screen had to be closed and reopened, requiring entering the operator information again in order to proceed. This was due to incomplete clearing of the errors, and has been corrected.