Zoho Inventory

Blueprints

Blueprints are the online representation of a business process. In Zoho Inventory, you can use Blueprints to design a process flow using states and transitions. They guide your team through the workflow, validate essential information, and automate the business processes managed via Custom Modules. Let’s understand this better with the help of a scenario.

Scenario: Zylker uses Zoho Inventory. To keep track of the items requested by employees, Bailey, Zylker’s Chief Procurement Manager, uses the Custom Modules feature to create a Purchase Requests module. To set up an approval process for the requests raised by users, she uses the Blueprints feature in Custom Modules and designs a process flow for approval using States and Transitions. Now, whenever a user creates a purchase request, the Blueprints section is displayed on the request’s Details page, and users with access to execute the transitions (transition owners) can approve or reject the requests by clicking the respective transitions.

Note:

  • This feature is only available in certain plans of Zoho Inventory. Visit our pricing page to see if it is available in your plan.
  • This feature is currently in early access. Contact support@zohosupport.com to enable it for your organization.

Terms to Remember

Before you begin creating a blueprint, read the following terms and their definitions as they are key to understanding how the feature works.

Create a Blueprint

Creating a blueprint involves the following processes:

Enter Basic Information

Here’s how you can create a blueprint:

Note: You can only select fields of the dropdown data type from Blueprint Field. This is because, when a record enters a blueprint, only options from the dropdown field can be used to trigger the required transition.

Design the Blueprint’s Process Flow

Once you’ve created a blueprint, you can use the dropdown options to create a flowchart that represents your business process. Here’s how:

Pro Tip: When connecting states, ensure that it does not create a loop (a closed connection).

Configure SLA for a State

To trigger a Service Level Agreement (SLA) for a state:

Create a Transition

Before Transition

Define when the transition should be displayed on a record’s Details page and to which users and roles it should be shown.

Note: The transition will be completed if any one of the transition owners clicks the transition button.

During Transition

Provide the details required for the transition to occur.

Transition InputDescription
No InputThe blueprint can move to the next state without any mandatory fields to be filled or additional information to be provided.
Fields, Checklists & Messages- Fields: Add the fields in which the transition owners must fill in data. Click + Add Field to add more fields.
- Checklists: Create a checklist to help transition owners keep track of the tasks they need to complete. Click + Add Checklist to add more tasks to the checklist.
- Messages: Add a message to inform transition owners what they must do. Click + Add Message to add more messages.

After Transition

Specify what actions should be performed after the transition is executed. You can configure immediate or time-based actions.

Create a Sequential Transition

A Sequential Transition consists of multiple sub-transitions that must be executed one after the other in the order they were created. Let’s understand this better with the help of a scenario.

Scenario: Zylker uses the Custom Modules feature in Zoho Inventory to create a module called Purchase Requests, which tracks items requested by its employees for office use. Once a user creates a purchase request, it must be approved by the user’s lead, followed by the Procurement Manager, and finally the Chief Procurement Officer (CPO). To establish this approval flow, Bailey, the CPO of Zylker, creates a blueprint for the approval process. She sets up a Sequential Transition for the Submit for Approval and Approve states and creates a sub-transition for each approver, ensuring that the purchase request is approved only when all approvers have approved the request.

The above scenario is similar to the Multi-Level Approval feature in Zoho Inventory, where a transaction is approved only when all approvers in the approval hierarchy approve it.

To create a sequential transition:

Once you’ve created the required sub-transitions, the blueprint’s process flow with the sequential transition should look similar to the image below.

Create a Parallel Transition

A Parallel Transition consists of multiple sub-transitions that are executed simultaneously. Let’s understand this better with the help of a scenario.

Scenario: Zylker uses the Custom Modules feature in Zoho Inventory to create a module called Purchase Requests, which tracks items requested by its employees for office use. Once a user creates a purchase request, it must be approved by both the Procurement Manager and the Finance Manager. To establish this approval flow, Brandon, the Procurement Manager of Zylker, creates a blueprint for the approval process. He sets up a Parallel Transition for the Submit for Approval and Approve states and creates a sub-transition for both the managers, ensuring that the purchase request is simultaneously sent to both managers and is approved only when both have approved the request.

To create a parallel transition:

Once you’ve created the required sub-transitions, the blueprint’s process flow with the parallel transition should look similar to the image below.

Publish a Blueprint

A blueprint must be published to allow records to enter it. If you’ve saved a blueprint as draft, here’s how you can publish it:

Execute Blueprint

Prerequisite:

  • Only published blueprints can be executed. Learn how to publish a blueprint.
  • The transition button will be shown on a record’s Details page only when the user who created the record chooses the option that starts the process flow of the blueprint in the dropdown field selected as the Blueprint Field. For example, in the Purchase Requests module scenario, the transition buttons will be shown to transition owners only if the user creating the record selects the Submit for Approval option for the Approval field.

Here’s how transition owners can trigger a transition:

If the blueprint owner added any configurations in the During Transition section, transition owners need to do the following based on the configurations.

Transition InputDescription
Fields, Checklists & Messages
Note: The transition will not complete until the transition owners perform the actions specified by the blueprint owner for these inputs.

- Fields: Fill in information in the fields displayed.
- Checklists: Strike the options displayed to check them off.
- Messages: Read the message shared by the blueprint owner.

With this, the transition will be completed and the blueprint will move to the next state. Complete all the transitions to enable the record to exit the blueprint and complete your business process.

Other Actions for Blueprint

These are the other actions you can perform on a blueprint:

Edit a Blueprint

Here’s how you can edit a blueprint:

Note: You cannot update or delete a transition if a blueprint has been published. Create a Draft and then proceed with the required action.

Bulk Update Records

You can bulk update records to include or exlcude them in a blueprint. Before bulk updating records, ensure that they meet the blueprint’s criteria.

Here’s how you can bulk update records for blueprints:

Delete a Blueprint

To delete a blueprint:

Other Actions for Transitions and States

These are the other actions you can perform on a blueprint’s transition:

Edit a Transition or State

Here’s how you can edit a transition or state:

Note: If you create a draft of a published blueprint, you must publish the draft for the changes to take effect. Once published, the existing version will be replaced by the new draft.

Delete a Transition

Here’s how you can delete a transition:

Note: If you create a draft of a published blueprint, you must publish the draft for the changes to take effect. Once published, the existing version will be replaced by the new draft.

Remove State

If you don’t want to use a state in the process flow of your blueprint, you can remove it. The state will then be added to the Quick Add section on the left side of the page.

To remove a state from the process flow:

Note: If you create a draft of a published blueprint, you must publish the draft for the changes to take effect. Once published, the existing version will be replaced by the new draft.

TOP