Introducing the Next-Generation Transformation Engine (v2)

While both transformation engines provide powerful mapping capabilities, several features and benefits are available only with the next-generation engine. These include:

1) A new suite of Ruleset Actions, including updated Variable types and an improved process to create custom Actions.

2) An improved Move rule that lessens the need for manual manipulation of your data by inspecting and adhering to Schema properties such as length, type, etc. It is more consistent in the way it inspects settings in the source and target Schemas; whether moving source data into a Ruleset variable or directly to target, the Move rule respects the data type set in the Schema and acts accordingly, for example:

• Trimming and padding of non-essential characters such as zeros and white spaces;
• Formatting implied decimals in both source and target data;
• Converting dates into the new DateTime data type.
• Providing better error messages when moving incompatible data types or violating other Schema properties. 

3) The power to run a transformation directly from the Ruleset editor, without deploying to a server.

4 The ability to quickly and easily configure older resources to work with the new transformation engine.

 

Please refer to the Related Topics at the end of this article for detailed information on the features described above.

 

You may see version references in the UI as you build Projects and other resources. For example, part of the process to create a Ruleset prompts you to select either version 1 (current engine) or version 2 (new engine); once created, the Ruleset editor is labeled to identify the version, as shown here:

 

While these versions refer primarily to the old or new transformation engine, they too are used in labeling resources such as the Ruleset, Business Process, and more.

If using Clarify v4.6 (and above) for the first time, you will be using the new engine by default, and all newly created Rulesets and supporting resources will be version 2.

However if you have existing integration projects that were built with pre-4.6 versions, you were using the older engine, including the older, version 1 Ruleset. You can continue to do so, as the Studio UI gives you the option to use earlier version resources.

If you choose to take advantage of the new engine but wish to use existing resources, then a simple conversion step will allow you to make these resources compatible with the new engine. See the topic on Resource Compatibility for more information.