SR-A99678 · Issue 272068
Chart clipboard page unloaded properly in tab refresh
Resolved in Pega Version 7.3
When a portal tab containing a chart was refreshed due to use of the "refresh when active" tabbed layout checkmark, the old chart clipboard pages remained. This was due to a missed use case, and has been fixed.
SR-B10018 · Issue 280365
Null pointer resolved for change events
Resolved in Pega Version 7.3
On a section where a grid had at least one column cell with the visibility condition configured to be run on client, each data change event on other controls inside the same section raised a JavaScript error which disabled all of the following actions configured to be executed on the change event. These script errors were due to the improper usage of the findCell API call, resulting in the second parameter always being sent as null. To correct this, the getElementRowPageRef of pega_ui_doc_eventsConditionChaining.js has been updated to pass the grid parent table properly for findCell to avoid a null pointer.
SR-B10051 · Issue 279714
Agent management detail corrected to show all nodes
Resolved in Pega Version 7.3
Drilling down to the agent detail from the Agent management page was showing only the current node when agents from the other nodes should have been displayed as well. This was caused by an error in the DataAgentIndex function, and has been corrected.
SR-B10051 · Issue 279523
Agent Management updated for long NodeNames
Resolved in Pega Version 7.3
Drill down to the agent detail from the Agent management page was only showing the current node. This was traced to a failed join when a very long "pyNodeName" DB line was encountered in pr_index_data_agents, and has been fixed.
SR-B10051 · Issue 279523
Agent Management updated for long NodeNames
Resolved in Pega Version 7.3
Drill down to the agent detail from the Agent management page was only showing the current node. This was traced to a failed join when a very long "pyNodeName" DB line was encountered in pr_index_data_agents, and has been fixed.
SR-B10076 · Issue 281632
Save and Cancel use case enabled
Resolved in Pega Version 7.3
When a button was configured with both the "Save" + "Cancel" out-of-the-box actions, the cancel action was performed but the data was not saved to the database. If the button was configured only as a Save action, the save worked as expected but the lock was not released. In order to support a CrossDomain windows use case of enabling an agent to save entered work but cancel out of the case so another another agent can pick up the case and continue with it, the Work-Autoclose function has been modified to write try catch blocks and call doClose when a button is configured with both the "Save" + "Cancel" out-of-the-box actions.
SR-B10103 · Issue 279865
Improvements in Export to Excel of very large files
Resolved in Pega Version 7.3
When exporting a very large (6000+ row) decision table into Excel, the process was very slow and the lack of a progress or busy indicator created the impression that the system was not responding. To resolve the processing issue, the code has been optimized to create lesser style objects. A busy indicator will also be displayed until the file starts download to indicate the operation is in progress.
SR-B10103 · Issue 279869
Improvements in Export to Excel of very large files
Resolved in Pega Version 7.3
When exporting a very large (6000+ row) decision table into Excel, the process was very slow and the lack of a progress or busy indicator created the impression that the system was not responding. To resolve the processing issue, the code has been optimized to create lesser style objects. A busy indicator will also be displayed until the file starts download to indicate the operation is in progress.
SR-B10103 · Issue 279866
Improvements in Export to Excel of very large files
Resolved in Pega Version 7.3
When exporting a very large (6000+ row) decision table into Excel, the process was very slow and the lack of a progress or busy indicator created the impression that the system was not responding. To resolve the processing issue, the code has been optimized to create lesser style objects. A busy indicator will also be displayed until the file starts download to indicate the operation is in progress.
SR-B10345 · Issue 281585
Command line jar import handling improved
Resolved in Pega Version 7.3
When installing Smart Dispute and related strategic applications, exceptions occurred when generating a DDL via prpcUtils (e.g. prpcUtils.bat generateDDL) if any of the files listed in schema.archive.input did not contain schema changes or did not have a delta. This has been resolved by updating the system to better handle files that do not require a DDL to be generated.