SR-A365 · Issue 205194
Resolved sporadic 'bad defined-on class' error
Resolved in Pega Version 7.1.9
The error "Attempting to access a rule with a bad defined-on class: " was seen sporadically and inconsistently on the user screen, PRPC logs, and tracer. This issue was triggered when an alert was generated and the system failed to find a rule message instance. To resolve this, opening the rule-message instance from db Loghelper.doAlert() method will pass the pyClasssName as well.
SR-A365 · Issue 205194
Resolved sporadic 'bad defined-on class' error
Resolved in Pega Version Pega Platform, Resolved in Pega Version 7.1.9
The error "Attempting to access a rule with a bad defined-on class: " was seen sporadically and inconsistently on the user screen, PRPC logs, and tracer. This issue was triggered when an alert was generated and the system failed to find a rule message instance. To resolve this, opening the rule-message instance from db Loghelper.doAlert() method will pass the pyClasssName as well.
SR-A365 · Issue 204670
Resolved sporadic 'bad defined-on class' error
Resolved in Pega Version 7.1.9
The error "Attempting to access a rule with a bad defined-on class: " was seen sporadically and inconsistently on the user screen, PRPC logs, and tracer. This issue was triggered when an alert was generated and the system failed to find a rule message instance. To resolve this, opening the rule-message instance from db Loghelper.doAlert() method will pass the pyClasssName as well.
SR-A3663 · Issue 210018
Corrected class inheritance issue for multi-tenant RAP migration
Resolved in Pega Version 7.1.9
When moving RAP files into QA and UAT classes for multiple tenants, class inheritance was being lost. The root cause was determined to be a problem with the internal class mapping and specifically the relationship distance map dealing with calls from one tenant (or shared) asking for classes in another tenant. This has been fixed.
SR-A3841 · Issue 208792
Cleaned up 'clear pages after non-use' function
Resolved in Pega Version 7.1.9
When the 'clear pages after non-use' option is selected, all the referencing threads should be closed and the page should be removed automatically. Instead, the document and threads were closed but the data page was not removed. This was traced to the Thread context not being present in the ThreadContainer during thread clean up, and has been corrected.
SR-A3841 · Issue 207560
Cleaned up 'clear pages after non-use' function
Resolved in Pega Version 7.1.9
When the 'clear pages after non-use' option is selected, all the referencing threads should be closed and the page should be removed automatically. Instead, the document and threads were closed but the data page was not removed. This was traced to the Thread context not being present in the ThreadContainer during thread clean up, and has been corrected.
SR-A3873 · Issue 208346
Next run in agent schedule updates after DB access issue
Resolved in Pega Version 7.1.9
It was discovered that if access to the database was interrupted, the Next run in agent schedule was not updating and not being run. This has been fixed by updating AgentQueue.handleProblem() to handle unexpected errors and ensure delayDueToProblem() is invoked always.
SR-A4279 · Issue 210830
Added handling for unknown UpdateDateType property
Resolved in Pega Version 7.1.9
Saving a Flow stream triggers the pzTrackChangesForFlow activity call, which then reads the pxUpdateDateTime property and converts it to Big Decimal for comparison. This conversion requires mode of the property (i.e. DateTime (?M?) in this case) to be known, which is specified in blob as encoded format. When using a PCI framework where the mode of the pxUpdateDateTime property is unknown(???), a NumberFormatException was generated. This has been fixed.
SR-A469 · Issue 210020
Reworked config file search to prevent WebSphere looping
Resolved in Pega Version 7.1.9
During server startup, the engine tries to populate the environment properties by reading the config files for the application server. A problem was found in some installations with WebSphere where trying to locate the XML file containing the information on the server port created an infinite loop that caused the engine startup to hang. To resolve this, the search function call now has been replaced by another method that tries to obtain the same information from config service without having to locate the XML file.
SR-A903 · Issue 204609
Removed primary page requirement for link-object activity
Resolved in Pega Version 7.1.9
When using the link-object activity method with the history checkmark and the specified step page without providing a primary page, the link-object activity method caused a null-pointer-exception when it attempted to fetch data from the pxRequestor page. This was caused by an unnecessary reference to the primary page, and the method to retrieve the value of pyUserIdentifier has been updated.