XSD
Allows to do an XSD validation. For example you need to check your Import Table XML file.
Json
Example
json
{
"name": "file-validation-xsd",
"taskReferenceName": "b",
"description": "The business description of the task",
"type": "SUB_WORKFLOW",
"optional": false,
"inputParameters": {
"mode": "FILE",
"file": "${a.output.file}",
"xsd": "file://assets/file.xsd",
"xsdVersion": "1.0",
"failOnError": true
}
}1
2
3
4
5
6
7
8
9
10
11
12
13
14
2
3
4
5
6
7
8
9
10
11
12
13
14
Definition
| Property | Type | Required | Description |
|---|---|---|---|
| The name (or type) of the task | |||
| The unique name of the task in your job. It is used to reference this task in the workflow. | |||
| The functional description of this task in your job. | |||
The type of the task. It must be SUB_WORKFLOW. | |||
true: the job continues if there is an error on this task. false: the job fails. | |||
| Input parameters of the task. See below |
Inputs
| Property | Description |
|---|---|
| mode | Enum FILE | FILES. |
| file | A valid input. It can reference the output of a previous task, example: ${previous_taskReferenceName.output.file} , or a static file, example: file://assets/file.xlsx, or a user input, example: ${workflow.input.input_key}. |
| files | A valid input. It can reference the output of a previous task, example: ${previous_taskReferenceName.output.files} , or a user input, example: ${workflow.input.input_key}. |
| xsd | An XSD file. |
| xsdVersion | The xsd version must be 1.0 |
| failOnError | true: the task will fail if only one file is invalid. |
Outputs
| Property | Type | Description |
|---|---|---|
| allFilesValid | YES | NO. YES: all files have been validated successfully. NO: at least one file has not been validated. |
Limits and additional notes
- The limitation of the input file size is 500 Mb.
FAQ
What is the version of XSD?
XSD 1.0