Resolved Issues

Following is a list of some of the important defects addressed in FortiSOAR release 7.2.0. This release also includes important security fixes.

• Bug #0679817: Fixed the issue of import failing in the case of playbook collections if playbooks in the collection contained a remote reference step.
• Bug #0730539: Fixed the issue in the handling of default value attributes so that the default value gets honored even if records are updated using APIs, such as updating the attribute using a playbook, such as the 'Escalate' playbook. Earlier, the default value attribute defined in the MMD got applied only when records were created using the FortiSOAR UI.
• Bug #0703540: Fixed the issue with generated reports to improve their readability. Earlier, generated reports that had long paragraphs would have their word-wrapped, which caused issues with readability. Now, the generated reports have end-of-the-line words formatted as hyphenated words, or the words are moved to the next line.
• Bug #0744893: Fixed the following issues in the grid view of a playbook:
  • Inability to horizontally scroll the playbooks grid if more columns are added to the grid.
  • Visibility of the 'Last Modified On' option in the grid. The 'Last Modified On' option is for system use and it being visible on the grid used to create confusion. Now, only the 'Modified On' option is visible in the grid.
• Bug #0746678: Fixed the issue with the default sort that is specified in the model metadata for query API.
• Bug #0747880: Fixed the issue of export silently failing in the case of referenced playbooks that contain references to themselves or looped references.
• Bug #0758480: Fixed the issue of the 'Configure Report Inputs' field in reports not getting sorted in alphabetical order.
• Bug #0763209: Fixed the issue of a reference playbook that contains a do_until condition, running in a loop until it reaches the maximum retries limit. This was because the condition evaluation in do_until always used to return false causing the playbook to run in a loop.
• Bug #0766486: Fixed the issue in report scheduling where scheduling would not work if the input type is specified as 'lookup' for the report.
• Bug #0769338: Fixed the issue with the 'Comments' widget, both on the collaboration panel and the main record detail view, wherein some records that contain HTML in a rich text field, users cannot see the text that they are typing in the text field; however, the text is visible in the 'preview' mode on the widget.
• Bug #0770460: Fixed the inconsistency in the naming convention for many-to-many fields when self-linking for the reverse module by the API.
• Bug #0770515: Fixed the 'log4j' security vulnerability and removed the dependencies on affected packages.
• Bug #0770706: Fixed an issue with relative date filters that caused a custom filter using the 'created on' field to not work in the 'Find Records' playbook step.
• Bug #0775432: Fixed the issue of failed cluster commands accumulating for passive nodes in an HA cluster environment.
• Bug #0777960: Fixed the issue of FortiSOAR not displaying maintenance pack or security patch information on the UI/CLI, leading to the inability of administrators to confirm whether a maintenance pack or security patch is installed on the FortiSOAR system. Now, you can see these details on the UI wherever FortiSOAR's version information is displayed, including the version dialog, login page, etc.
• Bug #0782224: Fixed the issue breaking of a do_until loop in the case of a reference playbook that contains a manual input. Now, until user input is provided, the reference playbook will continue retrying and keep sending the manual input.
• Bug #0782839: Removed the requirement of assigning Create or Modify permissions on the Application module to save user preferences, which fixed the following issues:
  • Saving user preferences.
  • Saving user-created filters as 'User' filters and not as 'System' filters.
  • Displaying of user-level filters only to the users.
• Bug #0784317: Fixed an issue with SSO users being unable to log into FortiSOAR in an AWS instance, where the user_id was set as the email of the users.
• Bug #0789581: Fixed the issue of administrators being unable to implement custom password policies. Now, administrators can set up custom password policies, which enforce additional restrictions (apart from the default rules) on the passwords that users can create.
• Bug #0796003: Fixed the issue with the 'Is In List' and 'Is Not In List' conditions when added to the 'On Create' trigger playbooks that caused a failure to trigger the 'On Create' playbooks even after fulfillment of the 'Is In List' and 'Is Not In List' conditions.
• Bug #0797162: Fixed the Spring4Shell and CVE-2022-22963 vulnerabilities.