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-122529 · Issue 184997
Creation and testing corrected for ATOM server connection using Alfresco 4.2
Resolved in Pega Version 7.1.8
When creating a new ATOM Server instance with Alfresco 4.2, an error was logged and shown on the screen. This process worked with Alfresco 4.0. In the process of upgrading openCMIS jars, Atom and SOAP server connectivity tests were also changed to use HTTP, and Atom Server connectivity tests should now work for all versions of Alfresco.
SR-122613 · Issue 185054
"Apply Rule" form UI updated
Resolved in Pega Version 7.1.8
After migration, the XML Configuration Rule form "Apply Rule" had inconsistent fields labels after converting the rule form to autogenerated. The UI has been updated to present the labels in the same manner as prior versions to avoid confusion.
SR-122923 · Issue 186055
Created DSS for switching to old assembler
Resolved in Pega Version 7.1.8
The error "** FAIL : Unable to apply Rule-Parse-XML instance. WrongMode" while mapping xml data to page list in a parse rule was caused by a gap in the assembler, and has been resolved by creating a Dynamic System Setting with the following: Setting Purpose: switchtooldassembler Value: true Owning Ruleset: Pega-IntegrationEngine.
SR-123011 · Issue 182646
Added null check for datetime in SOAP
Resolved in Pega Version 7.1.8
Some SOAP services using a Response Parameter with Data Type of DateTime and for services of type RPC/ literal were generating an NPE when the service was executed outside Pega7 using Google Chrome. Running the service directly from the service rule within Pega7 did not encounter this error. Other SOAP requests returned a date of 1970-01-01. This was traced to a check to get the thread which did not handle situations where PRDateFormat.formatXSDDateTime() could be null, and the handling for that case has been added for this browser.
SR-123018 · Issue 183818
Addressed ruleset integrations problems using Google Chrome
Resolved in Pega Version 7.1.8
When using Google Chrome and running the Integration > Tools > Rule-From-File wizard, the ruleset version was not displayed and it was not possible to proceed past the screen that requires values for rule name, ruleset, ruleset version and class name. This was due to there not being an input field for RuleSet Version, and the validation of that step in the wizard fails. This issue occurred due to Google Chrome not supporting the use of document.all in the HTML code, leading to an undefined value for the JavaScript. This has been resolved by changes to the HTML to make it browser code independent.
SR-123044 · Issue 182684
Improved failure handling for cache loading on startup
Resolved in Pega Version 7.1.8
During server startup after upgrade, a data page with a failed definition cache prevented all remaining data page definitions from loading into the cache. This was found to be caused by a Node scoped data page which had only shared rule sets and did not have at least one production ruleset. In order to smooth startup, the declarative data page definition cache load will skip one particular improper record if found and continue processing.
SR-123056 · Issue 186144
FCM IAC caching improvements
Resolved in Pega Version 7.1.8
Analysis on the web server access logs found that content such as JS, image, and CSS files are cached correctly when accessing PRPC directly but not cached at all on the client when the same case is opened via the FCM IAC Gateway. This caused network congestion for the browser. To resolve this, the system now removes the appending forward slash from the thread name in the finalizeNavURL method when the request is issued to a gateway, allowing the download of the static content based on the application instead of the thread name.
SR-123056 · Issue 185070
FCM IAC caching improvements
Resolved in Pega Version 7.1.8
Analysis on the web server access logs found that content such as JS, image, and CSS files are cached correctly when accessing PRPC directly but not cached at all on the client when the same case is opened via the FCM IAC Gateway. This caused network congestion for the browser. To resolve this, the system now removes the appending forward slash from the thread name in the finalizeNavURL method when the request is issued to a gateway, allowing the download of the static content based on the application instead of the thread name.