SR-C1769 · Issue 351502
Day function corrected for pre-1970 dates
Resolved in Pega Version 7.4
The function day (datetime) was behaving differently for dates before and after 1970/01/01. To resolve this, the Date diff calculation logic has been modified.
SR-C1859 · Issue 344369
Clipboard clears on form submit, plus performance improvements
Resolved in Pega Version 7.4
Progressing through an application questionnaire was causing clipboard size to increase without being cleaned. This was due to a page clearing request not being triggered, and the harnessonbeforeunload method has updated to trigger pyDeleteDocumentPg on submission of the form in topnavigation portal. In addition, performance improvements have been made to this process.
SR-C1960 · Issue 348388
Support added for RTE images with Mashup
Resolved in Pega Version 7.4
Using Mashup code to include a Rich Text Editor configured to accept images inside a section was not working as expected. Uploading an image displayed a cross image in the upload window, and subsequently the file was displayed as a broken image in RTE. Investigation showed that in a NonMT environment, data content requests from mashup will send requests with access group hash, which was not previously supported. An enhancement has now been added to accept data content requests with or without access group hash at the engine side in both MT and NonMT environments.
SR-C216 · Issue 351334
Restart flag added to connector errors
Resolved in Pega Version 7.4
Connector error messages have been updated with a Boolean flag "whether to restart: true/false".
SR-C2190 · Issue 345689
Enhancement to allow disabling application requestors
Resolved in Pega Version 7.4
A new DSS has been added to disable passivation of application requestors. When set to true, application requestors will not be passivated and the system will not check pr_page_store for a passivated thread for app requestors. Note that when this is enabled, passivation for ALL application requestors will be suppressed.
SR-C2466 · Issue 349952
Resultset fetchSize dynamically set for Elastic search re-indexing
Resolved in Pega Version 7.4
Previously, the Elastic search resultset fetchSize defaulted to 50. To allow for performance tuning, an enhancement has been added to allow use of a new dynamic system setting "indexing/distributed/fetchsize". This dynamic system setting for resultset fetchSize will be used only during the elastic search re-indexing; in all other places the default fetch size for result set will remain at 50.
SR-C2539 · Issue 345950
Efficiency tuning for UpdateClipboardModels
Resolved in Pega Version 7.4
When selecting interaction tab (call tab), the openWorkByHandle action was triggering twice, one for interaction work object, and other for service work object, making two calls to the pzUpdateClipboardModels activity. To improve efficiency, modifications have been made to the APIs to avoid sending multiple requests to the update DC data model.
SR-C2539 · Issue 349521
Reduced calls to pzUpdateClipboardModels on interaction tabs
Resolved in Pega Version 7.4
When selecting the interaction tab (call tab), the openWorkByHandle action was triggering the pzUpdateClipboardModels activity twice, once for the interaction work object, and a second time for the service work object. This has been corrected: when selecting the interaction tab for an interaction that has a service case, a single request will be triggered.
SR-C26 · Issue 343916
Removed unneeded save button for delegated data types
Resolved in Pega Version 7.4
When delegated data types were updated, a "Save" button was shown. Clicking on this produced an error in a pop-up. In this case, the lines of the data type were updated automatically and there was no need for the Save button. To avoid the error, a condition has been added to hide the Save button for delegated rules.
SR-C3006 · Issue 344948
Fixed Advanced Agent runtime determinations
Resolved in Pega Version 7.4
While implementing the use case of running an Agent 24 hours apart in only one node in the cluster, using the improved Advanced agent control https://pdn.pega.com/improved-control-running-advanced-agents/improved-control-running-advanced-agents was not working as expected. Intermittently, the agent would not run in any of the nodes in a day, but the very next day it would run on two nodes in the cluster. This was caused by a calculation error in determining the difference between the last run start time and next run start time, and has been fixed.