When you want to create a custom transformer for a very specific process you think will only ever be needed in your workspace, which transformer type should you choose?

When you want to create a custom transformer for a very specific process you think will only ever be needed in your workspace, which transformer type should you choose?

• A. Embedded
• B. Linked
• C. Answer
• D. Special

Answer: (A)

Embedding the custom transformer inside the workspace keeps the transformation logic tightly tied to that specific workflow. This makes sense for a process you expect to use only in this workspace, because everything stays self-contained: you don’t rely on external assets or separate files, and the workspace becomes portable as a single unit. If you later decide you want to reuse the same logic elsewhere, you can recreate or convert it to a linked (external) transformer or publish it to a library, but for a one-off, embedded is the simplest and most portable choice. Linked transformers are meant for reuse across workspaces and external storage, which isn’t your current need, and the other option isn’t a real transformer type in FME.

Embedding the custom transformer inside the workspace keeps the transformation logic tightly tied to that specific workflow. This makes sense for a process you expect to use only in this workspace, because everything stays self-contained: you don’t rely on external assets or separate files, and the workspace becomes portable as a single unit. If you later decide you want to reuse the same logic elsewhere, you can recreate or convert it to a linked (external) transformer or publish it to a library, but for a one-off, embedded is the simplest and most portable choice. Linked transformers are meant for reuse across workspaces and external storage, which isn’t your current need, and the other option isn’t a real transformer type in FME.