This idea is targeted to custom transformer deployment on FME Server but can be applied more generally to shared resources on FME Server.
Currently, custom transformers can be deployed to either a Repository, or to the Resources > Engine > Transformers folder as a shared resource.
Transformers deployed as a shared resource are available to all workspaces at runtime, which is very effective for ensuring consistency across an organisation.
The issue is that there is no simple way to manage this single resource across a large organisation with multiple development groups and I'm currently working with an organisation that has the "Engine" resource folder locked down so that only administrators can upload data there, to avoid inadvertent uploading of transformers that could potentially impact multiple workspaces.
It would be great if alternate shared resource paths could be implemented, either as entirely separate locations, or as sub-folders under the current path. (e.g. Engine > Transformers > [my sub-folder name]). In conjunction with this, sub-folders should allow for separate permissions than those of the main Engine folder.
Implementing the above would allow for different development teams to manage their own shared resources without impacting the entire organisation, and without needing to grant blanket permissions to the entire "Engine" folder.
