SR-B44591 · Issue 301046
Color issue fixed for last value ranges
Resolved in Pega Version 7.3
An "Invalid XML" error was generated when trying to apply different colors for different ranges of values in the advance UI control "Charts" > "Gauge Half Arch". This has been fixed.
SR-B44787 · Issue 300852
work object lock released if nextAssignment is false
Resolved in Pega Version 7.3
The lock was not getting released on Work object creation even though back-to-back assignment processing was disabled for the flow. To correct this, the work object will be unlocked if the pynextAssignment parameter is false.
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-B45435 · Issue 301778
GenerateGridHTML updated for JAWS version compatibility
Resolved in Pega Version 7.3
An update to the JAWS program caused it to no longer recognize some Pega grids as tables due to the use of role=presentation, and the table name was not associated with the layout header title leading to the tables not being labeled accordingly. To correct this, the GenerateGridHTML now has an added summary attribute in the ".gridTable".
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-B45613 · Issue 302956
Fixed query for RD using dependent classes
Resolved in Pega Version 7.3
A runtime exception was generated when running a summary report due to an incorrect query being built for RD when dependent classes was checked. This was caused by pyGetDistinctRecords being set to true even for summary reports, and has been corrected by ensuring pyGetDistinctRecords is set to false for summary reports.
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.