I am not sure that I understand the need here. Do you want to move all of DEV, TEST, QA, and PROD connections to say, a PROD FME Server? Or move all of those connections to say, a QA FME Server? Am I missing something?
@samuelvaldez, sorry I missed this when you originally posted it. My main idea here is that it would be nice to have a mechanism to easily upload named connections from Desktop to Server, and vice-versa, without having to upload a workspace. The example of DEV/TEST/PROD was just to illustrate that there may be many different versions of named connections but not all will be stored/referenced in a single workspace.
Yes, and this should be bidrectional, a true sync. Desktop user Bob should be able to download Alice's connection and service definition configurations (if they've been marked public). Also, if someone modifies the connection using the FME Server UI both Bob & Alice will need to the new info.
Not the synchronisation of the connections, but the permissions.
If Bob has a Named Connection, he has 2 choices: give full permissions to Alice, which means she can change it. If Bob doesn't want Alice to change it, his only option is not to share it. More granular permission s(eg Read/Use and Full Access) would be much more convenient.
Updated idea statusOpen→Archived
Idea merged into:
All the votes from this idea have been transferred.