A workflow state is a stage or step in the workflow process. There is always a Start state, which you can rename but is always the first state the form's workflow initiates, and you use transitions to determine rules for flowing between states until it finally terminates with Finish.
Each workflow state leading up to Finish is a pause in the flow, waiting for an event - usually for a user to enter data into the form and submit to trigger any relevant transition from that state.
Using States in Design
- Drag and drop states into the workflow. For more information, refer to State Types.
- Review and edit any relevant properties for the state in the Inspector.
- Create any required transitions.
- Save the project.
An alternative to drag and drop to create states is clicking the plus (+) context menu when hovering over an empty grid marker.
Once created, states can be moved around the canvas by clicking and dragging, then releasing on any available grid marker.
- Click to select the state to delete.
- In the Inspector Panel, click the More Options (...) button, and click Delete from the pull-out menu.
Alternatively, once selected you can press 'delete' on the keyboard.
- Confirm the deletion by clicking OK.
Workflows can incorporate the following types of states:
Each of these state types are described in more detail below.
Start is the initial state for all workflow projects, and, while it cannot be deleted, it may be renamed and otherwise behaves very similarly to a regular state. This is commonly used to initiate a process or request, capturing data from the requester.
Users who initiate a workflow form in this state are considered the workflow Creator.
Refer to State Properties for a list of properties in the Inspector for the Start state.
While not strictly a state, Finish represents the final termination of the workflow and is always present in a workflow. It has no properties and, as such, is not selectable in the canvas, and can only have inbound transitions. Once a workflow reaches this state, it cannot progress further and is therefore considered completed.
States are the most common building blocks for your workflow, allowing further data capture after the Start state is completed.
States share several properties with the Start state, with the addition of Observers. You can name these states appropriately, keeping in mind that, by default, state names may appear for end users in their task list. Unlike Start, normal states may be deleted if necessary.
Refer to State Properties for a list of properties in the Inspector for States.
Approvals are re-usable states that take the most common workflow patterns around reviewing and approving or rejecting workflows, and apply in a single step, simplifying what might otherwise be a complex structure to build and maintain.
When added to the workflow, the user can select an approval from the drop-down list of available approvals that have been configured in Manage. See Approvals.
An external step in a workflow that needs to be actioned by a system outside of the SmartIQ platform via Cloud-to-Cloud Integration (C2I). Additionally, the workflow will only progress after the process has finished.
For more information, refer to Events.
The following properties apply to both normal states as well as the Start state, except where indicated.
|Name||By default, Start is named '(Start)' and each new state added is named 'State #' with an incrementing number. The name can be changed at any time, however each state name must be unique.|
|Allow Cancellation||Gives the option to cancel the workflow immediately. Default for Start is to not allow cancellation. When enabled select any of the following user types who can cancel at this state: |
|Due Date||Due Date can be used in a Dashboard to highlight past due tasks. Escalations will run on their own trigger. Available options are: |
|Mentions||Gives the option to engage additional users or invite them to a workflow by mentioning them in a comment using the ‘@’ syntax. Any user mentioned will receive an email notification with a link to the state or comment.|
Users with State Access – Only users that currently have access to the state can be mentioned (default).
Anyone – Any user can be mentioned and they will be dynamically added as an observer to view the task and make comments.
|Observers||(Not applicable on Start state)|
Configure a user or group to view a read-only version of an in-progress workflow as well as specify the communication template to use. For more information, refer to Observers.
|Name||By default, this is the selected Approval type, and, if duplicated, an incrementing number is appended. The name can be changed at any time, however each state name must be unique.|
|Approval||The name of the selected Approval.|
|Enable Quick Approval||Enabling this option gives the Approver the ability to quickly approve or reject the request from the Produce dashboard. See Quick Approval for more information.|
|View||Provides control over what view approvers will see when entering this form to review. Select from 'Form' or 'Summary' (default is Form) as follows: |
|Mentions||Gives the option to engage additional users or invite them to a workflow by mentioning them in a comment using the ‘@’ syntax. Any user mentioned will receive an email notification with a link to the state or comment. |
|Approvers||Configure any approver user roles defined in the Approval in Manage, and map to named users either fixed or dynamic by reference. Add as many roles as needed to fulfill the requirements of the Approval. Note this property is only displayed when the Approval includes clauses of type 'User'.|
|Observers||Configure a user or group to view a read-only version of an in-progress workflow as well as specify the communication template to use. For more information, refer to Observers.|
Updated 3 months ago