Allow manually updating embedded custom transformers

That would be a really great improvement.

I oftenly create workspaces that can be reusable by me and a lot of my collegues.

Because of the complexity of the treatment, I package some parts into customs transformers.

When I push updates, it could be really usefull that users can just get a copy of the fmx file (from an email for example) and update their transformers in their workbenches instead of deleting and then copy/past the new one from the new version of the script.

Using linked transformers is to complicated for some of my users (they have to copy/paste the new version into the FME directory which is not always easy for them).

Yeah - I like this idea as well - I've just created a bunch of custom transformers. Sometimes when opening a workspace with one inside I get prompted that a new version is available and I get asked if I would like to update. Sometimes not - I can't figure out why the prompt is sometimes there and sometimes not.

If you choose 'No' on this update prompt then there is no way to later update it without having to delete and re-add the custom transformer as far as I can see.

I also agree with the comment by @arthur_bazin​ about linked custom transformers. They are handy because they will always use the version they are pointed to, but sharing a workspace with linked transformers inside becomes a bit tricky.

Can confirm this still happens sometimes and embedding the transformer again, it embeds the old version(the one currently in the workspace). You have delete all instances of the transformer and add it again (time wasting)

I was thinking about submitting a similar idea. My situation was that the client regularly looses the user settings in a virtual environment. The workaround was to embed the custom transformers.

There might be one caveat: if the user edits the custom transformer. If an embedded custom transformer has been edited, the upgrade could ask if it is OK to reset all the changes ;)