SR-121686 · Issue 183607
Email Listener timeout tuned for EAR deployments
Resolved in Pega Version 7.1.8
When the email listener encountered an error in installations with EAR deployments, it stopped processing emails until the listener was restarted manually. This was caused by the Timer variable being static in EAR deployments with no logic available to reset it, so it continued to grow over time and could result in sleep times of days. Logic has now been added to reset the timer. The default sleep time has also been set to increase 30 seconds each time an error is encountered to a max of 90 seconds (sleep times are 5 , 30 , 60, 90 seconds) at which point it will reset.
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-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-122108 · Issue 182692
Fixed linking for work objects in CalendarViewGadget
Resolved in Pega Version 7.1.8
Using CalendarViewGadget to show calendar with work objects generated a Javascript popup with message "undefined" when clicking on the link of a work object. This "undefined" alert was added for situations where there is no handle passed to the openWorkByHandle desktop API, but there was an incorrect key in the hashtable of strings used to get the localized value. This has been fixed.
SR-122173 · Issue 184843
Expanded correspondence parameters for fax
Resolved in Pega Version 7.1.8
The parameters of Subject and AttachmentsToSend are passed to the CorrNew Activity to create correspondence for the actions Data-Corr-Email and Data-Corr-PhoneText. This has been expanded to also pass those parameters to Data-Corr-Fax.
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.
SR-122440 · Issue 183753
Corrected text wrap for cases
Resolved in Pega Version 7.1.8
Text wrapping was not happening automatically in long history descriptions in a case. This was due to a missing function and has been corrected.
SR-122493 · Issue 190767
Support added for conditional page list properties
Resolved in Pega Version 7.1.8
After upgrading, validate rules on aggregate properties had unexpected behaviors. This rule formation was inadvertently allowed in some earlier versions despite guardrails, so support for these conditional page list properties has been added in order to enhance backwards compatibility.
SR-122504 · Issue 189293
Made operator identification consistent across flows
Resolved in Pega Version 7.1.8
A naming difference was seen in work flows depending on whether Visio or modular functions were used: Visio picks the "Task_Assignment2" function to generate java for assignment, giving the operator ID, but modular flows use "Task_Assignment" and show the operator name. In order to show consistent behavior, the code has been modified such that it first gets the operator name from the assign page if it exists, and it does not exist it will fall back to sending the operator ID as parameter.