Open Shift Automation
Open Shift Automation (OSA) is an automated engine that fills open shifts through a configurable flow of actions. It evaluates eligible shifts and processes them according to the configured flow and schedule.
OSA replaces the repetitive tasks that schedulers perform when they manually post, offer, repost, and eventually close shifts that remain unfilled. You can scope each flow to one or more team-job pairs, and each pair can optionally include the team's sub-teams and the job's associated child jobs. You can use different automation strategies for different teams, and a single flow can automate tasks across multiple teams and jobs.
Open Shift Automation page
The Open Shift Automation page displays enabled and disabled automation flows whose effective dates fall within the selected date range. You can access it in the Admin Portal and Self Service Portal by navigating to .
From this page, you can create, view, edit, and manage automation flows. It is divided into several areas that provide access to flow details, configuration settings, and management actions.
This table lists and describes the areas of the Open Shift Automation page:
| Area | Description |
|---|---|
| Flow list |
Displays all available automation flows whose dates fall within the selected date range. The pane also displays the total flow count. For each flow, you can view this information:
Note: If a flow includes multiple team and job assignments, the Team and Job fields display the assigned values as comma-separated lists.
You can sort the flow list by Name, Team, or Job in ascending (A–Z) or descending (Z–A) order using the Sort icon and adjust the date range to view flows available during a different period. |
| Flow details |
Displays the selected flow's configuration details in the right pane. You can also use the Version Selector button on the Flow steps tab to view previously saved versions of a flow's steps and review how they were configured. Each version shows the date, time, and user who saved it, ordered from newest to oldest. Clicking Edit opens the flow form where changes can be made to the flow's configuration. Clicking Duplicate creates a copy of the flow and its entire configuration. The duplicated flow is assigned a new name and is created in a disabled state by default. The Flow parameters tab displays the general information and settings for the selected flow. Use this tab to define the flow's scope and applicability, including its active date range and the team and job assignments to which it applies. The Flow steps tab displays the automation steps that define how the system processes open shifts. The Shifts tab lists all shifts being processed by the flow, showing each shift's label, date, assigned employee, status, current step and step type, and when it was last updated. You can use the filter bar to narrow the list by Requires action, Step, Level, and Above level. The Logs tab displays a paginated audit history of all automation activity for the selected flow. You can use the scope filter to switch between two views:
|
| Filter | Opens the Filter panel, where you can limit the flow list by Team and Job. You can also select whether to include subteams in the results. |
| Refresh | Reloads the flow list and updates the page with the latest available flow data. |
| Create flow | Opens the flow creation page, where you can define and configure a new OSA flow. |
| Ellipsis icon | Opens a menu that provides access to additional application settings, including Versions, Modes, and Colors. |
How OSA runs
OSA runs as a scheduled task. During each run, it:
- Verifies that OSA is active.
- Determines the scope of processing based on the configured task parameters.
- Loads eligible flows.
- Identifies open shifts that match the configured team and job criteria.
- Processes each shift according to the configured flow.
OSA processes only open shifts that meet the configured eligibility criteria, including team and job requirements and the flow's applicable date range.
Task parameters
To define the scope of how OSA runs, it reads its parameters to determine what to process. There are four:
- Apply To Teams
- Apply To Subteams
- Apply To Team Flows
- Apply To Flow Steps