You could create a wrapper workspace that fires both workspaces after each other using 2 WorkspaceRunner transformers, or use a batch script to fire both after each other. If you have FME 2016, you can also use the new FeatureWriter to write your features first and then connect the WorkspaceRunner to the Summary port.

If you have access to FME 2016, use the FeatureWriter Transformer instead of an actual writer. Then use the feature that exits the summary port to trigger the WorkspaceRunner, as I believe the summary feature only exits when the writing has finished. Alternatively, just place a FeatureHolder between the FeatureWriter and the WorksapceRunner.

Good luck.

Thank you both for your quick answers. Unfortunately, I only have FME 2015 (1.2.1). The wrapper workspace is a good idea, but the thing is I have ~80 FME processes and in each one of them I have to include a workspace runner, pointing to the same extern FME process. To build a wrapper for each would be very time-consuming.

Any other Ideas?

That's why I also mentioned the batch script (*.cmd/*.bat file).

thank you I will try that.

I think the only way to be sure is to use a shutdown script. Either use a system command to run the next workspace or the iFMEWorkspaceRunner method using FME objects. But as the others have said, in 2016 the FeatureWriter is designed to solve this scenario.