Using vtiger as a metadata layer on top of our business definitions and business dataWith this sentence we mean that we can use directly the workflow of modules, fields, relationships between entities in vtiger itself as if it was the common warehouse model.
MODULES AND BUSINESS PROCESSES
So from the very beginning of the year we can add this entity to our accounts and that’s adefinition of our own selling process to be used on vtiger.
For example i think another layer which is a quitation which is another module in a sense that is a specific detail of the potential and we define a quote which in turn will be transformed in a sales order.
At the end we will have the actual invoice sent to the client.
So you can see for example defining the Common Warehouse Metadata we can see the entire sales process as a staging of accounts-potentials-quotes adn invoices.
so will have an account and a telemarketing department will try to direct sell and we’ll have the SO and invoice module.
as wewe can see we defined a specific metadata layer which is composed on 3 modules
So vtiger use itself defines the what are our metadata and we are using our own business definitions and we are driving this concept using this layer just using o dont using any speficif other modules.
FLEXIBILITY IN ADDING ENTITIES
In this respect we can create even new modules (entities). Those can be created by a skilled vtiger programmer through the use of specific libraries. The power of this approach lies in the fact that firstly we can re-use modules (saving on programming) and most importantly the creation of these new modules (vtlib modules) dont “fork” the product, in the sense that they are treated as standard modules by the system.
These libraries can define also relations across entities. So we have another aspect of the use of vtiger in constructing a common warehouse model.
We think that this approach could be very flexible because vtiger can be modeled by an administrator user, without any progamming skills and we know that every company have their own business definitions and we can hardly define a standard set of measures and dimensions to give them as standard.
For example a very specific picklist can be created on the account module: the company of ours is a prospect, a client or a specific stage in our definition of our own customer base. So, since that any single company have their own business definitions in grouping and segmenting their own customers we can truly understand that is the entity itself used in vtiger is a metadata layer.
As a matter of fact the first important definition lies directly in the modularity of vtiger itself. So for example we can use the account module and you know that in vtiger we have custom modules. Defining processes through the use of existing modules. The second way bring to the use of new modules and at last we have the use of fields and custom fields created from the GUI itself.