Workflow step types
Select from a variety of workflow step types to build workflows from.
Model Stage Change
- Transitions a model into another stage.
- Requires available model stages associated with the workflow.1
| Field | Description |
|---|---|
| when these conditions are met (optional) | Add conditional requirements to qualify for this step.2 |
| set model stage to | Select the model stage to transition to. |
Workflow State Change
Transitions the workflow into another workflow state.3
| Field | Description |
|---|---|
| set workflow state to | Select or add4 the workflow state to transition the workflow to. |
| progress | Indicate the progress of the workflow at this transition into the next state. |
4 Click Add New State to create a new state unique to this workflow.
User Action v2
Creates a button that performs an action on behalf of the user.
| Field | Description |
|---|---|
| display action button when (optional) | Add conditional requirements for displaying this step.5 |
| action button label | Text that displays on your action button. |
| request fields (optional) | Include required inventory fields alongside your action.6 |
| user action deadline (optional) | Include a deadline for when users should complete this action by.7 |
| optional fields (optional) | Include optional inventory fields alongside your action.8 |
- 6
- Select the field, then click Add Field to insert.
- Manage model inventory fields
Users must have write permissions for the field in order to enter values.
7 Toggle Enable deadline on to configure a deadline.
- 8
- Select the field, then click Add Field to insert.
- Manage model inventory fields
Users must have write permissions for the field in order to enter values.
Approval
Display a preconfigured message to users in the selected approval group.
- Select from either User Roles, Model Stakeholder Types, or either User Role or User Type inventory field.9
- Must be connected to both a rejection and approval Model Stage Change step.10
- Configure two Model Stage Change steps for your associated rejection and approval stages.
- Then, from the bottom of your Approval step:
- Connect the left (red) to your rejection step.
- Connect the right (green) to your approval step.
| Field | Description |
|---|---|
| approval group | Select the roles, stakeholders, or user fields responsible for approval. |
| fields to review (optional) | Select the model inventory fields shown to approvers for read-only review. |
| Approval Message | When your workflow reaches this Approval step, the selected approval group is shown this message.11 |
11 Enter in a title and a message to display.
Broadcast
- Send email notifications to users in selected groups.
- Select from either User Roles or Model Stakeholder Types.12
| Field | Description |
|---|---|
| Select roles | Select the Model Stakeholder Types or User Roles to receive the email. |
| subject | Enter the subject of the email. |
| message | Enter the body of the email.13 |
13 Use the rich text editor to compose your message:
- Include optional details about the model the workflow is running on using the { } Insert Variable drop-down.
- Click on the Preview tab and choose a model under select model for preview to confirm how the notification will appear when rendered.
Condition Branch
- Allows diverging paths based on conditional requirements.
- A
defaultbranch will be automatically included as a catch-allelsepath to ensure that your conditional logic is complete.
Workflows cannot be saved until condition branches are connected to other steps.
To configure a condition branch:
On the Configure Condition Branch modal, click Add Branch.
Enter in the path name and designate the conditions14 that apply to this path.
Continue with steps 1 and 2 until your conditional branch logic is complete.
To remove a path, click and select Remove Path.
When you are finished setting up all your branch paths, click Update Step to save your step.
Proceed with linking the Condition Branch with your subsequent steps.15
Wait
- Creates a time condition for displaying next available action.16
- Used to enforce a time delay or a calendar date milestone.
To configure a wait step, select when you would like to resume workflow
| Option | Required field(s) | Description |
|---|---|---|
| After Time Interval | wait duration | Wait for a set amount of time. Applies to all models under the workflow. |
| At Specified Date | wait until | Wait until a specific timestamp. Applies to all models under the workflow. If the milestone date inputted is in the past, the next workflow step will display immediately. |
| At Specified Date on Model Field | model field17 | Wait until a specific timestamp as defined by a model inventory field on a per model basis. If the selected field is empty18 or the milestone date inputted is in the past, the next workflow step will display immediately. |
| Time Delta from Specified Date on Model Field | model field, time delta direction, wait duration | Wait for a calculated time relative to a date in a model field on a per model basis. If the selected field is empty19 or the milestone date inputted is in the past, the next workflow step will display immediately. |
18 Make model inventory fields required when creating models to ensure necessary fields have valid values.
19 Make model inventory fields required when creating models to ensure necessary fields have valid values.
Run Workflow
Triggers another workflow indicated by select workflow to run, allowing you to chain workflows.
Webhook
When a workflow reaches a webhook step, the workflow will pause. Listen for a POST request to resume the workflow:
Click Copy to the right of URL to copy the webhook URL to your clipboard.
This webhook URL is where you should send your
POSTrequest.
Under select target model for payload, choose a model from your inventory20 to populate the target for the payload.
Click Copy to the right of Payload to copy the payload to your clipboard.
Include this payload when you send your
POSTrequest to the webhook URL.
Click to the right of the
x-api-keyand its value to copy them to your clipboard.Click to the right of the
x-api-secretand its value to copy them to your clipboard.
Send your POST request to the webhook URL and include these headers with your request to authenticate your call.
HTTP Request
Sends a HTTP request with optional additional conditions.21
| Field | Description |
|---|---|
| url | Enter in the URL to send the HTTP request to. |
| method | Select the HTTP request method: GET, POST, PUT, DELETE22 |
| timeout (seconds) | Enter in a request timeout in seconds.23 |
| fail on non-2xx (optional) | Toggle whether or not the request will be considered failed if the response status code is not in the 2xx range. |
| allow invalid certificates (optional) | Toggle whether or not the request will be allowed to use invalid certificates. |
| follow redirects (optional) | Toggle whether or not the request will follow redirects. |
| require https (optional) | Toggle whether or not the request will require HTTPS. |
| headers (optional) | Include headers with your request.24 |
22 PUT and POST requests have additional configuration fields:
- body type — Select whether the body is
JSONorText. - body — Enter in your payload.
23 Max 300 seconds, or enter 0 to disable timeout.
- 24
- Click Add Header to enter a header.
- Provide a Header Name and Header Value.
End
- Designates the end of your workflow.
- Use this step when all of your other steps have been configured and linked together.25