SR-A43557 · Issue 258419
Earlier authentication inserted for open URL in repeat grid
Resolved in Pega Version 7.2.2
If a Repeat Grid was configured with a parameterized read-only Thread level Data Page as source and the DataPage had 'Reload once per interaction' checked in Load Management tab, clicking on a property that was configured to open a URL in a window caused an Unauthenticated or not available error on screen. This was traced to a corrupt list exception which happened when auto populate cleared the list elements on the first access as the data page refreshed and then getClassName() could not find the list element. To better handle this use, the engine activity API will first authenticate the request and then initiate the requestor interaction.
SR-A43557 · Issue 252477
Earlier authentication inserted for open URL in repeat grid
Resolved in Pega Version 7.2.2
If a Repeat Grid was configured with a parameterized read-only Thread level Data Page as source and the DataPage had 'Reload once per interaction' checked in Load Management tab, clicking on a property that was configured to open a URL in a window caused an Unauthenticated or not available error on screen. This was traced to a corrupt list exception which happened when auto populate cleared the list elements on the first access as the data page refreshed and then getClassName() could not find the list element. To better handle this use, the engine activity API will first authenticate the request and then initiate the requestor interaction.
SR-A21957 · Issue 256822
noteChange cache clearing improved
Resolved in Pega Version 7.2.2
If the access group coupled to a datapage was updated to point to a different version of the application, data pages tracing would not recognize the update even after being cleared and would instead show the load activity coupled to the prior application version. This was caused by the noteChange method not properly invalidating the cache when access group changes were made, and a check has been added to see if the rolelist or ruleset list has changed.
SR-A14735 · Issue 257217
Corrected jmxConnector thread termination
Resolved in Pega Version 7.2.2
In an installation with several PRPC JBOSS EAP-based nodes, the node running 'prsysmgmt' ('SMA') was periodically running out of Java Threads. This was due to JMX port connect threads being created for node authentication when SMA is deployed but then not correctly terminating on logoff or timeout (30 minutes). To correct this, logoff, timeout, deletion, or disconnect will now trigger the proper closing of any jmxConnnectors for that node.
SR-A87102 · Issue 257341
Corrected jmxConnector thread termination
Resolved in Pega Version 7.2.2
In an installation with several PRPC JBOSS EAP-based nodes, the node running 'prsysmgmt' ('SMA') was periodically running out of Java Threads. This was due to JMX port connect threads being created for node authentication when SMA is deployed but then not correctly terminating on logoff or timeout (30 minutes). To correct this, logoff, timeout, deletion, or disconnect will now trigger the proper closing of any jmxConnnectors for that node.
SR-A23247 · Issue 254176
Improved support for older EARs
Resolved in Pega Version 7.2.2
In order to improve backwards compatibility and resolve some agent restart issues, the engine has been updated to improve support for older EARs.
SR-A23247 · Issue 255179
Improved support for older EARs
Resolved in Pega Version 7.2.2
In order to improve backwards compatibility and resolve some agent restart issues, the engine has been updated to improve support for older EARs.
SR-A23558 · Issue 253477
IncrementalIndexer modified to better differentiate InsHandle
Resolved in Pega Version 7.2.2
Instances indexed with FTSIncrementalIndexer were returned in the result list with pxInsHandle="ClassName null" even when the pzInsKey of the instance was not null. This created a problem where perceived duplicates with the same pxInsHandle were stripped so the list did not return accurate results. To correct this, the code has been modified to set Additional Properties for External Class indices.
SR-A77555 · Issue 259289
Improved handling for multiple access 'when' in business event processing
Resolved in Pega Version 7.2.2
It was possible to encounter a missing page in the business event processing if event processing performed a call to tools.getThread().getAuthorization().haveAccess in multiple activities and there were several access 'when' actions defined for the class. The access 'when' requires that a work page be present to evaluate against, and depending on how the call was being performed or if passivation has occurred the process could throw an IndeterminateConditionalException and pass a null as parameter value for "aPage" parameter. To prevent this error, the activities pxCreateSummary and pxGetPrimaryClasses have been changed to pass the ClipboardPage of class for which haveAccess() is being called.
SR-A77555 · Issue 260161
Improved handling for multiple access 'when' in business event processing
Resolved in Pega Version 7.2.2
It was possible to encounter a missing page in the business event processing if event processing performed a call to tools.getThread().getAuthorization().haveAccess in multiple activities and there were several access 'when' actions defined for the class. The access 'when' requires that a work page be present to evaluate against, and depending on how the call was being performed or if passivation has occurred the process could throw an IndeterminateConditionalException and pass a null as parameter value for "aPage" parameter. To prevent this error, the activities pxCreateSummary and pxGetPrimaryClasses have been changed to pass the ClipboardPage of class for which haveAccess() is being called.