Fields
Filesystem
A required field. The system offers several sorts of file systems that can be used. It is up the the user to decide what will fit his needs. Based on the selected type additional configuration might be needed.When the file exists
A required field. Offers control on what to do when the file already exists. Either overwrite it or find an alternative filename. Overwriting obviously could result in the loss of data. Based on the selection additional configuration might be required. Two options are available: - Overwrite When the output file already exists it will be overwritten, risking data loss. - Add a increasing number to the filename Keeps increasing a number in the filename. The format can be influenced based on a template. Several configuration options are available.File path and contents
Path Source A required field. Describes the source where the transformer will get the path to store the file from. There are two options: - Get path from the data: If there is a path given in the context data it can be set here. The filename must be included in the path. - Custom path A text field where the output path can be set. The filename must be included in the path. The field supports the placeholders allowing the path and filename to be build from dynamically based on context data. This is not the source of the data that will be written to the file. Contents source A required field. Describes the source of the content that will be put inside the file. There are two options: - Get contents from the data Put in a path that points towards the data in the context data. - Custom contents Allows for custom content that can be placed inside the contents field. Supports placeholders to get data from the entity context.A mapper can be applied to convert the data to for example json or xml.