DOCUMENT LIBRARY

FortiGate / FortiOS

Release Notes

Home FortiSOAR 7.4.0 Release Notes

7.4.0

Resolved Issues

Resolved Issues

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

FortiSOAR UI Fixes

Bug ID	Description
0869849	Even when 'Publish' was completed in the primary browser window, other browser windows or tabs still displayed the 'System Publish in progress' message till users do not refresh the page. Now, the other browser windows or tabs resume the session, once publish is completed.
0876001	When the "Record Independent" option was chosen for "Manual Input" playbooks, the "User Prompt" fields did not appear in the Executed Playbook Logs.

Playbook Fixes

Bug ID	Description
0802480	When playbooks were triggered with very large payloads, the FortiSOAR UI was not displaying any messages. Now when playbooks are triggered with very large payloads, the FortiSOAR UI displays an error such as "`The request payload was too large. Please try again with a smaller payload`."

Connector Fixes

Bug ID	Description
0884253	Connector configurations were not securely storing sensitive information such a passwords. Now, this issue is fixed and sensitive information is getting securely stored.
0886830	Connector dependencies were sometimes not getting updated. Now, this issue is resolved and connector dependencies are getting correctly installed.

API Fixes

Bug ID	Description
0870506	Updated the `Bulk Ingest Feed` API to retain the data of existing records and only update the changed fields. In previous releases, calling this API would cause all of the module's fields to be reset, even those of records that already existed within the module.

Other Fixes

Bug ID	Description
0631018	When a FortiSOAR Agent was deleted its corresponding appliance was not getting deleted.
0804813	The `fromIRI` jinja filter was not working in the Jinja Editor.
0827713	The '`join`' queries were taking lot of time to execute on the PostgreSQL database.
0871158	When the ownership of manual inputs was assigned to Teams, then such manual inputs were not getting deleted.
0884300	On a FortiSOAR instance that had been upgraded from 7.2.x to 7.3.x, an issue that caused the Elasticsearch backup to fail while backing up Elasticsearch data has been fixed.
0887704	The Jinja that you needed to specify while assigning a manual input to a specific user, required to be specified in the dictionary format, for example, `{"iri": "/api/3/people/XXXXXX"}`. A string IRI, for example, `"/api/3/people/XXXXXX"`, or list of IRI's, for example, `["/api/3/people/XXXXXX","/api/3/people/XXXXXX"]` were not supported. Now, all formats, i.e., dictionary, string IRI, and list of IRI's are supported.

Previous

Next

Resolved Issues

Resolved Issues

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

FortiSOAR UI Fixes

Bug ID	Description
0869849	Even when 'Publish' was completed in the primary browser window, other browser windows or tabs still displayed the 'System Publish in progress' message till users do not refresh the page. Now, the other browser windows or tabs resume the session, once publish is completed.
0876001	When the "Record Independent" option was chosen for "Manual Input" playbooks, the "User Prompt" fields did not appear in the Executed Playbook Logs.

Playbook Fixes

Bug ID	Description
0802480	When playbooks were triggered with very large payloads, the FortiSOAR UI was not displaying any messages. Now when playbooks are triggered with very large payloads, the FortiSOAR UI displays an error such as "`The request payload was too large. Please try again with a smaller payload`."

Connector Fixes

Bug ID	Description
0884253	Connector configurations were not securely storing sensitive information such a passwords. Now, this issue is fixed and sensitive information is getting securely stored.
0886830	Connector dependencies were sometimes not getting updated. Now, this issue is resolved and connector dependencies are getting correctly installed.

API Fixes

Bug ID	Description
0870506	Updated the `Bulk Ingest Feed` API to retain the data of existing records and only update the changed fields. In previous releases, calling this API would cause all of the module's fields to be reset, even those of records that already existed within the module.

Other Fixes

Bug ID	Description
0631018	When a FortiSOAR Agent was deleted its corresponding appliance was not getting deleted.
0804813	The `fromIRI` jinja filter was not working in the Jinja Editor.
0827713	The '`join`' queries were taking lot of time to execute on the PostgreSQL database.
0871158	When the ownership of manual inputs was assigned to Teams, then such manual inputs were not getting deleted.
0884300	On a FortiSOAR instance that had been upgraded from 7.2.x to 7.3.x, an issue that caused the Elasticsearch backup to fail while backing up Elasticsearch data has been fixed.
0887704	The Jinja that you needed to specify while assigning a manual input to a specific user, required to be specified in the dictionary format, for example, `{"iri": "/api/3/people/XXXXXX"}`. A string IRI, for example, `"/api/3/people/XXXXXX"`, or list of IRI's, for example, `["/api/3/people/XXXXXX","/api/3/people/XXXXXX"]` were not supported. Now, all formats, i.e., dictionary, string IRI, and list of IRI's are supported.

Previous

Next