SR-B44839 · Issue 303893
Ensured LogServiceFile.pyWorkFileName is set
Resolved in Pega Version 7.3
In order to resolve an issue with file listeners not setting the property pyWorkFileName with the renamed file name on the LogServiceFile page, the pyWorkFileName property will be included in the Log-Service-File instance.
SR-B44878 · Issue 301248
displayHarness context maintained if established before passing pageName
Resolved in Pega Version 7.3
The runDataTransform() was running in the context of what was considered an incorrect page when called from the pre-js function of a Question shape when opening the case from the worklist. This was caused by using pega.offline.runDataTransform and passing the pageName parameter as null in an attempt to use the primary page context, but the system defaults to using the context of pyDisplayHarness instead of pyWorkPage when the pageName parameter is null. In order to support this configuration, the PreJS function of a question shape called from the displayHarness will maintain the context as displayHarness for pega.u.d.PrimaryPageName when passed.
SR-B45093 · Issue 301258
Fixed invalid reference for auto-populate
Resolved in Pega Version 7.3
An invalid reference exception was generated while trying to do Property-Ref on two properties inside Auto populate. This was caused by a coding error in a check used to avoid doing a getSourceProperty in case of a reference to a top level page, and has been fixed by modifying the setAsReference API in ClipboardProperty to gracefully handle Autopopulate scenarios.
SR-B4548 · Issue 275463
Class Data-Admin-Connect-MQServer now cached
Resolved in Pega Version 7.3
The rule instance cache has been updated to include the type Data-Admin-Connect-MQServer.
SR-B4548 · Issue 275330
Class Data-Admin-Connect-MQServer now cached
Resolved in Pega Version 7.3
The rule instance cache has been updated to include the type Data-Admin-Connect-MQServer.
SR-B45640 · Issue 302810
Resolved ConcurrentModification exception in getclass name
Resolved in Pega Version 7.3
Attempting to getclass name while iterating over values of mPageProperties in expandAllToProperties (in the putPropertyOntoClipboard call) was causing a ConcurrentModificationException that resulted in queues being blocked and loss of synch to the server. In order to more cleanly set the pxObjClass for the classless page-properties, pxObjClass has been added to the lookupDictionaryDefinition.
SR-B45640 · Issue 303222
Resolved ConcurrentModification exception in getclass name
Resolved in Pega Version 7.3
Attempting to getclass name while iterating over values of mPageProperties in expandAllToProperties (in the putPropertyOntoClipboard call) was causing a ConcurrentModificationException that resulted in queues being blocked and loss of synch to the server. In order to more cleanly set the pxObjClass for the classless page-properties, pxObjClass has been added to the lookupDictionaryDefinition.
SR-B45744 · Issue 302814
Debug logs Response XML
Resolved in Pega Version 7.3
The InvokeAxis2 activity was logging the Request XML to the debug log, but was not logging the Response XML. Code has been added to the InvokeAxis2 Activity to print the SOAP Response in the log file when debug is enabled.
SR-B46173 · Issue 302359
Improved HTTP thread handling
Resolved in Pega Version 7.3
During the execution of a performance test (SOAP service, RBS application), several exceptions were generated relating to the attempt to use a 'recycled thread'. In order to resolve this, the HTTP thread locking and ownership have been improved.
SR-B46173 · Issue 296360
Improved HTTP thread handling
Resolved in Pega Version 7.3
During the execution of a performance test (SOAP service, RBS application), several exceptions were generated relating to the attempt to use a 'recycled thread'. In order to resolve this, the HTTP thread locking and ownership have been improved.