SR-122313 · Issue 181185
Database Class Report properly populating Ancestors column
Resolved in Pega Version 7.1.8
When running the Advanced->Reports->Database Class Report, the "Ancestors" column was not populated for tenant level classes. The problem was with the method used to create the report querying the ClassMap using normal, tenantized APIs instead of Shared, so no data was returned. This has been corrected and the class ancestor values are now properly populated in the generated csv file.
SR-122387 · Issue 183319
Expanded BIX error codes
Resolved in Pega Version 7.1.8
When BIX is executed through the command line, it may not return an error code even if BIX has stopped processing because of a failure (for instance when the -f flag has been used). That is, the $? system call may return 0 when an extract has failed. The system has been updated to offer more information thorough error code returns, but when trying to programmatically capture whether a particular run of BIX was successful or not, it would still be advisable to check $? in the script, as this may be returned due to other reasons (such as a java/network/database related problem). This may be augmented by performing a parse on the PEGABIX log file and specifically checking for the text: 'Instances not extracted due to errors: 0'. At the end of each BIX this line will appear with a summary of how many extracts failed. After the BIX portion of the script has completed, it's possible to check how many occurrences of this error appear in the file. If it is one, then this meant none of the extracts produced errors. And if there are none, then either some exports did contain errors, or it didn't reach the part of the code that produces this line (hence an earlier error). This can be incorporated into a script using something like: errorfree='grep "Instances not extracted due to errors: 0" PEGABIX.log | wc -l'
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-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-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-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-123095 · Issue 184829
Removed redundant save prompt for changed logging levels
Resolved in Pega Version 7.1.8
When a logging level in Designer Studio was changed, a prompt appeared to save the rules upon exiting the System operations page. This was redundant - the log level is saved immediately when it is changed in the modal dialogue "Logging Level Settings", and the extra prompt has been removed.