Template Engine filter

You can use the Template Engine filter to access Template Engine. This filter can be added to input connectors and to output connectors.

When using a Template Engine filter, data coming in to the connector is passed on to Template Engine via the filter. This data is processed by Template engine, and sent back to the connector via the same filter.

The template used by Template Engine is the data sent to it via the filter. If this data contains Template Engine syntax, such as different types of directives and Template Engine utilities, this syntax is applied to the data. The output from Template Engine is then sent back to the connector via the filter.

All filter settings are pre-configured which means you only have to add the filter to the connector. See Creating filter chains in the Design Center documentation for information about filters and filter chains.

Using the filter on an input connector

You can use a Template Engine filter on an input connector to clean up the input data before it is passed on for further processing.

The input data must contain the appropriate Template Engine syntax for the filter to be of any use. A scenario for using a Template Engine filter on an input connector is where one StreamServer application sends output (including the appropriate Template Engine syntax) to another StreamServer application via a service call.

Using the filter on an output connector

You can use a Template Engine filter on an output connector to add features to the output delivered from the output connector.

You can add Template Engine syntax to the configuration of the Process connected to the output connector. When the output is delivered from the Process, the Template Engine syntax is applied by Template Engine before the output leaves the output connector. For example, you can use the #include directive in a StoryTeller Process to add a video to HTML output.