FortiSOAR uses the python arrow library to assist with dynamically
rendering time. Common uses are setting the current time to be used in a
field, shifting time backwards for data ingestion, or to be used in
API's (The joy of working with different a<!-- --><!-- --><!-- --><!-- --><!-- --><!-- --><!-- --><!-- --><!-- -->...
@khilfi You are correct that the ENV where all known data to the
playbook resides does not contain the vars.steps. json. As a best
practice, I recommend always creating a variable that has the step
results in it. That way the data is available in the...
Hi @RamboV , you can self host a community (Trial) instance by following
the instructions here.
https://docs.fortinet.com/document/fortisoar/7.6.2/deployment-guide/158469/deploying-fortisoar#Installing_FortiSOAR_7.6.2_using_the_FortiSOAR_installerAft...
Hey @JoseOjeb , I have found the issue in the jinja. The issue is the
spaces that are around the {<!-- -->{(Severity ... }} expressions. One quick
solution is removing the spaces, another is adding in whitespace trim
expressions to the if statements to remov<!-- --><!-- --><!-- --><!-- -->...