The custom entity definitions in VMware Cloud Director are object types that are bound to VMware Aria Automation Orchestrator object types. When a service provider publishes a custom entity definitions to either another service provider, or to one or more tenants, users VMware Cloud Director can own, manage, and change these types according to their needs. By executing services, service provider users and organization users can instantiate the custom entities and apply actions over the instances of the objects.
What to read next
Search for a Custom Entity You can search for a custom entity by its name.
Edit a Custom Entity Definition You can modify the name and the description of a custom entity. You cannot change the type of the entity or the VMware Aria Automation Orchestrator object type, to which the entity is bound. These are the default properties of the custom entity. If you want to modify any of the default properties, you must delete the custom entity definition and recreate it.
Add a Custom Entity Definition You can create a custom entity and map it to an existing VMware Aria Automation Orchestrator object type.
Custom Entity Instances Running a VMware Aria Automation Orchestrator workflow with an input parameter being an object type that is already defined as a custom entity definition in VMware Cloud Director shows the output parameter as an instance of a custom entity.
Associate an Action to a Custom Entity By associating an action to a custom entity definition, you can execute a set of VMware Aria Automation Orchestrator workflows on the instances of a particular custom entity.
Dissociate an Action From a Custom Entity You can remove a VMware Aria Automation Orchestrator workflow from the list of associated actions.
Publish a Custom Entity You must publish a custom entity so users from other tenants or service providers can run workflows using the custom entity instances as input parameters.
Delete a Custom Entity You can delete a custom entity definition if the custom entity is no longer in use, if it was configured incorrectly, or if you want to map the VMware Aria Automation Orchestrator type to a different custom entity.