Data privacy notice

 

When this content is loaded, usage information is transmitted to Vimeo and may be processed there.

 

             

Workflow action: Save to file system

Modified on Thu, 25 Jan at 5:01 PM

This action allows to store files in the file system of the server for a longer period of time. Files created by actions are otherwise only temporarily available and will be deleted once the workflow is finished.


Contents



The interface for setting the options of actions of type Save to file system.

Parameters

Details about saving to the file system

Files
Selection of files which should be saved. Files from previous actions, files from upload items, task attachments or form files can be selected. See actions for a list of supported URL protocols.


Destination directory
Specification of a path to save the file. If a directory is specified that does not exist, the action will try to create this directory. Please make sure that the appropriate write permissions are available for the target directory. If necessary, ask your system administrator for more information.
Examplesfor saving files in the system user directory:
Windows: C:\Users\fc\form\demo
Linux: /home/fc/form/demo
Allow folder structure in variables
If this option is enabled, variables may contain path segments of the form '<folder name>/<folder name>'.
Otherwise the path separator ('/') is removed from the placeholder. Navigational references to parent file folders are not allowed and will be removed.

Particularities for storing on a network drive

To save files to a network drive, there are a few points to consider:

  1. It is necessary that the network drive on the formcycle server has been shared.
  2. The network path is to be used as the target directory in the action instead of the network letter, so basically the entry you made when integrating the network, for example
    \\my-formcycle-server\data\target
  3. Often there is still the problem that the permission to write to the network drive is missing. To do this, the Tomcat must be granted authorization. In order to make this possible, the Tomcat must be started with a corresponding user because no rights can be assigned to a local service.
    The necessary steps are described in the following article.
    After the user has been switched, the write permission must be set on the network drive.


Action variables

Actions of type Save to file system provide Action variables which can be used in subsequent actions.


Standard action variables

[%$<action name>.SUCCESS%]
Return whether action was successfully executed. Returns Boolean (true/false).
[%$<action name>.RESULT%]
Return all results provided by the action in structured form.
[%$<action name>.ERROR_CODE%]
The error code thrown in case of an error in the action. Empty if no error occurred.
[%$<action name>.ERROR_MESSAGE%]
The thrown error message in the action's error case. Empty if no error occurred.


Action specific action variables

[%$<action_name>.RESULT.absolutePath%]
Absoulute path to the directory where the files were saved.
[%$<actionname>.ERROR.message%]
Error code returned if the export directory could not be created or the files could not be written to the file system.

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article