Guide to Chakra data modelling
Process object captures the process information of a single instance of process. So for a Sales solution, individual leads are actually individual processes. Similarly in a support solution individual tickets are actually individual processes. The schema that differentiates a lead from a ticket is defined in a schema object called procedure.
Task object captures a single task done or being done by a user. For example calling a lead or navigating to a location on the field can both be modeled as tasks.
Record object is used to capture stateless data. For example a contact or an SKU Item is modeled as a record object. These are stateless data only used to store some amount of information.
Chakra models are designed to be not only customizable but to conform to the data model of the business usecase. The most granular part of this data model is called an attribute. Think of it as a field in a database table or a column in an excel sheet.
🗃️ Attribute Types
📄️ Derived Attribute
Derived attributes allow you to define attributes for your Chakra Object based on automatic calculations. Following are the supported types:
Call object is to represent a physical call object made or received by a user. Depending on your telephony integration a call object might be generated by telephony plugins like Twilio and Ameyo