The <webserviceTrigger> tag encloses the definition for file folders for the storage of generated files.
This tag has no attributes.
| Allowed sub-elements | Quantity | Description |
|---|---|---|
| outputFolder | 1 | Contains the generated files and a log file in case of the successful execution of a job. |
| failedFolder | 1 | Contains the source files and a log file in case of a failed execution of a job. |
Example of a job definition on the basis of the Webservice trigger:
<?xml version="1.1"?>
<jobdefinition name="myjob" model="model.eox" xmlns:xi="http://www.w3.org/2001/XInclude">
<webserviceTrigger>
<outputFolder value="\output" />
</webserviceTrigger>
<actions>
<action name="MyLibrary.MyCustomAction" arguments="List{trigger.params}"/>
<action name="MyLibrary.MyCustomAction" arguments="List{trigger.params.value('mykey')}"/>
<action name="Engineering.MarkFileForDownloadCommand" arguments="List{trigger.outputFolder + 'results\\generated.file'}"/>
</actions>
</jobdefinition>Description:
If the <failedFolder> tag is omitted, as in the example above, the result data are also stored in the directory that is specified in the <outputFolder> tag in case of a failure. If both the <failedFolder> and the <outputFolder> tags do not exist, no logs r result files are stored. This is used to save space when there are many Jobs and the results of the Job are transferred via the PutResultCommand with the Job status (see JobServer.PutResultCommand).
The following actions can be executed by means of WebService triggers: