SR-D24214 · Issue 492568
Updated retry for context registraton
Resolved in Pega Version 8.3.1
The system was intermittently hanging after importing zipped files. Investigation showed that Batch threads were becoming stuck in AuthorizationContextManagerImpl.setSpecializations() due to a 'while' loop in setSpecializations that was seeking to register the new context. To resolve this, logic has been added which will try to register up to 10 times. If for any reason it can't register, the system will just return the unregister LAC. The check before deregister has also been enhanced and now will only deregister if the new context and the current context are different. It will not call register if the current context and the new context are the same.
SR-D24260 · Issue 492560
Updated retry for context registraton
Resolved in Pega Version 8.3.1
The system was intermittently hanging after importing zipped files. Investigation showed that Batch threads were becoming stuck in AuthorizationContextManagerImpl.setSpecializations() due to a 'while' loop in setSpecializations that was seeking to register the new context. To resolve this, logic has been added which will try to register up to 10 times. If for any reason it can't register, the system will just return the unregister LAC. The check before deregister has also been enhanced and now will only deregister if the new context and the current context are different. It will not call register if the current context and the new context are the same.
SR-D24261 · Issue 492556
Updated retry for context registraton
Resolved in Pega Version 8.3.1
The system was intermittently hanging after importing zipped files. Investigation showed that Batch threads were becoming stuck in AuthorizationContextManagerImpl.setSpecializations() due to a 'while' loop in setSpecializations that was seeking to register the new context. To resolve this, logic has been added which will try to register up to 10 times. If for any reason it can't register, the system will just return the unregister LAC. The check before deregister has also been enhanced and now will only deregister if the new context and the current context are different. It will not call register if the current context and the new context are the same.
SR-D26160 · Issue 504068
Corrected duplicate records being inserted in to the index table
Resolved in Pega Version 8.3.1
Rows in the index table were duplicated. This was traced to a logic error on the ClipboardPage relating to workObject2, and has been resolved.
SR-D26342 · Issue 495414
Tracer issues resolved for Google Chrome browser
Resolved in Pega Version 8.3.1
Tracer was running in the background even after the tracer window was closed. Attempting to run a Tracer in this condition resulted in an error indicating the Tracer was being run by another operator and should be restarted, and in the Dev environment, attempting to start a Tracer once it was closed resulted in the message "Cannot launch multiple Tracer sessions for a requestor." Investigation found that the Tracer session was not being closed when the tracer window was closed because the browser specific method intended to do so was not being called. This was found to be an issue caused by the Google Chrome browser changing the signature of the method, and has been resolved by updating the method name in the TraceMain HTML rule.
SR-D26342 · Issue 498714
Tracer issues resolved for Google Chrome browser
Resolved in Pega Version 8.3.1
Tracer was running in the background even after the tracer window was closed. Attempting to run a Tracer in this condition resulted in an error indicating the Tracer was being run by another operator and should be restarted, and in the Dev environment, attempting to start a Tracer once it was closed resulted in the message "Cannot launch multiple Tracer sessions for a requestor." Investigation found that the Tracer session was not being closed when the tracer window was closed because the browser specific method intended to do so was not being called. This was found to be an issue caused by the Google Chrome browser changing the signature of the method, and has been resolved by updating the method name in the TraceMain HTML rule.
SR-D28297 · Issue 498140
Tracer issues resolved for Google Chrome browser
Resolved in Pega Version 8.3.1
Tracer was running in the background even after the tracer window was closed. Attempting to run a Tracer in this condition resulted in an error indicating the Tracer was being run by another operator and should be restarted, and in the Dev environment, attempting to start a Tracer once it was closed resulted in the message "Cannot launch multiple Tracer sessions for a requestor." Investigation found that the Tracer session was not being closed when the tracer window was closed because the browser specific method intended to do so was not being called. This was found to be an issue caused by the Google Chrome browser changing the signature of the method, and has been resolved by updating the method name in the TraceMain HTML rule.
SR-D8754 · Issue 497376
Tracer issues resolved for Google Chrome browser
Resolved in Pega Version 8.3.1
Tracer was running in the background even after the tracer window was closed. Attempting to run a Tracer in this condition resulted in an error indicating the Tracer was being run by another operator and should be restarted, and in the Dev environment, attempting to start a Tracer once it was closed resulted in the message "Cannot launch multiple Tracer sessions for a requestor." Investigation found that the Tracer session was not being closed when the tracer window was closed because the browser specific method intended to do so was not being called. This was found to be an issue caused by the Google Chrome browser changing the signature of the method, and has been resolved by updating the method name in the TraceMain HTML rule.
SR-C60963 · Issue 424450
Clipboard flag conflict cleared to facilitate data migration via product rule
Resolved in Pega Version 8.3.1
After creating a Product rule in a 6.x version to export the Work Objects by adding all the necessary classes manually into the Product rule and then exporting the RAP, the in-flight work objects were imported successfully into the 7.x environment but the reference pages were not imported. This was traced to a broken reference link for the autopopulate process caused by ClipboardProperty flags being in conflict about whether or not the properties were defined as references, leading to the inference engine being disabled during the import. To resolve this, going forward the disabling of auto-populate properties will be done in conjunction with disabling the inference engine, as they should both be enabled or disabled together. By default the inference engine will be enabled as administrators are encouraged to import in the proper declarative context.
SR-D36293 · Issue 509303
Node level data page now specifies tenant name in MT environments
Resolved in Pega Version 8.3.1
In order to address a requestor contention between different tenants during the load of node level data page in multi-tenant environments, an enhancement has been added that will specify the tenant name in the data page name. This will improve performance by allowing different tenants to have different locks, ensuring the process of data page loading on one tenant will not make another tenant wait for the loading of the same data page. Additional debug and trace logging has also been added to provide more information related to declarative rule cache management.