SR-A76586 · Issue 256002
Guardrail updated for Report Definitions using Data Page for filter
Resolved in Pega Version 7.2.2
It is possible to configure a report definition to use a Data Page in the Filter/Criteria field (such as pxObjClass Contains D_ABC.PropValue) and not be prompted to list the Data Page on the Pages & Classes Tab, but when it is not listed on this Tab the query uses a literal value as opposed to a dynamic reference. In order to ensure expected results, a check has been added to fully identify invalid page prefixes and an Informational guardrail for Functionality will appear.
SR-B15138 · Issue 285032
RUF and listener updates made to support new version of Bouncy Castle
Resolved in Pega Version 7.3
Compatibility issues were found with Bouncy Castle 1.49 and newer versions of WebLogic. In order to proceed with updating Bouncy Castle to the latest version, the SendEmailMessage RUF in Pega-IntegrationEngine and Pega-Procom has been modified to adhere to the newer Bouncy Castle APIs, and the email listener has been updated. The logic related to Rule utility function compilation has been changed to only to consider the top version of a library.
SR-B2595 · Issue 274239
Enabled process cleanup for change stage shape
Resolved in Pega Version 7.3
When using the "Approve\Reject" step in case designer on a flow containing logic to jump back to a previous stage on rejection, the system created the new assignment needed for jumping back to the previous stage but did not clean up the existing assignment. This caused two parallel flows at the same time and the old assignment was loaded on the screen. This has been fixed by enabling the CleanUpProcesses parameter in the Change stage shape function of pzPostApprovalActions.
SR-B9916 · Issue 283675
Hyperlink works on custom HC login page
Resolved in Pega Version 7.3
In a Hybrid Client App with a custom login page, a simple HTML link which calls the function to load the mashup code for the gadget worked in the browser but not in the HC. This was caused by window.open not working inside HC. To enable this, the _launchPopup api of compositegadgetmgr.js has been modified to use launchbox.Browser.start instead of window.open and the isCookieConsentRequired API has been updated to return false for popup case.
INC-145756 · Issue 619293
Logging for MultiNodeSynchronize lock attempts changed from error to warn
Resolved in Pega Version 8.4.4
The File Listener was logging numerous errors stating "Unable to establish MultiNodeSynchronize lock while trying to determine if listener is enabled for this node". Handling has been previously established for error cases when the Listener is unable to establish a MultiNodeSynchronize lock, but this condition continued to be logged as an error even though it was not related to any failures in functionality. To resolve the logging issue, the logger level has been changed from ERROR to WARN.
INC-149370 · Issue 619990
Logging for MultiNodeSynchronize lock attempts changed from error to warn
Resolved in Pega Version 8.4.4
The File Listener was logging numerous errors stating "Unable to establish MultiNodeSynchronize lock while trying to determine if listener is enabled for this node". Handling has been previously established for error cases when the Listener is unable to establish a MultiNodeSynchronize lock, but this condition continued to be logged as an error even though it was not related to any failures in functionality. To resolve the logging issue, the logger level has been changed from ERROR to WARN.
INC-145756 · Issue 619294
Logging for MultiNodeSynchronize lock attempts changed from error to warn
Resolved in Pega Version 8.5.3
The File Listener was logging numerous errors stating "Unable to establish MultiNodeSynchronize lock while trying to determine if listener is enabled for this node". Handling has been previously established for error cases when the Listener is unable to establish a MultiNodeSynchronize lock, but this condition continued to be logged as an error even though it was not related to any failures in functionality. To resolve the logging issue, the logger level has been changed from ERROR to WARN.
INC-149187 · Issue 622485
Logging for MultiNodeSynchronize lock attempts changed from error to warn
Resolved in Pega Version 8.5.3
The File Listener was logging numerous errors stating "Unable to establish MultiNodeSynchronize lock while trying to determine if listener is enabled for this node". Handling has been previously established for error cases when the Listener is unable to establish a MultiNodeSynchronize lock, but this condition continued to be logged as an error even though it was not related to any failures in functionality. To resolve the logging issue, the logger level has been changed from ERROR to WARN.
INC-149370 · Issue 619991
Logging for MultiNodeSynchronize lock attempts changed from error to warn
Resolved in Pega Version 8.5.3
The File Listener was logging numerous errors stating "Unable to establish MultiNodeSynchronize lock while trying to determine if listener is enabled for this node". Handling has been previously established for error cases when the Listener is unable to establish a MultiNodeSynchronize lock, but this condition continued to be logged as an error even though it was not related to any failures in functionality. To resolve the logging issue, the logger level has been changed from ERROR to WARN.
SR-C80753 · Issue 419246
Native calendar control works for Firefox on Android
Resolved in Pega Version 8.2
When using Firefox with 'Use native control on mobile' checked, attempting to enter a date into the DateTime field highlighted the mm field but the date selector did not open and keyboard entry was not recognized. This was traced to the native calendar for date time control not opening in Firefox on Android. To correct this, type checks for date, time and datetime-local have been added to the isTextBox function in pzpega_ui_events_infra js.