Known Issues and Workarounds

• Issue #0678796: If the version of your Report Engine connector is prior to 1.0.2, the "Export Report" system playbook (Settings > System Fixtures > Report Management Playbooks) did not have the timezone parameter, so if after upgrading the Report Engine to the latest version (1.2.0), even then the report does not get exported based on the selected timezone.
  To resolve this issue, and export the report based on the selected timezone, do the following:
  1. Navigate to Settings > System Fixtures > Report Management Playbooks.
  2. Open the Export Report Playbook.
  3. Open the Generate Report from Report ID step from which copy the values of the Report ID and Report Params fields.
  4. Delete the Generate Report from Report ID step.
  5. Add a "Connector" step and select the Report Engine v1.2.0 connector.
  6. Select the Generate Report From Report ID action.
  7. Paste the values of the Report ID and Report Params fields that you had copied in step 3.
  8. Save the playbook and export the report as PDF.
     Now, the report gets exported based on the selected timezone.
• Issue #0679697: The csadm db --externalize command fails with a "Failed to drop database <name of database>" error in case the FortiSOAR database is present on an external PostgreSQL server.
  This issue occurs if there is a stale connection present to the FortiSOAR database on the external PostgreSQL server. To resolve this issue and release all stale connections, restart the Postgres service using the following command:
  systemctl start postgresql-<postgresql version>
  For example, systemctl start postgresql-12
• Issue #0679759: When you stop a schedule the value, i.e., the DateTime of the Last Run At field becomes blank.
  This issue will be resolved in future releases of FortiSOAR.
• Issue #0679776: If you select both the Row Expandable and Enable Horizontal Scrolling in the grid view template and if in the grid view of the module you expand a record, then, in this case, the UI of the records following the expanded row might get scattered.
  This issue will be resolved in future releases of FortiSOAR.
• Issue #0679841: You must ensure that the relations that you are adding while configuring co-relationships between modules are correct. FortiSOAR does not prevent the creation of incorrect relationships between modules. Therefore, you must ensure that you add correct bidirectional relationships for both the modules for which you want to define the relationship. For example, if you define a Many to One relationship on the Alerts module for the Events Module, then in the Events module you must define a "One to Many" relationship for the Alerts module.