If it's nice, review sans advice.
On this page
- Stage Name
- Internal Name
- Node Colour
- Target Duration
- Visibility
- Display Card
- Form
- Review
- Advanced Options
- Events
Stage Name
This is the name of the stage.
This will be visible to end users and on the node within the workflow designer.
Internal Name
This is not editable.
This is our internal value we give this node. This will not be seen anywhere other than here. It is useful for techies who use APIs.
Node Colour
This is the stage colour, this is editable from a list of predefined options (this is to ensure we are WCAG AA compliant).
It will be visible to end users and on the node within the workflow designer.
Target Duration
This is so you can set an ideal length of this stage in days. This is a numerical value input.
This value is used to determine if a record is running overdue within the personal page features.
For example, if you set Target Duration = 7
After 7 days the record will become overdue.
If automation is enabled the record will move to the next stage after 7 days.
Visibility
There are three visibility states. This will change the record visibility on discover and personal pages to other users.
- Visible (Default) - the record will be visible to all users with permissions to view.
- Draft - the record will be visible to owners, process managers and admins only.
- Hidden - the record will be visible to admins only.
Display Card
Here you can select which card will be used with this record in this stage. You can find out more information on card configuration here.
If you wish to maintain card appearance across the whole workflow, the same card must be selected at each stage.
Form
Here you can set which form is used with this record in this stage. You can find out more information on form configuration here.
If you wish to maintain forms across the whole workflow, the same form must be selected at each stage.
Manage Form
Here you can manage the visibility of each field and table on the form when the record is in this stage. A powerful option if you want to trim form contents based on stages!
There are four field/table states:
- Visible (Default) - this field/table will be visible to any users.
- Required - This field/table will be required to have an input by users.
- Read-Only - this field/table cannot be edited by users.
- Hidden - this field/table will not visible to any users.
Review
Stage Reviewers
This is a editable list of specific users who can edit the review a record in this stage.
Required Number of Approvals
This is a numerical value input. This is the required amount of reviewers that need to have approved the review before the record can be moved to the next stage.
If the required number of approvals is reached and the required number of reviews is not reached. The record cannot be moved to another stage.
Required Number of Reviewers
This is a numerical value input. This is the required amount of reviewers that need to have completed reviews before the record can be moved to the next stage.
If the required number of reviewers is reached and the required number of approvals is not reached. The record cannot be moved to another stage.
Both required number of approvals & reviewers must be reached to move the record to the next stage in the workflow.
Checklist
This is a configurable list of items that reviewers will have to mark as complete before submitting their review.
All of these items will need to be marked as complete before a review can be submitted - they are not optional.
Advanced Options
Read Only Override
If enabled, all form contents will be editable to Process Managers.
This will override any specific field/table behavior set in Manage Form.
Edit Access
Here you can define pools of users who can edit the record in this stage. There are three groups of users:
- Owners
- Reviewers
- Editors
Editors
This is a editable list of specific users who can edit the record in this stage. This can be used to define users who are external to the owners or reviewers groups
Events
Here you can set events to occur when a record enters this stage. Here are the events you can configure:
Create New Version
This will create a new version of the record. This will act like a snapshot which can be used for reference in future.
Prepopulate Data
This will allow you to set pre-populated data into any field or table for when a record enters this stage.
- Configure - set and edit the prepopulated data.
- Always Occur - This event will trigger every time the record enters this stage, not just the first time.
- User Input Override - The configured prepopulated data will replace any user data from other stages.
If the form has consistent fields or tables. User data from previous stages will be overridden by prepopulated data if User Input Override is disabled.