Actions
Actions perform functions, such as sending email or populating a PDF, and are executed after an event is triggered. By Drag & Drop an action or clicking on the node, an action can be added to an event and thus to a processing chain.
Each action consists of at least:
- name
- The name of the action
- Description
- The description is optional.
There are two different action types.
Deploying actions
A providing action creates or provides files that are further processed by the processing actions.
Deploying actions are:
- Export as XML
- Provide file
- Export as persistence file
- Fill PDF document
- Create text file
- Fill Word document
- Compress ZIP
- Process log as PDF 7.2.0+
Processing Actions
These actions process files from various sources. Most actions allow files from the following sources
- Form files
- Client files
- Files from previous actions
- File from upload elements
- Form record attachments
- External resources (URL)
Note that not all protocols are supported for URLs due to security considerations. The following protocols are allowed:
- http
- https
- ftp
- sftp
- scp
- smb
- nfs
- data
- git
Processing actions are:
- Import from XML
- File download
- Database query
- Change form values
- HTML response page
- Move to inbox
- LDAP query
- Create new process ID
- Run plugin
- HTTP request
- Create log entry 7.2.0+
- Set server attribute
- Save to file system
- Save to WebDAV server
- Change state
- Stop task
- Change Availability
- Copy form record
- Delete form record
- Redirect
- Compress files
- Save
- Send double opt-in email
- Change counter
Plugin actions
New actions can be added by plugin. These actions can be providing or processing actions. These actions are documented on the pages of the respective plugin which provides them.