With template types, it is possible to group templates by integration or workflow. They also allow adding contract variables (data fields) to contracts, which you can use to send data in and out of contracts.
By using template types, users of the Oneflow application can specify which integration the template and any contracts created from this template should belong to. When a template type is applied to a contract template, the contract template will automatically gain access to all the data fields predefined in the template type.
Template types also determine which webhooks send contract event notifications to.
|_links||object||Contains links to endpoints associated with the parent object. See Links.|
|created_time||string(datetime)||The time the template type was created.|
|data_fields||array||Contract variables that you can use in contract sections. See Data field.|
|description||string||Description of the template type, for example: "Our custom integration automatically populates template variables with this template type."|
|extension_type||string(enum)||An alias used for template types created by integration extensions. See Extension types.|
|id||integer(signed_integer_id)||The ID of the template.|
|name||string||A short, descriptive name for the template type, such as "Shoe Sales."|
|updated_time||string(datetime)||The time when the template type was last updated.|
Template types generated by an integration extension are assigned an extension type. This type is an alias assigned by Oneflow when the integration extension is created. When filtering template types, use the extension type instead of the identifier.
It should be one of the following values:
Updated 11 months ago