Results of type FILE can be saved into file locations using this action. The tasks' owner has to have write access to the respective destination. The following options are available in the configuration:

• Path to the destination folder: a directory where the files will be stored.
• File Name Format: a pattern for the name of the file(s) that will be saved.
• Delete results after days: deletes old results after the given amount of time in days. Results will be deleted once a new result becomes available. The given value has to be an integer number greater than or equal to zero. The check is made using the file's last modification date. Also, the file name will be checked to only differ in the [date] and [time] placeholders. This is relevant when there are multiple resulting artifacts in the same directory.

The Save File action allows storing files in the file system only if the user has the permission Server Administration. However, additional plugins may augment this action with additional file destinations, which may use a separate permissions concept.

The file chooser additionally allows selecting destinations in the Drive. You may also input a directory in the Drive, that has yet to be created. The task owner has to have permissions to use the Drive and have respective permissions for the chosen directory.

There are three placeholders to dynamically determine the resulting file name:

• [filename] - the name of the file as generated by a job
• [date] - the date, when the job was executed
• [time] - the time at which the job was executed

Note: the File Name Format must not define the file extension. The extension will be added at the end.

Pattern:     [filename] [date] [time]

File Input:  abc.pdf
File Output: abc 2017-04-07 09-45.pdf

Path Input:  abc/def.pdf
Path Output: abc 2017-04-07 09-45/def.pdf