Skip to main content

Hi,

Our department currently uses 2025.1.1 version of Flow.

Is there a way in FME Flow to identify the database/web connections used by workspaces/workflows without the need to go into automations or schedules to identify them manually? 

Ideally, it would be great if can create a dashboard that lists all workflows (across all workspaces) along with the database connections they use. The reason for this request is that multiple offices within our department use FME Flow and have uploaded their own workflows. As a result, we’ve discovered that duplicate database connections have been created by these different teams.

Currently, I have to manually inspect each automation or schedule to identify the workflows and their associated connections. A centralized dashboard would greatly simplify this process and help us enforce standards by identifying and eliminating duplicate database connections.

Any help or ideas is much appreciated!

Thank you,

LS.

You can do this using a rest api call

e.g. to get dependencies for an automation

$(FME_SERVER_WEB_URL)/fmeapiv4/dependencies?id=@Value(id)&type=automation

 

This will then return a number of dependencies, one of which will have type connection

You can make a similar call for workspaces

 


Thank you for your quick response! 

I will try this out soon.

 

LS.


The dependency api is good start, but from my testing in 2023, it didn’t pick up everything (it does not go inside workspaces). But maybe it will do enough for your needs. 

If you need to get everything, our company has built a full on scrapping process to get ‘hopefully’ every fme flow and workspace detail. It is rather large and can work with both V3 and V4 api’s, and goes well beyond connections

Back in 2023 talking with the person who developed the dependancy api endpoint I noted this, in relation to doing this with the api:

Going reverse and getting all references would be a large task, especially as you would need the details inside every workspace to ensure it was comprehensive. Just looking at one of the more used web connections in a client environment and found it is in 403 locations; as published parameters, reader/writers, transformers, permissions and tokens.