Fixed the issue with auto refresh not working when widgets, connectors, or solution packs were deleted from the Create tab on the "Content Hub" page.

Fixed the issue of users being unable to terminate playbooks that were in the 'Incipient' state from the FortiSOAR UI.

An update made to the profile picture of a user was not getting reflected on the 'User Tile' widget. This issue has been fixed and now the updated profile picture of the user gets displayed on the 'User Tile' widget.

Fixed the issue with the 'Escalate' button on the alert details page appeared to be loading indefinitely if the alert details page was closed immediately after clicking the 'Escalate' button. Now, the status of the 'Escalate' button in the alert details page is updated after refreshing the page.

In the Content Hub, users were unable to create content with a name that was the same as any existing content. For instance, if your FortiSOAR instance had the 'Fortinet FortiSIEM' connector, you would be unable to create a Solution Pack with that name. Now, as both the name and type are verified for uniqueness in the Content Hub, you can generate content with the same name. However, it is recommended that unique names be given to content created in the Content Hub.

Fixed the issue with 'Last Calendar Month' parameter not being retained while editing widgets.

The complete dictionary of picklist fields such as status, category, etc. in playbook steps such as create record, update record, etc. were getting saved. Saving the complete dictionary of picklists is unnecessary; only the IRI of picklists is required. Therefore, now only the IRI of the picklist fields is saved, which helps reduce that amount of data in the playbook log.

Fixed an issue where, playbooks with multiple manual inputs, the last manual input would trigger all the steps rather than just those specific to that manual input.

Fixed the issue that the reference playbook step was unable to retrieve the last run result.

In a conditional field of a decision step in a playbook, the UI automatically adds the opening and closing parenthesis while saving the playbook. Now, if the condition is generated using some functions from the 'Dynamic Variables' window, then parenthesis get added twice, which causes the playbook to fail. To resolve this issue and prevent parenthesis from being automatically re-added, parenthesis are deleted from the condition field of the decision step.

An issue that caused extra iterations for three-level nested child playbooks with 'Wait' steps or steps set to run on 'Agent' nested at the third level has been fixed.

Fixed an issue with schedulers not terminating playbook instances that were stuck in the 'Incipient' state. Now, playbooks stuck in the 'Active' or 'Incipient' state are terminated automatically when their permissible execution time limit is exceeded.

The error code of the failure was not previously recorded in the failed record logs. Now, the failed record logs include the failure code and the cause of the failure, which simplifies debugging.

To embed an image inside the widget html, the entire path, including the widget version, required to be specified. To resolve this issue, the widgetBasePath variable has been added, which may be used to reference version agnostic paths for assets such as images in the widget html.
Note: This is supported from FortiSOAR release
7.4.1 onwards.

Fixed the problem with the Global Audit page loading slowly when there was a lot of audit data.

While setting up a proxy server using the csadm network set-https-proxy command, the 'https' protocol is used even if the protocol is set as 'http', which causes errors during upgrades and when downloading packages like cryptography, uwsgi, pycryptodome, pyOpenSSL, etc. To fix this issue, the --protocol argument has been concealed in the of the csadm network set-https-proxy command's help and suggestions, and 'http' is used as the default protocol to communicate with the proxy server.

The 'module_permissions' table was never cleaned up, so even when an existing role was re-imported, new permissions were added to that role without cleaning up the old permissions. Now, the new permissions for an existing role that is re-imported now replace prior permissions.

The starting and stopping of schedules were not logged in the audit log. As this is required, the start and stop activities for schedules are now logged in audit logs.