With Dependent Fields and Blocks, you can define dynamic business rules at the field level. They are activated only when the configured condition is satisfied. Additionally, you can set rules to mark a field as mandatory or read-only.
For example, you can define a condition where the Location field must be revealed only when you fill out the Phone Number field in a record.
Watch a video to understand the working clearly.
Dependent Fields and Blocks is supported only in the following screens:
In this section, you will learn about the functionality of Dependent Fields and Blocks in Vtiger CRM. But before you dive into the working of this setting, it is essential that you complete these prerequisites:
We will explain the functionality in a bottom-up approach with the following diagram:
Consider this example.
A customer sells insurance with Product A and Product B. He has 120 custom fields for Product A and 120 custom fields for Product B. The customer’s requirement is straightforward. They don’t want Product B’s fields to be visible while working on Product A and vice-versa.
Here is the solution.
With the help of Dependent Fields and Blocks, we can achieve the above requirement. When the customer selects Product A from a Picklist or Checkbox field, the fields related only to Product A are shown, and when he selects Product B, the fields related only to Product B are shown.
Once you understand the functionality, configuring the dependency is quite an easy task. We have divided the entire process into four steps for better understanding. Read on...
This is the primary step in using which you can go to the Dependent Fields and Blocks screen.
You can add both block dependency and field dependency here.
If you choose a block dependency, you can add multiple child field dependencies under it. You cannot do the same for a field dependency.
Once you decide on the dependent blocks and fields, you must specify the user’s action on the field.
Once you add the access rules, you must mention the trigger field and its value. The trigger is a condition that must be satisfied for the dependent fields/blocks to be shown.
You can edit or delete an existing dependency by hovering over the dependency.
Handy Hint: If you see a icon in the List View, it represents that the field is not shown due to a dependency rule.
Here are a few limitations that you must be aware of: