No. | Description |
---|---|
1) Name | Give your workflow a name for easy identification. If you do not set a Slack Command (in field 5) for the workflow during initial creation, Rootly will hyphenate the Name field as the default command value. |
2) Description | Add a detailed description to inform users what the workflow does. |
3) Workflow Folder | Place the workflow in a specified folder. If a workflow is not in any folder, you will be able to find the workflow by filtering for All Workflow on the workflows page. |
4) Enabled | When a workflow is disabled, it will not automatically run when trigger conditions are met. Disabled workflows can still be triggered by manual Slack command. |
5) Slack Command | Every workflow can be triggered via Slack command. Choose an easy-to-remember command if your process calls for a workflow to be triggered in this fashion. If you do not set a value here, Rootly will hyphenate the Name field as the default command value. |
6) Command Feedback Enabled | Selecting this field will result in a message output in Slack every time the workflow is run via manual Slack command. |
7) Repeat Every | Each workflow can be run on a recurring schedule. This field must be used alongside the Repeat On field. The value set in this field indicates how often the workflow is initiated (e.g. 30min, 2h 30min, 1 day). The very first run of the workflow will initiate when the trigger events are met (field 10). However, subsequent runs will initiate once the repeat interval is reached - regardless of the trigger events. Recurring workflows will stop as soon as the run conditions (fields 11 & 12) are no longer true. |
8) Repeat On | This field must be used alongside the Repeat Every field. When a value is set for the Repeat Every field, use this field to select the days of the week on which the workflow will run repetitively. For example, if the following values are set: - Repeat Every = 5h - Repeat On = M, W, F The workflow will run repetitively every 5 hours on Mondays, Wednesdays, and Fridays. |
9) Wait Before Executing | Each workflow can be configured with a delay. The minimum delay that can be set is 10 seconds. Condition checks for workflows with delays will follow this pattern: - Condition Check: Pass → Delay → Condition Check: Pass → Run → End - Condition Check: Pass → Delay → Condition Check: Fail → End - Condition Check: Fail → End |
10) Trigger events | Trigger events determine when a workflow is initiated. Once initiated, the run conditions (fields 11 & 12) will be checked before executing any of the actions (fields 13). You can find the full list of trigger events on this page. |
11) Run condition operator | Once a workflow initiates, the platform will check for the run conditions. The run conditions must be met in order for the workflow to progress to the actions. Each run condition can be joined by the following operators: - all of - every condition must be true - any of - if any condition is true - none of - if every condition is false |
12) Run conditions | Run conditions are set based on incident, action item, retrospective, alert, or pulse parameters. The Workflow Type determines what parameters are available to condition off of. Run conditions must be met before a workflow can proceed to take any action. |
13) Actions | Workflow actions are what actually execute once the run conditions are met. Available actions are dependent on the applications that are integrated for the organization. |
all of
- every condition must be true
any of
- if any condition is true
none of
- if every condition is false
is
- true if the property is exactly a set value
is one of
- true if a single-select property is ANY of the set values
contains any of
- true if a multi-select property includes ANY of the set values
contains all of
- true if a multi-select property includes ALL of the set values
contains none of
- true if a multi-select property includes NONE of the set values
none of
- true if a single-select property is NONE of the set values
is set
- true if a field contains a value
is unset
- true if a field does NOT contain a value
No. | Description |
---|---|
1) All Workflows | You can quickly view all of the workflows in your organization. |
2) Folders | You can create folders to place your workflows in. Workflows are not impacted by which folder they are placed in. This is purely used for organization purposes. |
3) Enabled / Disabled | This is an easy way to enable/disable each workflow. You don’t have to click into the edit page for each workflow to do so. |
4) Expand / Collapse | Expanding the tile will show a summary of the workflow - giving you a quick way to view them without having to click into each workflow. |
5) Workflow Summary | It’s not always easy to recognize what a workflow is configured to do purely based on its name. When expanded, you’ll be able to see a summary of the workflow containing its trigger events, run conditions, and actions. |
6) Filter & Sort | To quickly locate workflows, you can filter and sort workflows. |