This shows you the differences between two versions of the page.
Both sides previous revision Previous revision | |||
wmanager:customize_data_model [2018/04/18 15:20] Gianluca Pelliccioli removed |
— (current) | ||
---|---|---|---|
Line 1: | Line 1: | ||
- | ==== CUSTOMISE DATA MODELS ==== | ||
- | |||
- | WManager is build in such way that the user can easily customise data models. | ||
- | |||
- | WManager Business Data Model is shown below | ||
- | |||
- | {{: | ||
- | |||
- | Business data model is mainly depends on five tables. | ||
- | * **Product** | ||
- | * **Contract** | ||
- | * **Assets** | ||
- | * **BE** | ||
- | * **Accounts** | ||
- | |||
- | * Product table manages the different type of item of the organisation. | ||
- | * Account table manages all the customer information. | ||
- | * Contract table manages the agreement between the customer and organisation for the product. | ||
- | * Assets table is connected with be table that manages the business entity for the product, which the customer have signed the contract. | ||
- | |||
- | |||
- | ---- | ||
- | |||
- | |||
- | {{: | ||
- | |||
- | For customising the data model as shown in the above figure, catalogue table is added to the model. Catalogue table should connect to assets table through which we can manage business entity and contract between the customer and organisation for the particular item. | ||
- | |||
- | Catalogue is the type of assets which we have connected to assets table. We can manage different items through the single WManager instance, just we need to create the new items table and we should have a reference in the assets table which will manage the business entity. | ||
- | |||
- | |||