Fortinet black logo

Release Notes

Home FortiSOAR 7.4.2 Release Notes
7.4.2
7.5.0
7.4.4
7.4.3
7.4.2
7.4.1
7.4.0
7.3.2
7.3.1
7.3.0
7.2.2
7.2.1
7.2.0
7.0.3
7.0.2
7.0.1
7.0.0
6.4.4
6.4.3
6.4.1
6.4.0
6.0.0

Resolved Issues

Resolved Issues

The following important issues have been fixed in FortiSOAR release 7.4.2. This release also includes important security fixes. To inquire about a particular bug, please contact Customer Service & Support.

FortiSOAR UI Fixes

Bug ID Description
0888173 When a user navigated from Dashboards to any other page in FortiSOAR and then back to Dashboards, the user's default dashboard was shown rather than the dashboard that was most recently viewed, edited or created by the user. This is fixed so that when a user navigates from Dashboards to any other page in FortiSOAR and then back to Dashboards, the dashboard that the user most recently viewed, edited, or created will be displayed.

0930324

 The "Clear All" option was not functioning for the system default filters used to search records, i.e., the system default filter was still being applied even after clicking "Clear All" or refreshing your FortiSOAR instance, and a filtered view was being displayed on the FortiSOAR UI. Now that this problem has been fixed, the FortiSOAR UI presents an unfiltered view when you select "Clear All", removing the system default filters that were used to search records.

0935470

Reserved terms like "createdate" and "createDate" were case-sensitive, thus if users typed "createdate" as the field title, FortiSOAR would notify them that it was a reserved word. However, if users put "createDate" as the field title, no warning was shown. Therefore, case insensitivity has been added to field titles for reserved terms.

Playbook Fixes

Bug ID Description

0872074

When a connector step in a playbook failed, evaluated_args were not displayed, even if the failure had nothing to do with the input. For example, if the code snippet connector had invalid syntax, it would fail without showing the invalid code, making it difficult to debug. The evaluated_args that were sent to the connector when it failed are now displayed.

Other Fixes

Bug ID Description

0924492

When users upgraded their FortiSOAR system, the values in multiselect picklists were not being set. This issue is now fixed.

0939942

If a task record is created using a playbook is deleted, the playbook remains in the 'Awaiting' state. A new system playbook has been introduced which is triggered on the deletion of a task record. This system playbook checks if the deleted task is playbook-driven, and the playbook status is 'Awaiting', and if this is the case, the system playbook terminates the playbook.

0943956

In the 'Functions' library, inputs of the 'Integer' type were not being rendered. This issue is now fixed.
Previous
Next

Resolved Issues

The following important issues have been fixed in FortiSOAR release 7.4.2. This release also includes important security fixes. To inquire about a particular bug, please contact Customer Service & Support.

FortiSOAR UI Fixes

Bug ID Description
0888173 When a user navigated from Dashboards to any other page in FortiSOAR and then back to Dashboards, the user's default dashboard was shown rather than the dashboard that was most recently viewed, edited or created by the user. This is fixed so that when a user navigates from Dashboards to any other page in FortiSOAR and then back to Dashboards, the dashboard that the user most recently viewed, edited, or created will be displayed.

0930324

 The "Clear All" option was not functioning for the system default filters used to search records, i.e., the system default filter was still being applied even after clicking "Clear All" or refreshing your FortiSOAR instance, and a filtered view was being displayed on the FortiSOAR UI. Now that this problem has been fixed, the FortiSOAR UI presents an unfiltered view when you select "Clear All", removing the system default filters that were used to search records.

0935470

Reserved terms like "createdate" and "createDate" were case-sensitive, thus if users typed "createdate" as the field title, FortiSOAR would notify them that it was a reserved word. However, if users put "createDate" as the field title, no warning was shown. Therefore, case insensitivity has been added to field titles for reserved terms.

Playbook Fixes

Bug ID Description

0872074

When a connector step in a playbook failed, evaluated_args were not displayed, even if the failure had nothing to do with the input. For example, if the code snippet connector had invalid syntax, it would fail without showing the invalid code, making it difficult to debug. The evaluated_args that were sent to the connector when it failed are now displayed.

Other Fixes

Bug ID Description

0924492

When users upgraded their FortiSOAR system, the values in multiselect picklists were not being set. This issue is now fixed.

0939942

If a task record is created using a playbook is deleted, the playbook remains in the 'Awaiting' state. A new system playbook has been introduced which is triggered on the deletion of a task record. This system playbook checks if the deleted task is playbook-driven, and the playbook status is 'Awaiting', and if this is the case, the system playbook terminates the playbook.

0943956

In the 'Functions' library, inputs of the 'Integer' type were not being rendered. This issue is now fixed.
Previous
Next