SR-128320 · Issue 193581
Updated chart export handling for Safari
Resolved in Pega Version 7.1.8
The charts in reports are getting disappeared on click of When using the Safari browser, clicking on Export to Excel/Export to PDF caused the charts in reports to disappear. This was traced to the form target being blanked in the browser handling, and a browser check has been added to invoke special handling for Safari..
SR-128634 · Issue 195936
Enhanced authentication setting carryover
Resolved in Pega Version 7.1.8
An issue was found with calling out-of-the-box authenticated activities from unauthenticated service activities. For example, when the declare page reload was triggered by a SOAP request (e.g. soap request creates new work which refers to the declare page), the report definition failed with an error saying that the requestor was not authorized to execute pxRetrieveReportData. This happened even though the SOAP Service Package and data page load activity had been set up to not require authentication. This authentication conflict was caused by the rule resolution disregarding the initial setting skipping authentication when it encountered the authentication requirement for the pxRetrieveReportData activity. This has been resolved by setting the authentication requirement to be applied to all rule execution in the same requestor.
SR-128689 · Issue 194302
Enabled line wrap for Display Shortcuts in RD
Resolved in Pega Version 7.1.8
Report definition was cutting off a long description rather than wrapping it to a new line. This was traced to pzDisplayShortcuts (a final rule) not being set to wrap text, and that setting has now been enabled.
SR-128701 · Issue 194839
getPropertyValue name collision resolved
Resolved in Pega Version 7.1.8
In order to accommodate custom RUFs called 'getPropertyValue', the Pega version of the rule is now called with full Library qualification.
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-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-129171 · Issue 195047
Corrected error in order of operations for Numeral builder
Resolved in Pega Version 7.1.8
The Add function in reporting was not returning the proper result when included in an equation with multiple order of operations. This was an error in the Numeral function builder, and has been corrected.
SR-129387 · Issue 200153
Logic updated to correctly tally requests that bypass authentication
Resolved in Pega Version 7.1.8
The logic used by the usage summary report to capture service invocation was not updated when the code was changed to bypass authentication for some service requests: if authentication was disabled, the request was treated as authenticated and was not correctly reported in the service invocation total of the SOAP usage summary report. To correct this and report accurate transactions, the system now resets the authentication flag for stateless unauthenticated requestors at the end of service invocation so that usage tracking is correctly recorded.
SR-129592 · Issue 196979
Scheduled report now checks default max records value
Resolved in Pega Version 7.1.8
When scheduling a report definition, the default value for max records to export was ignored when run by a scheduled task agent but used if the report was run manually. This value is normally set to 10,000 in the system settings and should be the default unless an override value has been entered for "Maximum Number Of Rows For Export" on the Data Access tab. To correct this issue, the pzRunScheduledShortcut activity has been updated to use the default if no value has been entered.