Welcome to Portal

?Unknown\pull-down

Welcome to Zoho Cares

Bienvenido a Soporte de Zoho

Search our knowledge base, ask the community or submit a request.

Automate transitions

Using Qntrl, 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  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.  



In the above example, when a card reaches the  Awaiting reply stage, it starts a timer for the mentioned time frame of 4 weeks. After 4 weeks, 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 card meets a specific 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. 



In the above example, when a card with the mentioned condition reaches the Resume   approved stage, the transition takes place automatically, and the blueprint moves to the next stage.  

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 

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 Qntrl.



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

When a card reaches the  wait   state , it starts a timer with the configured time . Once the timer expires, the card 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 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. 



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



Routing different transitions

You can configure cards to be automatically approved or rejected for specific conditions , or after a given time frame. 



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 cards that pass through  auto - select or  auto - reject transition.


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

Helpful?40
Updated: 3 years ago
Share :
Follow

Subscribe to receive notifications from this article.