Fortinet black logo

Resolved issues

Copy Link
Copy Doc ID a662fa71-db1d-11eb-97f7-00505692583a:10837
Download PDF

Resolved issues

Following is a list of some of the important defects addressed in FortiSOAR release 7.0.1:

  • Bug #0697187: Removed system modules, such as routers, tenants, agents etc., from the list of modules that can be used by the FortiSOAR ML Engine connector to train the ML engine to analyze your existing record data and then recommend similar records and predict and assign field values in records.
  • Bug #0714401: Disabled character limits on fields for which encryption is enabled. Prior to version 7.0.1, the character limit of 255 characters was applicable to encrypted fields; which could lead to failure while trying to save that field. Therefore, now when the encryption property is enabled on any field, then the character limit of that field is changed to match its MAX Field Length.
  • Bug #0716977: Fixed the issue that relationship fields were getting updated when you updated primary fields in the 'more information needed' popups, such as the 'Closure Notes' popup. This used to cause an override conflict when the same record was updated outside the current browser window.
  • Bug #0717760: Fixed an issue with a SAML user where the lastName of the user used to be set to "Me" if the lastName was not received from the provider. Now, this has been fixed as follows:
    • If the provider sends neither the firstname or lastname, then the SSO will be set to "Change Me" for the firstname and lastname.
    • If the provider sends either the firstname or lastname, then the SSO will set to the same and the other one will be kept blank.

  • Bug #0718007: Fixed the issue that in case of SSO users, their lock/unlock and inactive/active status was not being displayed in the users' grid on the Users page.
  • Bug #0721147: Fixed the issue that the Token Refresh API call was getting triggered from every browser tab of same browser instance, causing multiple token exits and activations for a single logged-in user session. Now, only a single token refresh call will be made for the same instance.
  • Bug #0721186: Fixed the issue with the manual input, where a step that was not selected in the manual input path, was yet getting executed, even though it was not mapped to any action from manual input. Now, such steps will be skipped.
  • Bug #0722107: Fixed the issue of FortiSOAR audit logs disclosing private IP addresses in the source field. .
  • Bug #0722279: Fixed the issue that fields added to a manual trigger input prompt using the 'Record Field' option and those that were marked as read-only in the Module editor such as the Tenant field would be non-editable in the input prompt. Now, this issue is fixed by allowing input selection for such fields.
  • Bug #0725620: Fixed an issue that the manual trigger input prompt would fail to load if a field in the prompt was added using the 'Record Field' option and the user does not have access to that field. Now, appropriate messages are displayed if users do not have access to the input fields.
  • Bug #0726283: Fixed an issue with playbook execution logs not displaying appropriate logs due to application of incorrect tag filters. For example, while viewing individual playbook execution history the default 'exclude' filter was getting applied due to which the execution history for a system playbook was not getting displayed. Now, this issue is fixed by not applying any filter on playbook execution history for an individual playbook.
  • Bug #0726965: Fixed an unclear message: Unlinked Manual Input - Record IRI passed is invalid that would be displayed when a user did not have access to a manual input. Now, the message has been updated and made cleared as: Invalid Request - Issues with linked record or permissions.
  • Bug #0727048: Added audit logs for successful logins on FortiSOAR MEA by FortiAnalyzer or FortiManager users. Also added audit logs for successful logins by users on FortiSOAR Cloud.
  • Bug #0728438: Fixed the issue with comments not getting linked to the record. This issue occurred as the Comments widget used the module's name while linking comments rather than the field name on the Comments module. This has been fixed and now the Comments widgets uses the relationship field name for linking.
  • Bug #0728525: Fixed an issue with Dynamic Variables displaying the spinning wheel and not loading in some playbooks that were upgraded from 6.4.4.
  • Bug #0729558: Fixed an issue that caused failure while loading the Correlation Graph if there was any non UTF-8-character present in the data of display name fields, such as incident name, or source fields.

Resolved issues

Following is a list of some of the important defects addressed in FortiSOAR release 7.0.1:

  • Bug #0697187: Removed system modules, such as routers, tenants, agents etc., from the list of modules that can be used by the FortiSOAR ML Engine connector to train the ML engine to analyze your existing record data and then recommend similar records and predict and assign field values in records.
  • Bug #0714401: Disabled character limits on fields for which encryption is enabled. Prior to version 7.0.1, the character limit of 255 characters was applicable to encrypted fields; which could lead to failure while trying to save that field. Therefore, now when the encryption property is enabled on any field, then the character limit of that field is changed to match its MAX Field Length.
  • Bug #0716977: Fixed the issue that relationship fields were getting updated when you updated primary fields in the 'more information needed' popups, such as the 'Closure Notes' popup. This used to cause an override conflict when the same record was updated outside the current browser window.
  • Bug #0717760: Fixed an issue with a SAML user where the lastName of the user used to be set to "Me" if the lastName was not received from the provider. Now, this has been fixed as follows:
    • If the provider sends neither the firstname or lastname, then the SSO will be set to "Change Me" for the firstname and lastname.
    • If the provider sends either the firstname or lastname, then the SSO will set to the same and the other one will be kept blank.

  • Bug #0718007: Fixed the issue that in case of SSO users, their lock/unlock and inactive/active status was not being displayed in the users' grid on the Users page.
  • Bug #0721147: Fixed the issue that the Token Refresh API call was getting triggered from every browser tab of same browser instance, causing multiple token exits and activations for a single logged-in user session. Now, only a single token refresh call will be made for the same instance.
  • Bug #0721186: Fixed the issue with the manual input, where a step that was not selected in the manual input path, was yet getting executed, even though it was not mapped to any action from manual input. Now, such steps will be skipped.
  • Bug #0722107: Fixed the issue of FortiSOAR audit logs disclosing private IP addresses in the source field. .
  • Bug #0722279: Fixed the issue that fields added to a manual trigger input prompt using the 'Record Field' option and those that were marked as read-only in the Module editor such as the Tenant field would be non-editable in the input prompt. Now, this issue is fixed by allowing input selection for such fields.
  • Bug #0725620: Fixed an issue that the manual trigger input prompt would fail to load if a field in the prompt was added using the 'Record Field' option and the user does not have access to that field. Now, appropriate messages are displayed if users do not have access to the input fields.
  • Bug #0726283: Fixed an issue with playbook execution logs not displaying appropriate logs due to application of incorrect tag filters. For example, while viewing individual playbook execution history the default 'exclude' filter was getting applied due to which the execution history for a system playbook was not getting displayed. Now, this issue is fixed by not applying any filter on playbook execution history for an individual playbook.
  • Bug #0726965: Fixed an unclear message: Unlinked Manual Input - Record IRI passed is invalid that would be displayed when a user did not have access to a manual input. Now, the message has been updated and made cleared as: Invalid Request - Issues with linked record or permissions.
  • Bug #0727048: Added audit logs for successful logins on FortiSOAR MEA by FortiAnalyzer or FortiManager users. Also added audit logs for successful logins by users on FortiSOAR Cloud.
  • Bug #0728438: Fixed the issue with comments not getting linked to the record. This issue occurred as the Comments widget used the module's name while linking comments rather than the field name on the Comments module. This has been fixed and now the Comments widgets uses the relationship field name for linking.
  • Bug #0728525: Fixed an issue with Dynamic Variables displaying the spinning wheel and not loading in some playbooks that were upgraded from 6.4.4.
  • Bug #0729558: Fixed an issue that caused failure while loading the Correlation Graph if there was any non UTF-8-character present in the data of display name fields, such as incident name, or source fields.