Hello everyone!
We are very happy to present to you, the following enhancements in Zoho CRM's Blueprint.
#1 Save a Blueprint as a draft
It so happens that sometimes you are not ready to deploy your final Blueprint into CRM yet, and you need to put some more thought into the process flow. When you publish a Blueprint, you will begin having records entering it - so it's not a good idea to deploy it before it's ready. To help you with this, we have come up with an enhancement in which you can save a Blueprint as a DRAFT.
You can play around with your States and Transitions in the DRAFT version, and once you are satisfied with the final process flow, you can PUBLISH your draft. Note that the draft version is not a testing environment, rather a canvas of sorts, for you to test your process flow. You cannot test the execution of a Blueprint with the draft version - for now, it's only meant for you to play around with the process flow. At a given point in time, you can have one "Published" version and one "Draft" version of a Blueprint.
-
Published version:
If a Blueprint is published, it means that it is live in your CRM setup. Records meeting the Blueprint criteria will begin following this version of the process flow.
- Draft version: If a Blueprint is saved as a draft, it means that it is not yet deployed in the live CRM setup, but available for you to experiment, without affecting any existing records.
The moment you edit a Blueprint, you can either publish the changes directly or save the latest version as a draft. You can toggle between the Draft and Published versions in the Blueprint Editor.
#2 Introducing a unified version for Blueprints
Records in Zoho CRM will now follow a uniform version of a Blueprint, at a given point in time. Earlier, whenever you edited a Blueprint, the latest version would be applicable only on newer records. Records already part of the previous version would continue to follow the previous flow only. This setup was rather problematic, in the sense, that different records of the same module might be following different versions of a Blueprint, depending on when they were created. Not anymore!
Now whenever you edit a Blueprint, you will be given two options: to either move existing records to the latest version or take the records out of the process altogether. This way, you can ensure that all records in a module follow the latest version of your Blueprint.
Check out these enhancements right away and get back to us if you have any questions!
For further details on the update, please visit this Help doc.
Regards
Vaagdevi Ravishankar