Skip to main content
  • Home
  • Ideas
  • Modular FME , Bookmarks acting like modules
Archived

Modular FME , Bookmarks acting like modules

Related products:FME Form
  • siennaatsafe
    siennaatsafe
  • M
    marko
  • S
    saqibamin
M

I'd love to see FME have the ability to push modules/custom transformers/bookmarks up to the server that automatically gets copied to all workbenches on the server containing that module. If you could create a bookmark in the usual way and then save it as a module. Then on the push select if you want to push the entire workbench to the server or just individual modules. That way if you have lots of shared functionally between workbenches you can push to all the FME workbenches in one hit rather then making multiple small changes.

We have multiple complicated workbenches that share functionality but wouldn't want to have just one workbench doing everything due to unwanted complexity. However, ensuring bug fixes and small changes are equal across all the services can be painful.

If this could be put in place along with a more GIT based versioning system FME server would be a lot easier to work with.

This post is closed to further activity.
It may be a question with a best answer, an implemented idea, or just a post needing no comment.
If you have a follow-up or related question, please post a new question or idea.
If there is a genuine update to be made, please contact us and request that the post is reopened.

4 replies

david_r
Evangelist
  • david_rEvangelist
  • August 2, 2017

I'm not quite sure I understand, but wouldn't this be similar to using linked custom transformers?

M
Forum|alt.badge.img+5
  • marko
  • Author
  • August 3, 2017
A custom transformer is good for dropping into a workbench to solve a problem, but what if you want to change that block of transformers and then push that to all of your server workbenches at the same time? You would have to make modifications to every workbench save and push, where as if the server could save modules you could change and push just once and every workbench on your server would be modified with that change. We have multiple complicated workbenches that have shared functionality so currently I have to open each one in turn, modify and then push. Making sure they are all consistent can be tricky/time consuming.
david_r
Evangelist
  • david_rEvangelist
  • August 3, 2017
But isn't this just what a linked (opposed to an embedded) custom transformer does? Or am I missing something? If you update a linked transformer on FME Server, all workbenches referencing that linked transformer will automatically use the new version, no need to re-upload.
rylanatsafe
Safer
Forum|alt.badge.img+13
  • rylanatsafeSafer
  • Safer
  • February 9, 2018
Hi @marko, I have to agree with what @david_r has suggested here. Have you reviewed whether Linked Custom Transformers might provide a resolution for your request?

 

https://docs.safe.com/fme/html/FME_Desktop_Documentation/FME_Workbench/Workbench/custom_transformer_embedding_linking.htm

 

"When you export a custom transformer and use it in another workspace, you can choose to link to the transformer by referencing its definition. If the definition changes, then so does the workspace behavior. Linking to the transformer is useful if you frequently update it and you use it in many different workspaces."

 

 

Please note that I have marked this idea as "Not Planned" – if Linked Custom Transformers do not address your concerns, please reply and help us further establish the criteria.

Helpful Members This Week

Community Stats

30,921
Posts
117,185
Replies
38,725
Members

Latest FME

Terms & ConditionsCookie settings

Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings
A product of
Safe Software respectfully acknowledges that we live, learn and work on the traditional and unceded territories of the Kwantlen, Katzie, and Semiahmoo First Nations.