SR-B31873 · Issue 298086
Review/Perform harness modifications for scheduled report errors
Resolved in Pega Version 7.3
Scheduled reports would periodically go to Completed state and stop running prematurely. Deleting and then reopening a scheduled report (from recents) caused corruption of scheduled reports that are re-scheduled. This was traced to the Review/Perform harness going in to a corrupt state, and has been corrected by re-building the Review harness as well as some minor changes to the Perform harness to ensure the correct buttons are displayed when deleting a scheduled report and reopening it from the recents list.
SR-B41820 · Issue 299434
Map from field updated to ensure Correspondence Name and Type are included
Resolved in Pega Version 7.3
An error was generated while configuring a Map From field as Correspondence. This was an issue with the Correspondence Name not being passed: when the Map From is selected as Correspondence, the backend expecting the Map from Key as a space separated combination of Correspondence Name and Correspondence Type. If only the Correspondence Name was selected, then the back end failed to find the Correspondence Type. This has been fixed by modifying the code to combine left and right from key part to ensure both parts are sent.
SR-C82408 · Issue 422326
Repaired instance insertion for REST connection invoked via Queue
Resolved in Pega Version 8.3
After upgrade, the REST connection invoked in an activity which in turn called out-of-the-box ProcessQueue was not getting the response into the SYSTEM-QUEUE-EXECUTIONREQUEST-CONNECT-CREATEBOOKING instance. The right response was observed coming from other source systems in the logs, and the work object status also changing as expected. This has been resolved by exposing a DSS to revert to the old behavior of Response being present in the queueItem when a connector is queued for execution.
SR-C93264 · Issue 437309
Inference engine enabled to resolve JourneyManager data flow exception
Resolved in Pega Version 8.3
Customer environments were intermittently seeing an exception with the error "Could not get ultimate primary destination for data flow .DF_JourneyManager" when trying to compile an activity that ran a dataflow that ultimately called the DF_JourneyManager data flow. This error was traced to the Inference engine being in a disabled state so the system was not able to get the dataflow output class via declare expressions. The Inference engine has now been enabled to resolve this issue.
SR-C79523 · Issue 421039
Updated the documentation for enabling debug logging during upgrades
Resolved in Pega Version 8.3
The documentation regarding enabling debug logging during upgrades has been updated to reflect the following information: To enable debug logging during installs, upgrades or prpcUtils invocations: The template logging configuration for installs, upgrades and prpcUtils is located within the scripts/config directory of the Pega Platform distribution. To change what gets logged, modify the prlog4j2.xml file (refer to https://logging.apache.org/log4j/2.x/manual/configuration.html#XML). Some of the utilities involved in the install and upgrade processes use java logging. To impact what is logged by these tools, modify the deploylogging.properties file in the same directory.
SR-C84384 · Issue 430962
Logoff control for Sales Automation case worker portal updated to clear states
Resolved in Pega Version 8.3
After logging in to the Sales Automation case worker portal and clicking a menu item other than dashboard, the link was properly highlighted in the navigation menu and the appropriate data was loaded in the harness. However, after logging out of the application and logging again as the same user, the portal opened to the dashboard page and the previously clicked link was highlighted instead of the dashboard link in the left navigation menu. While it was possible to reset the menu state by closing the browser and starting a new session, the issue has been resolved by updating the logoff control for this portal to use the general system control_logoff which clears states on exit.
SR-D5196 · Issue 445416
Hardcoded prweb reference removed from the REST connector to enhance flexibility
Resolved in Pega Version 8.3
The DASS for pegarobotics/RobotManagerHostDomain allows specifying the instance where Robot Manager is hosted. Previously, connect-REST pzInvokeRoboticAutomation contained a reference to the resource path {RobotManagerHostDomain}/prweb/PRRestService/robotics/v1/automations which forced the use of prweb. In order to add flexibility, the hardcoded prweb reference has been removed from the REST connector resource path, and the pegarobotics/RobotManagerHostDomain) DASS's default value has been updated to include 'prweb' in it. Local sites should update DASS accordingly to point to an updated URL with prweb if needed.
SR-D8390 · Issue 488002
Handling added for runtime exception on upgrade due to inaccessible external schema mapping
Resolved in Pega Version 8.3
If a system used external schema mapping, attempts to upgrade were failing with the error "Caused by: com.pega.pegarules.pub.database.ConfigurationException: Unable to obtain data source "java:comp/env/jdbc/PegaRULES", as it is undefined". This was traced to configuring external DADNs which were not accessible from the server where the upgrade was being run: an upgrade will fail if it cannot connect to an external datasource even if no changes need to be made to that datasource. However, because a PRRuntimeException was unexpectedly being thrown instead of a Database Exception, the exception was not properly caught and handled. This has been corrected.
SR-D32332 · Issue 502269
Removed unneeded table name calculation
Resolved in Pega Version 8.2.4
After giving short names (less than 30 characters) for "To Table", saving did not produce an error, but an error was thrown during Check In. Investigation showed that while checking in the extract rule, a block of code in the Rule-Utility-Function validateTreeProperties was being executed to recompute the pagelist's table name instead of using the name provided by the user. To resolve this, the RUF has been modified to not execute this block of code during check-in of the extract rule. The validation will be seen during save if the 'To field' has more than 30 characters.
SR-D38588 · Issue 506368
Removed unneeded table name calculation
Resolved in Pega Version 8.2.4
After giving short names (less than 30 characters) for "To Table", saving did not produce an error, but an error was thrown during Check In. Investigation showed that while checking in the extract rule, a block of code in the Rule-Utility-Function validateTreeProperties was being executed to recompute the pagelist's table name instead of using the name provided by the user. To resolve this, the Rule-Utility-Function has been modified to not execute this block of code during check-in of the extract rule. The validation will be seen during save if the 'To field' has more than 30 characters.