As the stages are stored in the single system field, the stages created in one blueprint can be reused on other blueprints of the same form. A stage can be deleted only if it isn’t used in other blueprints.
When the last blueprint in an application is deleted then you will be given an option to retain the stages. When this option is chosen then the stage values will be stored in the blueprint field. Later if these stage values can also be deleted by navigating to the associated blueprints section in the form builder. Learn more
Note: To accommodate more blueprint variables, we are bringing in a few changes to its format. These updates to Blueprint attributes are being rolled out to users in a phased manner. Previously, the current blueprint stage can be accessed through input.Blueprint_stages in your scripts. After the migration, such instances will be changed to input.Blueprint.Current_Stage automatically. Additionally, two more attributes will be available to access the name and status of the blueprint. These can be accessed from input.Blueprint.Name and input.Blueprint.Status.
When you import a .DS file that contains instances of input.Blueprint_stages, an error (Field 'Blueprint_Stage' does not exist in form) will be thrown. We recommend changing Blueprint_stages to Blueprint.Current_Stage while importing an old .DS file.
Refer to Blueprint Attributes help document to learn more.
Learn how to use the best tools for sales force automation and better customer engagement from Zoho's implementation specialists.
If you'd like a personalized walk-through of our data preparation tool, please request a demo and we'll be happy to show you how to get the best out of Zoho DataPrep.
You are currently viewing the help pages of Qntrl’s earlier version. Click here to view our latest version—Qntrl 3.0's help articles.