SR-B44278 · Issue 302830
MT guide updated for rules blocking/restriction
Resolved in Pega Version 7.3
The MultiTenant guide has been updated to clarify what causes rules to be blocked or restricted and the possible consequences of unrestricting rules.
SR-B44280 · Issue 302124
Fixed REST call to JVM property http.non.ProxyHosts
Resolved in Pega Version 7.3
If JVM system properties are used to configure an HTTP proxy, it is applied unconditionally by all REST connectors. The JVM property http.non.ProxyHosts is normally used to exclude connections selected hosts from using the proxy, but due to an error this property was not being consulted by the REST connector. This has been corrected.
SR-B44280 · Issue 301832
Fixed REST call to JVM property http.non.ProxyHosts
Resolved in Pega Version 7.3
If JVM system properties are used to configure an HTTP proxy, it is applied unconditionally by all REST connectors. The JVM property http.non.ProxyHosts is normally used to exclude connections selected hosts from using the proxy, but due to an error this property was not being consulted by the REST connector. This has been corrected.
SR-B44327 · Issue 302991
Migrated work objects properly resolve references
Resolved in Pega Version 7.3
After upgrade, Work objects created in an earlier version were not opening due to a difference in the Reference Property Link metadata used by forward links. This has been handled by ensuring the Reference Property Links are resurrected if not explicitly present.
SR-B44426 · Issue 300990
New JS APIs added to get section streams
Resolved in Pega Version 7.3
In order to support getting section stream(s) using JS API's, the following new JS APIs have been added to the pzpega_api_ui_actions actions JS file: pega.api.ui.actions.getSection(sectionName, contextPage, callback) pega.api.ui.actions.getSections(sectionName, contextList, callback)
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.