SR-122732 · Issue 182663
Cleaned up error logging for Oracle split schema multi-tenant upgrade
Resolved in Pega Version 7.1.8
When upgrading a multi-tenant environment with an Oracle split schema database, the log file was filling with warning messages on all tenant IDs during Rules upgrade. While errors are expected if there are tenants in the database that are no longer valid, the failure to resolve the tenant ID was being reported twice. In order to smooth the upgrade process, the log messages in this environment have been changed from warnForced to info, and each error will only be logged once.
SR-122738 · Issue 184536
Resolved extraneous error from Case Viewer imports
Resolved in Pega Version 7.1.8
Attempting to import specifications from Excel in Case Viewer to update specifications that were checked in was showing the error 'Update Fail'. The updated specification was successfully imported, but the new change is checked out to the user. This was an error generated by the final step of the Import Specification wizard and has been resolved.
SR-122820 · Issue 177433
Passivation thread logic improved
Resolved in Pega Version 7.1.8
It was noticed that the passivation daemon was triggering thread dumps several times a day, affecting performance and disk space. This was caused by threads in the process of being passivated inaccurately being reported as long-running. This has been corrected by changing the long-running thread detection to recognize threads in the process of passivation, and to bypass them unless there is a long-running passivation problem.
SR-122820 · Issue 182133
Passivation thread logic improved
Resolved in Pega Version 7.1.8
It was noticed that the passivation daemon was triggering thread dumps several times a day, affecting performance and disk space. This was caused by threads in the process of being passivated inaccurately being reported as long-running. This has been corrected by changing the long-running thread detection to recognize threads in the process of passivation, and to bypass them unless there is a long-running passivation problem.
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-123023 · Issue 185999
Fixed emailing error for Report Browser subscriptions
Resolved in Pega Version 7.1.8
Once someone is subscribed to a scheduled report created in Report Browser, an email should be sent based on task scheduling. This was not happening as expected, though the status in the scheduled tasks was showing as sucessful. This was caused by an error in the ActionSendMailReporting activity which set the FromUserName to EmailAccount.pyEmailAddress instead of EmailAccount.pySMTPUserName, and has been corrected.
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.