After the source is added, the next step is to add a submit rule for the document.
The first Submit rule is configured with Create Submit Rule button. Depending on the selected document source, the relevant submit rules are available:
To customize the name of the Submit button for the end-user on the device and web app, tap on the Submit rule button to edit it:
This action is used to move documents from one user/group to another within the same workflow. Such routing does not require additional saving to the storage, or sending over email. You can preconfigure to whom the documents will be reassigned from the drop-down list of workflow participants.
Additionally, if a user needs to be able to choose a recipient, then choose the Select manually option.
The reassigned documents arrive in either the My Inbox (for a user) or Group Inbox (for groups) section on the device.
This action is used to send documents from Fluix to any email without wasting time on manual entering of the email address and message in the field. You can preconfigure the recipients’ addresses, email subject, custom message, and the document format:
To add preconfigured recipients, enter their e-mails into the ‘to’ field. After each email address, press the ‘+’ button to add the next recipient. Enable Allow user to add more recipients if your users need to add all or some recipients by themselves.
The following file formats are available:
To have the document name included in the subject of the email, add %document% in the subject field.
Note: If a workflow submit rule contains an incorrect pre-defined email address when a user submits files from this workflow, then a delivery failure notification will be sent to a user, an admin, and an owner of the Fluix account.
This action is used to move documents to a folder on your remote storage.
Data can be saved to storage in the following formats:
You can also have subfolders labeled with the user’s e-mail automatically created within the destination folder. Check Create user folder to enable this option. The folder is created once the user submits to the storage for the first time.
This action is used to transfer data to a preconfigured URL. Enter the destination URL and select the file format in the corresponding fields.
Submit by HTTP can be performed in the following formats and methods:
This action is used when Cabinet is selected as a document’s source:
Once users submit a document, it will be automatically uploaded back to the source that it was initially distributed from.
This action is used when documents need to be emailed and digitally signed by a user outside of Fluix.
For this action, make sure to add Inbox as a document source. This way, once a document is signed and returned to Fluix, it will reside under the Inbox tab and can then reach its final destination.
This action will extract the data from the completed PDFs into reports available to the admin in the Data section.
The submit may contain several actions, e.g. send by email and save to storage, that happens simultaneously once triggered.
1. First, you will need to navigate to the workflow builder in the Fluix admin portal (Configurations–>Workflows–>New workflow) and create a new Upload to CRM/ERP submit rule.
2. After you have it in place, you will have to configure its parameters (endpoint URLs, header values, HTTP methods, etc.) based on your needs and the API integration requirements of the service in question. Please note that these requirements differ based on the service you would like to integrate with. Therefore, this is the right place where your inbound IT specialist may join or when to reach out to our support team for assistance.
3. Save changes in workflow. From that moment, upon every single submission of a document, the data will be automatically uploaded to the system.
When a workflow requires a user to be able to choose how a document moves, alternative submit actions are needed. Once the first submit action is created, press the Alternative Submit Rule button to begin creating an alternative one.
After the submit action is selected, the workflow can be published. For details, please proceed to the next article Publishing a Workflow.
The latest updates from our Product team, straight
to your inbox