Resetting planning boards
Reset team and data planning boards by moving tasks to the holding area, excluding protected shift types.
Overview
Planners prepare a board by first clearing it per team and day. This automation moves all tasks to the holding area, except for shift types on a protected list, and logs the result for each team and day.
What has changed
- Planners prepare boards faster
- The same teams and days are cleared in the same way
- Fewer manual errors
At a glance
In één oogopslag
Overzicht
Planners prepare a board by first clearing it per team and day. This automation moves all tasks to the holding area, except for shift types on a protected list, and logs the result for each team and day.
Wat er verandert
- Planners prepare boards faster
- The same teams and days are cleared in the same way
- Fewer manual errors
How it works.
What it does per team and day
- Logs into ONS and calculates the date range
- Loads the list of teams
- Opens the planning board per team and day
- Moves all tasks to the holding area
- Skips shift types on the exclusion list
- Logs the result per team and day
Rules
For each team and day, all tasks are moved to the holding area, except for those in shift types on a protected list. Because the logic is fixed, the same input always yields the same result, and every run is logged.
Check out other automations.
Frequently asked questions.
No. The digital colleague works in the screens and systems your team already uses, whether they are legacy applications without an API or modern ones, so there is nothing to replace.
Yarado builds it, runs it and monitors it. When a screen or a system changes, we adjust the automation, so your team needs no developer or automation skills of its own.
Yes. Every run is recorded in the Yarado portal, where you can see which processes ran, when they last ran, what they produced and what went wrong. Depending on the automation, the processing log is also emailed to the team that needs it.
Yarado monitors every run and is alerted automatically when one fails, so a problem is picked up on our side. Cases that need a person are reported to your team with the reason, in the portal or by email.
Yes. Automations are built around your own steps and systems, and this page is just one example of what is possible. A first automation is typically live in weeks, not months.