Skip to main content
Open

Allow attribute values for web connection names

Related products:Transformers
  • August 15, 2017
  • 3 replies
  • 63 views

erik_jan
Contributor
Forum|alt.badge.img+26

At a customer site I have the need to "calculate" the name of a web connection based on a number of environment settings.

So, I use an AttributeCreator to create the _FMEServerName attribute.

But then the FMEServerJobsubmitter and FMEServerLogFileRetriever do not accept an attribute to define the named connection.

I would like this to be changed, so the name can be taken from an attribute (not just from a published parameter or a hard-coded value).

3 replies

  • September 26, 2018

Similarly, OneDrive web connections also cannot be specified by an attribute, but it would be very helpful if they could be.

Example use case: Our FME service processes a file for a customer. At the end of processing uploads it to the customer's OneDrive account. The name of the OneDrive web connection for that customer is retrieved from a configuration file/table i.e. is an attribute.

 


  • June 5, 2020

Yes thanks for submitting this idea, I was about to do the same.

We keep all our environment (test, prod etc) db connection names in a central environment table. This allows workspaces can be run in any environment and they detect which connection to use without us having to keep multiple versions of workspaces.

We can't set this up for web connections at present as FMEServerJobSubmitter won't allow the connection to be called from an attribute.


  • June 5, 2020

We can pass db connection names via attribute to set which environment our workspace will run against. We have a limitation with jobs that call other FME Server jobs as we can't pass web connections.

It would be great if we could pass web connections into FMEServerJobSubmitter via attribute.