Resolved Issues
The following important issues have been fixed in FortiSOAR release 7.6.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 |
|
0951771 |
Fixed the issue where the visibility condition did not work when applied to a multiselect picklist field that was populated. |
|
0955945 |
Fixed an issue with the Date/Time format for a filter applied on 'Global Search'. The filter's Date/Time format did not match the format set on the FortiSOAR UI. |
|
0961995 |
Fixed the issue where the 'Set as Default' filter was not being retained or applied to grids in the 'Correlations' sub-tabs of the 'View' panel. |
|
1022900 |
Fixed the issue where the username was not being populated when using the @ sign in the collaboration panel. |
Playbook Fixes
| Bug ID | Description |
|
0984457 |
Fixed an issue where a playbook's trigger step did not respect multiple selections made for a dynamic list field type provided in an input prompt. |
|
1000576 |
Fixed the issue where web components such as a drop-down on an external manual input form, appeared with a white background, making it challenging to read. From now on, all components on the external manual input form will now adhere to the default 'Space' theme. |
|
1010821 |
Fixed the issue of UI-triggered playbooks that required record inputs. UI-triggered playbooks are playbooks where users have added a button to trigger a Manual Trigger or Reference Playbook on pages such as the Dashboard, View Panel, Listing, etc. for specific operations. |
|
1015887 |
Fixed the issue with the Jinja expression not rendering correctly in the 'Simplified' view when a dictionary key contained a space. |
Other Fixes
| Bug ID | Description |
|
0882723 |
Fixed the issue where the default value of a field was not being respected in the 'Add' view of a record for a user who does not have access to the field. Now, the default value of that field is applied in the 'Add' view of a record for such users. |
|
0950816 |
Fixed an issue where changes made to the owners of queues were not being saved while editing queues. |
|
0950880 |
Fixed the issue where the Data Ingestion Wizard was unable to proceed past the 'Fetch Data' step when the 'Append' option was chosen to include correlations in the 'Create Record' step of Data Ingestion Playbooks. |
|
0957360 |
Fixed the issue where records were not being cloned when there was an integer field in the display name of a module. |
|
0966289 |
Fixed the performance metrics widget’s Median calculation handling. The time range field value is not considered in the payload if the filter criteria contains any date-time type field. |
|
0973850 |
Fixed the issue of multiple roles not being considered for field-level permissions. Now, aggregated field-level permissions are being taken into account. |
|
0993829 |
Fixed the issue where users needed the ' |
| 1008243 |
Fixed the browser storage issue related to large metadata and its copies. Release 7.6.0 included optimized browser storage usage for efficient management of model metadata. |
|
1008615 |
Fixed the issue where FortiSOAR Configuration VM would fail when the proxy username and password contained special characters such as ' |
|
1010299 |
Fixed the issue where listeners started during the testing or editing of connectors were not stopped unless the test configuration or connector was deleted, leading to performance issues due to memory consumption. Now, when a new test configuration is added while editing a connector in FortiSOAR, the listeners started by previous test configurations will be stopped. Furthermore, once the connector is published and configured, all previous listeners started by the test configurations will be stopped. |
|
1040066 |
Increased the license verification grace period for FortiSOAR to improve handling during an FDN outage. |
|
1014915 |
Fixed the error with the 'Round Robin' queue, which was incorrectly assigning alerts to the same member instead of assigning alerts to each member of the queue sequentially when alerts were created more than ten minutes apart. |
|
1014917 |
Fixed the issue where FSR Agent's appliance keys were not getting propagated to other nodes of a cluster when the Agent was created after cluster formation. |
|
1024559 |
Fixed the issue that prevented FortiSOAR from connecting to the local server if a user skipped the 'Set Hostname' step in the FortiSOAR Configuration VM, resulting in missing entries in the |
|
1039585 |
Fixed the issue of schedules were not being saved when its frequency was set for multiple days in a week. |
|
1047562 |
Fixed the issue of missing audit logs entries for records such as a manual inputs with its IRI set to null, relationship processing failing in case of linked records such as comments that were not associated with a specific module, etc. |
|
1050554 |
Fixed the issue encountered by non-admin users when navigating to a dashboard or report that requires user input and then moving to a module page (such as alerts or incidents). Previously, opening and closing the detail view of a record would result in a blank page with a message saying " |
|
1050823 |
Added a check to display lag replication statistics during the suspend-cluster operation. |
|
1053596 |
Fixed the issue of Threat Intelligence Management (TIM) Feeds not getting purged as the scheduled playbook "Purge Expired Threat Intel feed" was failing due to an out-of-memory error. |