There are times when a workspace (or automation) initiates several processes in parallel.
However, it is not always clear which path FME will choose to tackle first.
It would be really cool if the physical design of the workspace or automation had an impact. For example, if the order of Reader Feature Types, or the length of the connection line determined the order of submission.
Feature Types within a Bookmark might be read from left to right, or top to bottom.
Parallel processes that can all start after a trigger would be decided by which path was shortest submitting to the job queue first, to that with the longest path being submitted last.
Archived
Design of Workspace or Automation determines processing order
+11- Contributor
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.
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.
Login to the community
No account yet? Create an account
An FME Account is required to contribute
LoginEnter your E-mail address. We'll send you an e-mail with instructions to reset your password.