Whats your workflow to run jobs locally (FME Flow debugging)?

We often have a lot of parameters which are project specific. I.e we have project A with 10 parameters that are basically static and project b with 10 parameters that are also basically static. What we do is save the "parameter” values to our database and just use 1 main parameter in the workbench that says to get project A. Then use the featurereader to get all the needed settings as attributes instead of parameters. Its much less error prone but it only works if you for example know that for project A you always want to read a specific folder (or folders). 

OK  - I’m going to do some workspace hacking. Let see how I get on

Well I made some good progress but didn’t save my workspace - Workbench crashed and I lost it all - dang. But it was very hacky and most likely would not really have worked for most many workspaces.
Maybe I’ll have another go when I get really frustrated 

 

Is this about user parameters? From a form? Or environment parameters?

Yeah I just want to run a workspace in FME Form with the same inputs are from the job FME Server. It’s easy enough to copy paste but if there are a lot it gets annoying.

Essentially I have a workspace in the middle of an automation that I want to run locally (it has ~10 parameters which need to be set). The outputs from the automation writer from a previous job are used to populate the workspace. 

I’ve developed the workspace against a wide range of test data, however, now I’m in beta testing and there is a lot more real world data (and user setting combinations) which are not getting handled properly.

Clear. Sorry, we don’t have anything built for that scenario.