At line 1 changed 4 lines |
All have a start and end and use curly brackets. Some take additional parameters separated by colons. : |
|
They are also processed in this order of sequence as listed here:\\ |
|
Function syntax consists of a start and end tag, the function name to be enclosed in curly brackets. Take at least one parameter as "argument". Some take additional parameters separated by colon characters. Generic syntax: |
{{{ |
{functionname_start:optionalargument1:optionalargument2}argument{functionname_end} |
}}} |
The arguments can be text or numeric literals or server variables. Special case of optional arguments, when these contain the colon (:) character itself, that needs to be manually encoded as ~..~. |
The functions are processed by the replacement engine in this very order of sequence as listed here.\\ |
---- |
!General purpose |
\\ |
At line 131 changed one line |
!Save, Load, and Add to named list items in a job flow. (UserVariable task only) (CrushFTP 10.3.0_43+ supports this)\\ |
!Special functions that only work in the UserVariable task\\ |
__Save, Load, and Add to named list items in a job flow. (UserVariable task only) (CrushFTP 10.3.0_43+ supports this)__\\ |
At line 152 added 5 lines |
__Parse in a JSON object, explode to a list of key name - key value pairs__ |
{{{ |
json_parse_start |
}}} |
Use it like {json_parse_start}{myJson}{json_parse_end} with it's argument a variable referencing a JSON object. Can dereference a particular key value with the key name enclosed in curly brackets ( like {mykey1} ). It doesn't work with nested JSON structures.\\ |
At line 147 changed one line |
!Special functions that only work in the UserVariable task |
__Parse in an XML file, explode to a list of key name - key value pairs__\\ |
At line 149 changed one line |
Parse in a JSON object, explode to a list of key name - key value pairs |
__!!!Restriction:__ Only works for XML attributes: __type="properties"__ or __type="vector"__.\\ |
\\ |
At line 151 changed one line |
json_parse_start |
{xml_parse_start}{file_contents}{xml_parse_end} |
}}}\\ |
\\ |
You can also convert the input XML into a parsable format:\\ |
{{{ |
{xml_parse_start}{replace_start:<mytag:<mytag type="properties"}{file_contents}{replace_end}{xml_parse_end} |
}}}\\ |
{{{ |
{xml_parse_start}{replace_start:<mytag:<mytag type="vector"}{file_contents}{replace_end}{xml_parse_end} |
At line 153 changed one line |
Use it like {json_parse_start}{myJson}{json_parse_end} with it's argument a variable referencing a JSON object. Can dereference a particular key value with the key name enclosed in curly brackets ( like {mykey1} ). Doesn't work with nested JSON structures. |
\\ |