SR-122902 · Issue 182835
Shutdown issue with Tomcat resolved
Resolved in Pega Version 7.1.8
During shutdown, errors were reported on the App Server window. Shutdown did not complete and the App Server Window remained open. This was due to the "Shutdown" button/feature not properly terminating Tomcat. There was a workaround to manually close the Tomcat window, but the DNodeServiceListener has been modified to release all of the threads properly.
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-123031 · Issue 182673
Corrected inheritance logic for ComputeSegment
Resolved in Pega Version 7.1.8
ComputeSegmentLogic activity logic was not considering inheritance path. This was an issue with having the run-time rule resolution at design-time, and has been changed to pass propagate the apply-to class to sub-activity calls so that it can pick up the right rule.
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.
SR-123127 · Issue 185219
Improve error handling for File Listener
Resolved in Pega Version 7.1.8
The File Listener not processing all files successfully when there was more than one file to be processed. This was caused by missing logic for the clearing of 'hasOnce' at the file level for the record type. Since 'hasonce' was not cleared at file level, once a file with an incorrect configuration is processed, others files were also getting processed as errors. This has been resolved by adding code to reset the 'hasonce' on a per file basis so File Listener is able to process multiple files.
SR-123149 · Issue 184289
SOAPRequestEnvelope parameter added for custom Auth Activity
Resolved in Pega Version 7.1.8
In some cases, the SOAP request envelope content was not available to the authentication activity called by the auth service protocol. Since the operator ID is derived via a decision table from a different value in the SOAP request envelope, there was no way to use that value as an input to the new authentication activity. To correct this, SOAPRequestEnvelope is now made available on the parameter page of customAuth Activity with name "pxReqSOAPEnvelope".