Components and Packaging in Zoho Vertical Studio
Components are fundamental building blocks of Vertical Studio applications, comprising functionalities, configurations, and customizations. These components, such as fields, modules, blueprints, widgets, and templates, work together to create a complete and functional application.
Component properties define a component's characteristics including its behaviour, appearance, and functionality. Examples of Component properties include a Field's Label, Tool-tip, Worflow's name, description, actions, etc.
Packaged Components
Packaged Components refers to the components that are developed, published, and distributed to the subscribers by the developer. These components are deployed either during sign-up or as part of an upgrade.
For example, consider a custom module designed for managing client contracts, created in the developer console and published. When the subscriber accesses it, the module's behavior, including customization options and permissions for editing or removal, adheres to the established packaging guidelines.
Packaging allows developers to distribute these components collectively by publishing them as an application. This process ensures that each component in the subscriber's account adheres to the predefined rules for editing and removal. Detailed guidelines on managing these components are outlined in the next section.
Managing Packaged Components
To gain a deeper understanding of how the packaged components can be managed at the developer console and at the subscriber accounts, it is important to understand the key concepts of upgrade types and modify access. These terms clarify how components behave during upgrades and who can modify them post-deployment.
1. Upgrade Type
Upgrade Type defines whether the changes made by the developer to the packaged components will be deployed during an upgrade in the subscriber's accounts or not. Upgrade type can be of two types:
a. Upgradable:
Changes to the packaged components are automatically included in the next version of the application. These updates are deployed to the subscriber org(s) during sign-ups or version upgrades.
b. Non-upgradable:
Changes are included in the upgraded version of the application and are only applied to new sign-ups. Existing subscribers do not receive these updates during an upgrade.
2. Modify Access
Modify Access defines who can modify the specific properties of packaged components or delete them after they have been published and made available to the subscribers.
a. Non-Editable:
Non-Editable properties are locked once saved or published and deployed to subscriber accounts, preventing any changes by both the developer and the subscriber. This restriction is applied specifically to the properties of the component, not the component itself. For instance, the 'Formula Return Type' in a formula field is a non-editable property, meaning it cannot be modified after it has been set and deployed.
b. Developer Only:
Only the developer can modify the properties of the packaged components, while subscribers cannot make changes. This ensures that the developer maintains control over the component's properties.
c. Developer and Subscriber Editable:
Both the developer and the subscriber can edit the component properties. However, changes made by the developer will only be included in new versions for new sign-ups and not retroactively applied to existing subscriber accounts. This will liberalize the ownership of the component, allowing both the developer and the subscriber to modify it as per their respective needs.
Altogether, every packaged component by itself, and its respective properties, will have a defined upgrade type and modify access.
Destructive Changes
Any modifications, deletions, or updates pushed as upgrades to the subscriber accounts that may have permanent and irreversible effects on your subscriber data or configurations are classified as Destructive Changes.
Please be aware of the potential consequences of any destructive changes performed by a developer before proceeding:
- Data and Configuration Loss: Deleted or modified subscriber data or configurations cannot be recovered once the upgrade is deployed.
- Operational Disruption: Changes may impact critical processes in the subscriber's organization, including workflows, customer interactions, billing, and reporting.
- Compliance Risks: Altering or deleting certain data or configurations could lead to non-compliance with regulatory or contractual data retention requirements.
We recommend the following precautions when performing such actions:
- Thoroughly review all changes with utmost care to prevent unintended data or configuration loss.
- Test changes before deploying to the subscriber's production environment.
- Communicate the changes to the subscribers well in advance so that they will be prepared for any potential impacts.
Access your files securely from anywhere
Zoho CRM Training Programs
Learn how to use the best tools for sales force automation and better customer engagement from Zoho's implementation specialists.
Zoho DataPrep Personalized Demo
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.
- Zoho Workerly Home
- Forums
- Connect With Us:
- Zoho Recruit Home
- Forums
- Connect With Us:
New to Zoho Writer?
Create. Review. Publish.
New to Zoho CRM Plus?
Deliver unforgettable customer experiences
New to Zoho CRM Plus?
Deliver unforgettable customer experiences
New to Zoho Marketing Plus?
Everything you need to run your marketing
New to Zoho Marketing Plus?
Everything you need to run your marketing
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.
New to Zoho Survey?
Zoho Sheet Resources
Zoho Forms Resources
New to Zoho Sign?
Zoho Sign Resources
Sign, Paperless!
New to Zoho TeamInbox?
Zoho TeamInbox Resources
New to Zoho ZeptoMail?
Design. Discuss. Deliver.
New to Zoho Workerly?
New to Zoho Recruit?
New to Zoho CRM?
New to Zoho Projects?
New to Zoho Sprints?
New to Zoho Assist?
New to Bigin?
Related Articles
Zoho Vertical Studio - Overview
Zoho Vertical Studio is a robust low-code platform designed to help developers and businesses create, customize, and deliver SaaS applications tailored to the unique needs of specific industries. By offering an extensive suite of pre-built tools, ...Layouts
Layouts in Zoho Vertical Studio are versatile interfaces that help businesses to structure their data to fit specific requirements. The key advantage of using layouts is that you can streamline the data management by ensuring that users interact only ...Layout Rules
Layout rules offer a powerful way to dynamically change the behavior of fields, sections and subforms in real-time based on the values provided by the user. This helps in streamlining the data entry and enhance user experience by ensuring only ...Vertical Studio - Zoho Analytics integration
The Advanced Analytics for Vertical Studio applications, powered by Zoho Analytics, offers a flexible solution for transforming raw operational data into actionable business intelligence. This powerful integration between the Vertical Studio ...Workflow Rules in Vertical Studio
Workflow Rules automate actions such as sending email notifications, assigning tasks, and updating record fields based on specified conditions. This feature simplifies processes by automating tasks when certain criteria are met. Key Components of a ...
New to Zoho LandingPage?
Zoho LandingPage Resources