Collaboration
Feathery supports advanced collaboration use cases for form workflows.
Last updated
Was this helpful?
Feathery supports advanced collaboration use cases for form workflows.
Last updated
Was this helpful?
Feathery allows form designers to invite multiple users to collaborate on a single form submission. They can specify the number of collaborators, assign fields, ordering, and more.
In order to use collaboration with your form, you must first enable form collaboration in form settings and save your settings.
Once enabled, you may define collaborator settings in the same place (form settings) or on the user collaboration dialog available from the form publish dropdown (see below).
Collaboration workflows are accessible via your form publish dropdown, towards the bottom.
You have the ability to specify how many people will be collaborating on a single submission, along with which fields each collaborator will be able to fill out. You can also specify if you want them to fill out the form sequentially or not via the Set Collaborator Order toggle.
Feathery stores your configuration into a template, so it's easily accessible the next time you're looking to invite users.
Now that there are multiple collaborators on a submission, the submission isn't considered "complete" until each one of the collaborators has completed their section. You should set up your event triggers accordingly.
For ordered collaborative submissions, you can track the current collaborator whose turn it is to work on the submission. For unordered submissions, you can view all collaborators who still need to complete the submission.
To do this, go to your form results and click Edit Table View. Then, update your table view with a column for the Pending Collaborator attribute. Collaborative submissions will automatically show the pending collaborator in that column.
If you're an admin or the pending collaborator, you can click on the submission and see a button called Open Collaborative Submission, which you can click on to continue working on that collaborator's part of the submission.
Standard and custom account attributes can be prefilled into a collaborative submission when the owner of a Feathery account is the one who's filling out their portion of a collaborative submission. There are two ways you can do so:
Select a field in the designer, go to the Properties tab, Semantic Meaning section, and set the Attribute to the relevant information you'd like to prefill. Then, the account attribute will automatically be prefilled into this field when they load the collaborative submission.
You can access the relevant attribute via the special hidden field feathery.account.<attribute name>. E.g. if you have an account attribute called First Name, you can access its value via the feathery.account.first_name hidden field.
You can add custom logic to your form that is based on the currently active collaborator on the submission. To do this, use the special hidden field: feathery.collaborator. This is supported in:
Custom Validations
Show or Hide rules
Conditional navigation
Logic Rules.
For example, you may wish to hide certain form fields based on the specific collaborator combined with other conditions. The feathery.collaborator hidden field contains the label of the collaborator as configured in settings (see above).
label
string
The collaborator label as defined in the collaborator template configuration. Read-only.
orderNumber
number
The order/position of the current collaborator in the collaborator template configuration. Starts at 0. Read-only.
permission
string
The collaborator's form fields access: 'custom' or 'all'. Read-only.
permissionFields
string[]
If permission is 'custom', then this is an array of field keys.
Feathery also provide a Task view for logged-in users to see all currently assigned tasks (which are form submissions that they've been invited to collaborate on). From this view, they can filter for current or past tasks and complete them. Admins can also see every pending task across their organization.
Invited
Viewed the form
Edited the form
Completed their part of the form
Feathery supports assigning tasks to a collection of users such as a User Groups (defined ) and lists of email addresses. This is useful for assiging tasks to an internal department, for example. Any user in that User Group can claim the collaboration task and complete it. If another user tries to complete the task after it has been claimed, they will be notified that another member has already claimed the task.
When your collaborator template is defined, you'll now see a toggle on your that allows you to define the email recipients as the collaborators on the form submission. This is useful if you want to send a custom email to all of the users who collaborated on a submission.
You have available to set on your form to allow your end users to control the collaboration routing sequence.
Feathery forms make additional information about the active collaborator available within via the feathery.collaborator global object. The collaborator object is a sub-property of the feathery object that is available as a global in all logic rules. The feathery global is documented in the . All properties are READ ONLY.
When the collaboration template is defined, you'll be able to attach an audit log to emails sent out via your . The audit log will contain IP address and timestamps for when each collaborator was:
