Troubleshooting Tip: After upgrading to 7.4.1, previously added custom functions are not visible in the playbooks while using the Dynamic Values Window

[nmathur]

Description	This article describes how to fix the issue of existing custom expressions not being available in the Dynamic Values, after upgrading to FortiSOAR release 7.4.1 from any release prior to 7.4.1. Release 7.4.1 has introduced a user-friendly way of creating custom functions. It is possible to either recreate the existing functions using this new method or to use the steps detailed in this article to resolve the issue. For information about the new method of creating custom functions, see the Connector Guide in the FortiSOAR Product Documentation.
Scope	FortiSOAR instances that have been upgraded to 7.4.1 from releases previous to 7.4.1.
Solution	To resolve this issue, carry out the following steps: Open the my_expressions.json file located under /opt/cyops-workflow/sealab/expression_builder/custom. Ensure that the 'params' JSON object in the my_expressions.json file for each expression has the 'visible' attribute set to true. "params": [ { "name": "input", "title": "input", "type": "text", "value": "", "visible":true, "required": true }, { … "visible":true, … } ] Download the populate_custom_functions.zip file attached to this article to the FortiSOAR instance. Unzip the file. Note that it contains the populate_custom_functions.py file. Copy the populate_custom_functions.py file to /opt/cyops-workflow/sealab/expression_builder/management/commands. Switch to the 'root' user:  sudo su  Change the ownership of the populate_custom_functions.py file as follows: chown nginx:nginx /opt/cyops-workflow/sealab/expression_builder/management/commands/populate_custom_functions.py Run the following command: /opt/cyops-workflow/.env/bin/python3 /opt/cyops-workflow/sealab/manage.py populate_custom_functions