Open Case

Wattyo Support

leaf

leaf

Man illustration

Flower illustration

Updated on March 7, 2025

Data Model

Estimated reading: 3 minutes 5 views

Entity Relationship Diagram

mermaid ERD

Data Model

ADD DIAGRAM

Object	Description	Example
Catalog	It representes a Product Catalog which holds a collection of Catalog Section along with its related Product	A Water Supply services Catalog
Catalog Section	It’s a logical way to organize the Catalog into different group of products to make it easier for the user to locate the different available products.	DOMESTIC SUPPLY SERVICES
Product Section Assignment	It’s used to assign a product to a specific Product Catalog	WATER PLUS assigned to DOMESTIC SUPPLY SERVICES section
[ Products ]({{< relref “./administration/products/” >}})	It groups all the configuration functionalities listed below and the core/basic product properties.	A Product named ‘Water Supply’ with code ‘WAT’
[ Eligibility Rules ]({{< relref “./administration/products/eligibilityRules” >}})	It defines when this product is available for selection or not.	Only show the product for Customers with Type = VIP
[ Compatibility Rules ]({{< relref “./administration/products/compatibilityRules” >}})	It determines if a product can coexist with any other in the same Order/Order Item/Account	Flood Insurance requires Water Supply service
[ Product Version ]({{< relref “./administration/products/productVersions” >}})	The different definition snapshots for a product.	Version 1 can have one Attribute and be inactive, and Version 2 can have two Attributes and be active.
[ Product Version / Attributes ]({{< relref “./administration/products/productVersions/attributes” >}})	The different property / fields that would be available for setup when configuring a Product.	A Height attribute of type Number. A Comments attribute of type text. A Brand attribute of type Picklist.
Product Attribute Assigment	It relates an Attribute with a Product Version	Attribute TYPE is assigned to INSURANCE product version v1
[ Product Version / Relationships ]({{< relref “./administration/products/productVersions/relationships” >}})	They define which child components or product a Product can have, or at least give the user the option to show them. You have different ways and properties to setup a relationship. It’s the most important part of Complex/Compound products	A Relationship name Discounts that will give the option to select 1 and only 1 Discount from a list of them.
[ Product Version / Product Validation Rules ]({{< relref “./administration/products/productVersions/validationRules” >}})	With validation Rules you can specify criterias that a configuration must met in order to consider it valid, otherwise you could show an Error to the user. You can also use rules to Hide or Show attributes, or to make them Editable or Read Only.	If Civil Status attribute is ‘married’ then Husband/Wife name attribute should be set.
[ Product Version / Configurator Sections ]({{< relref “./administration/products/productVersions/configuratorSections” >}})	They are used to organize the different relationships in the Product Configuration User Interface. In a Configuration Section you can show one or more relationships.	A ‘Required Components’ section that would include different mandatory relationships.
[ Product Version / Agreement Term Rules ]({{< relref “./administration/products/productVersions/agreementMapping” >}})	They define how an Agreement generated from that Product should be.	If ‘Urgent Service’ is selected then add the ’24/7 Agreement Term’ to the Agreement.

Leave a Comment Cancel reply

CONTENTS