Skip to main content

Hi there,

We have a plethora of web connections in FME Flow from various people publishing workspaces.  now that we can use FME Flow as the web connection repo, I would like to tidy these up and ensure a better naming convention/structure.

What would be the best way to do this?

I think we have to:

  • download every workspace,
  • open them and audit the connections,
  • build a table to show where all the connections are used,
  • create new ones that adhere to our standards,
  • update all workspaces and republish to Flow,
  • ensure any workspace apps have permissions on the new connections
  • delete old connections

Does this sound right? 

Thanks,
marc

Broadly speaking, yes. 

Unfortunately the Workspace Reader does not generate an easy overview of web connections that are used. You could check the ReaderParameters and WriterParameters feature types to see where the attribute reader_parameter_name and writer_parameter_name contain the word CONNECTION. Same thing for the TransformerParameters feature type (and transformer_parameter_name attribute). This would also find database connections though.

One thing you can try, in a test environment first, if the connection names are unique enough, is a search and replace action across multiple files in one go (workspaces are plain text files, unless they’re password-protected). If you’re lucky, it’ll work right away.

There is an v4 API call you can make which will return dependencies for automations/workspaces, connections are returned with type ‘connection’

Community Stats

32,026
Posts
121,631
Replies
39,648
Members

Latest FME

Terms & ConditionsCookie settingsAccessibility statement
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.