Multi-level prioritization of records with multiple Kanban views per module
Greetings Enterprise Support Community!
We are happy to announce the introduction of a new possibility within Zoho CRM - creating multiple Kanban Views within a single module (depending on your edition).
As you may already know, the Kanban View in Zoho CRM, is a card-based view that displays data in an organized manner for better comprehension. As of now, CRM only supports a single Kanban view per module. As a result, every time you need to view your records (with this view) with a different 'Categorize By' field within the same module, you will need to edit the existing view as per your requirement. This can prove to be quite tedious.
This situation will be eased with the launch of this new feature with which you will be able to use multiple fields in order to prioritize your records. Refer to the GIF below to get a better understanding of the same.
Now, why exactly would businesses have the need to create multiple Kanban views? It is to help streamline the user experience, making it more convenient and less laborious for users. And how is that? By making it possible for users (who utilise Kanban views) to prioritise customer data by different fields.
Let us look at some examples to understand this better.
As you may have seen in the GIF above, users can categorise the records in their Deals module based on multiple factors:
For instance, Deals by Contract Status.
A user at an events company wants to track their events by multiple statuses.
They can do so with the records'
Event Promotion Status
Logistics Status
Venue Booking Status
Take for instance, you create a Kanban view for the Accounts module, you fill in the necessary details as shown below (as is the case at present).
However, with the upcoming update, the Aggregate By field will no longer be mandatory.
You will be able to view your records based on the field you sort them by.
Working with your Kanban Views
Given that you will be able to create multiple views per module, you will also be able to manage and delete views based on your requirement. Managing views will mean that you will be able to reorder the Kanban views based on your individual preference; and edit or delete them as well.
2. Expand and Collapse your stages
You will now be able to expand and collapse each stage within your view. Besides, you will also be able to drag and drop cards to collapsed stages.
A button to create stage specific records will also be provided on the footer of each stage. The current view's layout/pipeline and stage detail will be populated in the record creation page.
Now, why exactly would businesses have the need to create multiple Kanban views? It is to help streamline the user experience, making it more convenient and less laborious for users. And how is that? By making it possible for users (who utilise Kanban views) to prioritise customer data by different fields.
Let us look at some examples to understand this better.
As you may have seen in the GIF above, users can categorise the records in their Deals module based on multiple factors:
For instance, Deals by Contract Status.
A user at an events company wants to track their events by multiple statuses.
They can do so with the records'
Event Promotion Status
Logistics Status
Venue Booking Status
Take for instance, you create a Kanban view for the Accounts module, you fill in the necessary details as shown below (as is the case at present).
However, with the upcoming update, the Aggregate By field will no longer be mandatory.
You will be able to view your records based on the field you sort them by.
Working with your Kanban Views
Given that you will be able to create multiple views per module, you will also be able to manage and delete views based on your requirement. Managing views will mean that you will be able to reorder the Kanban views based on your individual preference; and edit or delete them as well.
Note.Manage Permission will be provided to restrict a profile from Creating/Deleting or Modifying a Kanban View.Re-ordering is user specific. If User A reorders their list views as 1-2-3, it will not affect User B's view. They will be able to re-order it to 2-1-3.To identify who created/modified the view and when it was modified, you can hover over the view.
2. Expand and Collapse your stages
You will now be able to expand and collapse each stage within your view. Besides, you will also be able to drag and drop cards to collapsed stages.
A button to create stage specific records will also be provided on the footer of each stage. The current view's layout/pipeline and stage detail will be populated in the record creation page.
- Only me
- Everyone
- Selected users
Note.If you have territories within your organisation, territories with subordinates will be displayed in the drop down.You will be able to create a Kanban View with picklists containing over 75 options. However, the system will throw an alert stating that only the initial 75 options of the picklist will be categorized.
Copy Customisation of the Multiple Kanban View will also be supported.