Sample Use Case

Setting up a Blueprint 

Process Flow

Steps

• Associating a form - Blueprints are associated with a form. Stages and transitions in a blueprint are displayed for the records of a selected form. For example, when employees apply for leave, they submit a record using a form. The record will contain blueprint transitions like Approve Leave and Reject Leave, and stages like Leave Approved or Leave Rejected.
  
  Select a form from the drop-down.
  

• Naming the blueprint
  

• Defining a condition - Blueprints can be triggered based on conditions. For example, let's say a blueprint should be enabled only when the received request is of type "New Feature Request", so that the development process of the feature can be tracked.
  
  Define a condition as displayed below:
  
  Note: Setting a condition is not mandatory, and can be skipped when blueprint should be enabled for all records.
  
  

Note: Stages can be renamed or deleted by clicking on them.

Click on the + icon to a dd a transition between the stages:

• Transitions contain two parts, Before Actions and After Actions. Before Actions are to configure who can view the transition, under what criteria to display the transition, any relevant tooltips, and confirmation messages. After Actions consist of actions to be executed after the transition is triggered. The actions available are Notification, Data access, Integrations, and Deluge script.
  
  Set the following Before Actions :
• Transition Owners - To configure who can view and perform the transitions.
  

  
  

  Select the required option underTransition Owners.

  

  
  

  Note: Users can be selected based on email addresses, Permissions, and User fields.

  
  
• Criteria - To display transition buttons for records that meet a specific criteria.
  For example, the Assign Developer transition should be enabled only when the Developer field is not null, i.e., after a developer has been assigned.

  

  
  

  Note: Setting criteria is not mandatory, and can be skipped when transitions should be enabled for all records.

  
  
• Transition Properties - This is used to configure tooltips and a confirmation message. Tooltips appear when the mouse is hovered over the transition, and confirmation messages are displayed when the transition button is clicked.
  
  

  Check the Display tooltip box and enter the tooltip text.

  

  
  

  Check the Require confirmation before execution box to configure the confirmation action in the popup that appears.
  

  

After Transition actions are used to configure workflows that are triggered when the transition button is clicked. For example, we can use the send mail task to send an automated email notification to customers when their requests are approved.

Click on Add New Action under the After header gives options to configure various workflow actions:


The following image shows the various workflow actions that can be configured:

• Transitions can further be categorized into Common and Parallel.
  
  Configure Common Transition : Common transitions can be accessed from multiple stages in a blueprint. For example, consider online order management where the customer can cancel the order at anytime, so the cancel order transition will be available across all the stages. Or think about the On Hold transition, which should be available at all stages of the development lifecycle.
  
  Click the highlighted icon next to the transition and toggle ON Common Transition.
  
  
  Once a transition is marked as a common transition it will appear for all the blueprint stages by default. This helps when we want a particular transition to be enabled for all the blueprint stages without having to create the transition manually for each stage.
  
  
  Configure Parallel Transition : When multiple transitions are required to move from one stage to another, then it's known as a parallel transition. For example, hostel fees, college fees, and book fees must all be paid before the record can be marked as "fee paid".
  
  Click the highlighted icon next to the transition and toggle ON Parallel Transition.
  
  
  Once a transition is marked as a parallel transition, we can add additional transitions between the same blueprint stage. The + icon is used to configure the additional transitions.
  

Step 5: Click Save Blueprint.

Tutorial