Automate by time

1. Navigate to   and select  Orchestration from the menu. 
   
2. Click on an existing orchestration or create a new one. Learn how to create an orchestration. 
   
3. Navigate to Step 2: Design Blueprint.
   
4. Select a blueprint you wish to automate and click on a transition. 
   
5. In ‘ Who can perform this transition ?’ dropdown under Before section in the right panel, select  Automated by time.
   
• The default configurations under the  Before and  During transition tabs will be overwritten.
  
6. Enter a time frame in the  Wait for field. The time frame can be between minutes, hours, days, or weeks.
   
• The minimum wait time is 15 minutes.  
  

Automate by condition

1. Navigate to    and select  Orchestration  from the menu. 
   
2. Click on an existing orchestration or create a new one. 
   
3. Navigate to Step 2:  Design Blueprint. 
   
4. Select a blueprint you wish to automate and click on a transition. 
   
5. In ‘ Who can perform this transition  ?’ dropdown under Before section in the right panel, select  Automated by condition.
   
1. The default configurations under  Before  and  During  transition tabs will be overwritten.
   
6. Click the  Set Condition  button. Configure a condition using the following options:
   
1. Select condition: Cards that meet the selected condition will be automated.
   
2. All Cards: All the cards that pass through this transition will be automated. 
   

Note:

• When a card reaches the stage  whose different transitions are automated by time and condition (which matches with the card), a higher preference is given to the transition automated by condition.   
  

• When a card reaches the stage whose different transitions are automated by more than one timer, a higher preference is given to the transition that was created first.  A dditionally , this transition will only be displayed in the card. 
  

• When a card reaches the stage whose different transitions are automated by more than one condition (all of which match the card), a higher preference is given to the transition that was created first.  
  

• If the blueprint’s flowchart contains a loop of transitions that are automated, and if the automated timer and condition is true every time, the loop cycle is restricted to  ten times.  
  

• Only 6 automated transitions are allowed from a stage.                           

• If an auto-transition is in progress and a user has permission to view/access the card, the user will be able to view the card under All Cards view. 

Business Scenarios

Wait states in transitions 

SLA in transitions

 

Here, an escalation is triggered when a card is delayed beyond the defined time frame.  Different levels of escalation can be triggered in every blueprint. 

The actions to be performed after the escalation are captured in the  After section of the transition. You can send emails, update card fields, trigger webhooks, or associate custom functions. 

Routing different transitions

Additional Reading : Learn how to automate decision-making in workflows using Qntrl.