Follows standard convention to store, retrieve, filter and establish relationships between other entity module records. Workflows, Reporting, sharing and profile access control is automatically enabled based on the assigned user of record.
Modules that bring functionality without necessarily binding to standard record conventions are named as extension modules. Usually they provide in-app specific functionality that works with user accessible entity module records. Access to records is possible through VTAP Runtime.
Example: Reports, Dashboard etc…
Allows embedding external applications or web-page inside CRM.
Module Designer offers IDE through which you can develop custom code for building functionality.
Through customizer IDE you will be able to create and customize the following
Comprises of one or more UI elements together providing specific functionality on the page.
Example: Menu, Oneview Widgets
Component names follow core product convention for runtime binding. The format of is as follows:
For example if you have a component with name "CustomButton" then component name will be Contacts_Component_CustomButton. For more details about the component and its structure click here.
Module where you are defining the component from.
Name of the component.
Comprises of one or more Components having custom client-side runtime behaviour.
Enables you to extend functionality of standard pages or components by subscribing to the event hooks and reacting to the triggers at runtime.
Enables you to customize the look & feel of client components or pages in the CRM.
To add custom scripts, pages and components you need to use VTAP Runtime object. It allows you to interact with Vtiger user interface and add custom behaviors. Learn more about it here.