Manage Entity Types

overview in this developer guide, you will learn about creating entity types in the entity service an entity is an object or a concept, such as a vehicle or a box, for which data is stored and operations are performed understanding entity categories and sub categories entity category an entity category represents the type of object or concept for storing and manipulating data it provides a high level classification for entities for example, in the context of a vehicle entity, four wheeler or two wheeler can be considered entity categories entity sub category an entity sub category is a further subdivision of an entity category it allows for a more granular classification of entities within a specific category continuing with the vehicle entity example, if a four wheeler is an entity category, then a truck or car can be considered an entity sub category create an entity type to create a new entity type, call the createentitytype endpoint and provide the entity type parameters see the following request below { "name" { "plural" "vehicles", "singular" "vehicle" }, "alias" { "plural" "vehicles", "singular" "vehicle" }, "category" \[ { "name" "fourwheeler", "description" "four wheeler vehicles", "subcategory" \[ "car", "truck" ] }, { "name" "twowheeler", "description" "two wheeler vehicles", "subcategory" \[ "motorcycle", "scooter" ] } ], "attributes" \[ { "alias" "model", "name" "model", "description" "vehicle model", "isreadpublic" true, "tag" \[ "basic", "info" ], "datatype" "string", "indexed" true, "defaultvalue" "", "validation" { "required" true } }, { "alias" "color", "name" "color", "description" "vehicle color", "isreadpublic" true, "tag" \[ "basic", "info" ], "datatype" "string", "indexed" false, "defaultvalue" "", "validation" { "required" false, "valueoneof" \[ "red", "blue", "green", "black", "white" ] } } ], "coreattributes" \[ { "name" "uniquecode", "alias" "ucode" } ], "callback" { "url" "https //example com/callback", "meta" {} }, "isstatemachineenabled" false, "events" \[ "created", "updated", "deleted" ], "entitycode" "1234", "terminalttl" "90d", "enableorchestrator" true } in this example the entity type has a plural name "vehicles" and a singular name "vehicle" entities are identified by their pluralname which must be unique per customer and app it has aliases for both plural and singular names it belongs to two categories "fourwheeler" and "twowheeler" “fourweeler” has subcategories of “car” and “truck, and “twowheeler” has subcategories of “motorcycle” and “scooter” it has two attributes "model” and "color" "model" is a required attribute "color" is an optional attribute with predefined allowed values it has a core attribute "uniquecode" with an alias "ucode" it specifies a callback url to notify the outcome of the request state machine is enabled it has three events "created", "updated", and "deleted" it has an entity code "1234" the terminal ttl is set to 90 days the enableorchestrator is set to true time to live (ttl) time to live (ttl) in the entity service allows developers to automatically manage the deletion or removal of entity instances by specifying a time duration after which they should be considered expired and eligible for removal this feature helps optimize storage utilization and ensures that outdated or irrelevant entity instances are efficiently removed from the system ttl for state machine enabled entities for entities with a state machine, follow these guidelines to configure ttl every entity must define a terminalttl and terminalstates in the entity state machine config the ttl will be set on the entity when it transitions to one of the terminal state(s) as per the configuration the ttl will be unset from the entity when it transitions away from the terminal state(s) as per the configuration example { "states" \[ { "name" "active", "terminalstates" \[ "inactive" ] }, { "name" "inactive" } ], "terminalttl" "30d" } in this example, when an entity transitions to the "inactive" state, which is defined as a terminal state, the ttl of "30d" (30 days) will be set if the entity transitions away from the "inactive" state, the ttl will be unset ttl for non state machine enabled entities for entities without a state machine, use the following configuration to apply ttl implement a new attribute named ttloninactive with a default value of false if terminalttl is not provided in the request body and ttloninactive is set to true , the terminalttl will automatically be set to "90d" (90 days) once ttloninactive is set to true , it cannot be reverted to false if ttloninactive is false and terminalttl is set, then in every operation of entity instance creation, the terminalttl will be updated irrespective of whether the instance's isactive is true or false example { "name" { "plural" "products", "singular" "product" }, "ttloninactive" true, "terminalttl" "60d" } in this example, the ttloninactive attribute is set to true , and the terminalttl is explicitly set to "60d" (60 days) if terminalttl was not provided, it would default to "90d" (90 days) since ttloninactive is true validations and constraints ttl records can take up to 48 hours to expire the maximum allowed value for terminalttl is 90 days setting a value greater than 90 days will result in an error for entities with a state machine, at least one valid transition to a terminal state must be defined failure to do so will result in an error while configuring the state machine by configuring ttl for your entities, you can effectively manage the lifecycle of entity instances, optimize storage utilization, and ensure that outdated or irrelevant data is automatically removed