Automate transitions

Automate transitions

Using Orchestly, you can configure transitions to be executed automatically by setting a wait time or a condition.

Automate by time

Transitions can be configured to execute automatically after a specific time frame. 
  1. Navigate to     and select Automation from the left panel. 
  2. Select a blueprint you wish to automate. Learn how to create a blueprint. 
  3. Select a transition.
  4. Navigate to ‘ Who can perform this transition ?’ under the  Before section. 
  5. Select  Automate transition- By time from the dropdown. 
    • 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 time is 15 minutes. 


When a job reaches the Awaiting reply stage, it starts a timer for the mentioned time frame, after which the transition takes place automatically and the blueprint moves to the next stage.

Automate by condition

Transitions can be configured to execute automatically when the job meets a specific condition. 

  1. Navigate to     and select Automation from the left panel. 
  2. Select a blueprint you wish to automate.
  3. Select a transition.
  4. Navigate to ‘ Who can perform this transition? ’ under the  Before section. 
  5. Select  Automate transition -  By condition from the dropdown. 
  6. The default configurations under  Before  and  During  transition tabs will be overwritten.
  7. Click the  Set Condition  button.  
  8. Select condition : Jobs  that meet the selected condition will be automated.
  9. All jobs : All the jobs that pass through this transition will be automated.


When a job with the mentioned condition reaches the Resume   approved stage, the transition takes place automatically, and the blueprint moves to the next stage.  Learn more about stages and transitions. 


Note:

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

  • When a job 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.  Additionally, this transition will only be displayed in the job. 

  • When a job reaches the stage whose different transitions are automated by more than one condition (all of which match the job), 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. 


Business Scenarios

Wait states in transitions

In the food manufacturing industry, processed items need to be frozen or fermented for a specific time before they can be packaged. This wait time can be automated in Orchestly.



Here, the wait state can be configured to wait for a specific time until fermentation is complete. 

When a job reaches the wait state, it starts a timer with the configured time. Once the timer expires, the job moves to the next transition automatically. 

SLA in transitions

Automated transitions help you to set up escalations in a blueprint.

 

Here, an escalation is triggered when a job is delayed beyond the defined timeframe. 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 job fields, trigger webhooks, or associate custom functions. 



Reports are used to track the amount of jobs passing through the escalated transition. 

 

Routing different transitions

You can configure jobs to be automatically approved or rejected for specific conditions, or after a given timeframe. 



Here, when a vendor has a rating less than 1, you can configure the deal to be rejected automatically.

Reports are used to track the amount of jobs that pass through auto-select or auto-reject transition.