A custom transformer will work on a different schema only if the exposed attributes are published.

A custom transformer will work on a different schema only if the exposed attributes are published.

• A. True
• B. False
• C. Depends on the data
• D. Not enough information

Answer: (A)

The ability of a custom transformer to run on a different input schema hinges on its defined interface. A custom transformer exposes certain attributes as its published interface, meaning those attributes are the names and types the transformer expects to receive and/or output. When you want the same transformer to work with another schema, you must publish or expose the attributes it uses so the workspace can map the actual input attributes in the new schema to the transformer’s exposed interface. If those attributes aren’t exposed, the transformer has no defined way to access or map the incoming attributes, and it won’t operate correctly on the new schema. Once the relevant attributes are published, the transformer can consistently interact with different schemas by relying on that published interface.

The ability of a custom transformer to run on a different input schema hinges on its defined interface. A custom transformer exposes certain attributes as its published interface, meaning those attributes are the names and types the transformer expects to receive and/or output. When you want the same transformer to work with another schema, you must publish or expose the attributes it uses so the workspace can map the actual input attributes in the new schema to the transformer’s exposed interface. If those attributes aren’t exposed, the transformer has no defined way to access or map the incoming attributes, and it won’t operate correctly on the new schema. Once the relevant attributes are published, the transformer can consistently interact with different schemas by relying on that published interface.