Skip to main content
Question

Chained workflows

  • January 29, 2015
  • 1 reply
  • 29 views

Forum|alt.badge.img
Trying to do some chained workspaces, having of course a parent and two other workspaces called by FMEServerJobSubmitter transformer and using 'wait' option as part of this transformer. I.e. an output file of first child workspace will be written to TEMP location which full path name is unknown. According to the article FME Server Workflow Management, when writing out to file-based data format, you can pass a reference to the file between workspaces, using the output_datasets{} list. So this reference is used like a pointer to the unknown location of output file of first workspace by the second FmeServerJobSubmitter as input. Now my question is how to define this as input within a second workspace itself when making/creating a second workspace as the location of input file is still unknown at this point of time?
This post is closed to further activity.
It may be an old question, an answered question, an implemented idea, or a notification-only post.
Please check post dates before relying on any information in a question or answer.
For follow-up or related questions, please post a new question or idea.
If there is a genuine update to be made, please contact us and request that the post is reopened.

1 reply

gio
Contributor
Forum|alt.badge.img+15
  • Contributor
  • January 29, 2015
The workspace wich is caalled with this unkown needs to have a parameter for this.

 

The submitter wil hav this parameter available when linked.