You can now set up a template containing an SQL query, and use it to create the transformations for many similar object types or event types. Templates are especially useful if you are modeling multiple flavors of the same event (for example, delivery dispatch by different shipping methods), or if you are transforming data from multiple data sources to create the same objects or events.

When you're creating a transformation for an object type or event type, you'll now get the choice to use one of your transformation templates. There's a new Templates tab in the Transformations area of the Objects and Events environment, where you can create, edit, rename, and delete your transformation templates. You can also see the transformation instances that you've created using each template. The list of transformations in the Transformations tab tells you if a transformation was created from a template, and you can access the template from there too.

To get the best out of transformation templates, include local parameters in them for the parts that you expect to vary, such as the source system name. For each transformation instance that you create from a template, you can then just go to the list of local parameters in the transformation editor, and add the correct values for that transformation. The content from the template remains read-only, and it changes to match if you edit the template - so with one edit you can apply fixes or updates to all the transformations that use the template. If a transformation instance needs further customization, for example because a source system holds the data for an attribute in a different way, you can create a partial overwrite like you would for a Celonis catalog transformation. Partial overwrites stay in effect when the template changes.

For the instructions to work with transformation templates, see Creating transformation templates.