Publishing a user parameter inside a custom transformer automatically adds it to every workspace that uses that transformer.

Publishing a user parameter inside a custom transformer automatically adds it to every workspace that uses that transformer.

• A. True
• B. False
• C. Only for the original workspace
• D. Depends on the transformer version

Answer: (B)

Published parameters live with the custom transformer, not with every workspace automatically. When you add or publish a parameter, it becomes part of the transformer’s definition, and any workspace that uses a version of that transformer that includes the new parameter can expose and configure it. However, existing workspaces that still reference an older transformer version won’t see the new parameter until they are updated to use a version of the transformer containing it. So the idea that it automatically adds to every workspace is not correct; the availability is version-dependent and requires workspace updates.

Published parameters live with the custom transformer, not with every workspace automatically. When you add or publish a parameter, it becomes part of the transformer’s definition, and any workspace that uses a version of that transformer that includes the new parameter can expose and configure it. However, existing workspaces that still reference an older transformer version won’t see the new parameter until they are updated to use a version of the transformer containing it. So the idea that it automatically adds to every workspace is not correct; the availability is version-dependent and requires workspace updates.