Runtime Policies are rules of automation that you can set up to trigger actions (create, update, move, send notifications, invoke web service) when certain events occur. They are working on the: "If this then that" principle.
In Kanbanize, the runtime policies can be divided into five groups depending on the type of event that triggers the execution of the policy:
1. Policy execution triggered by "special events"
As a "special event" can be considered an action such as card creation or blocking/unblocking of cards.
The runtime policies triggered by special events are as follows:
2. Policy execution triggered by card movement
In this group comes the runtime policies that trigger an action when a card is moved to a different position:
When a card is moved to a different position, an action will be triggered (create card or subtasks, update the card details, etc.).
- Card is moved
- Child card is moved
- All children are moved
- Mirror card is moved
- Relative card is moved
3. Policy execution triggered by card update
When a card property is changed (e.g. priority, color, etc.), an action will be triggered (create cards or subtasks, move the updated card; send a notification, etc.)
4. Policy execution is time-based
With this runtime policies, you can set up a time-related rule (e.g. "when the deadline of a card is in 1 day") that will trigger an action only when the condition is fulfilled. This policy allows to set up a schedule and automatically create/update cards at a given time.
The runtime policies in this group are as follows:
- Time-based policy (deadline is in "x" days or the cycle time is greater than "x" days, etc.)
- Recurring create cards (every day, every workday, every week/month, etc.)
- Recurring update cards (every day, every workday, every week/month, etc.)
5. Policy execution is board-related
These runtime policies are related to your board structure and your workflow. If you have set WIP limits for your board, you can automatically trigger an action whenever the WIP limit is reached/exceeded.