SR-121828 · Issue 179859
Localization added for the "Loading" text of the busy indicator
Resolved in Pega Version 7.1.8
Previously, the 'alt' values of the "Loading" text for the pega_ui_busyIndicator (pxThrobber) were hard-coded to English. This has been changed to allow localization.
SR-121858 · Issue 183012
Added integration for Microsoft Azure Root Certificates
Resolved in Pega Version 7.1.8
Attempting to implement Single Sign On using MS AZURE AD was failing. This was due to the Microsoft Azure Root Certificates not being correctly configured/imported into the target Application Server. Microsoft Technical Support was engaged and recommended manually exporting the required certificate from Azure and importing into the target environment as a workaround, and this integration has now been addressed with updates to the XML Security ResourceBundle.
SR-121969 · Issue 184370
Deleted attachments flow error fixed
Resolved in Pega Version 7.1.8
If an attachment was added and submitted and then deleted from the attachment tab, the application then generated an error. This was caused by the system passing an invalid FromFrame after closing the modal dialog, and the code has been updated to use the originalFromFrame value when launching the flow.
SR-121980 · Issue 181118
Microsoft Internet Explorer 11 support added for auto-complete with multiple line properties in Report Definition
Resolved in Pega Version 7.1.8
If a property in a column of ReportDefinition that contains a carriage return (in order to input and display the value on two lines in the results) was then used as a source to Autocomplete control, then autocomplete control was not displaying the results. This was caused by a broken display with the Microsoft Internet Explorer 11 browser in compatibility mode, and code has been added to escape the new line character before converting the string to a JSON object so it will display as expected.
SR-121993 · Issue 181639
Fixed handling issues with substitutions enabled Parse XML rules
Resolved in Pega Version 7.1.8
Parse XML rules generated from an XML schema (xsd) saved in draft and "Not available" were generating Java errors when attempting to check out the rules and make them available. This happened when there were substitution elements and an embedded reference to the same element, and was caused by improper handling of the substitution helper method. This has been corrected.
SR-122118 · Issue 180259
Improved condition handling for complex harnesses
Resolved in Pega Version 7.1.8
If a Review Harness had multiple embedded tab sections with includes, a read-only condition in the parent section was not being honored in a sub-section if the 'when' condition became false. This happened when a SectionIncludeInCell RUF passed an unquoted null value as a 3rd argument while invoking stream reference, and has been resolved.
SR-122118 · Issue 183909
Improved condition handling for complex harnesses
Resolved in Pega Version 7.1.8
If a Review Harness had multiple embedded tab sections with includes, a read-only condition in the parent section was not being honored in a sub-section if the 'when' condition became false. This happened when a SectionIncludeInCell RUF passed an unquoted null value as a 3rd argument while invoking stream reference, and has been resolved.
SR-122176 · Issue 184992
Older button visibility conditions retained after upgrade
Resolved in Pega Version 7.1.8
After migration, older button controls set to visibility "ALWAYS" and when condition "canPerform" became visibility "WHEN" and when condition "canPerform". To resolve this, the logic for the activity Embed-Harness-Section!UpgradeOnOpen has been updated to check for "VISIBILITY" first before "visible when" to retain the proper settings.
SR-122197 · Issue 182685
Resolved Connect SOAP header mapping issue
Resolved in Pega Version 7.1.8
In the Connect SOAP rule, a Request tab configured with a Request Header field using XML Stream option was missing the PEGA tag in the generated SOAP header. This was caused by an error in the Axis stack and has been corrected to ensure all elements defined in the MapFrom XML rule are correctly generated.
SR-122230 · Issue 180223
Datetime properties format improved for backwards compatibility
Resolved in Pega Version 7.1.8
After upgrading, the search API was returning datetime properties in an incorrect format, causing a page error that was sometimes visible to an end user. The error only occurred if additional processing was happening in that page that caused the validation dictionary to launch. The root cause of this problem was a backwards compatibility defect related to Elastic Search, and it has been corrected.