In what order are features processed when there are multiple streams of data

From fmepedia

To help you forward this info a TinyURL (http://tinyurl.com/) has been defined.   The URL for this page can be quoted as: http://tinyurl.com/o95nu

Q) In what order are features processed when there are multiple streams of data?

A) If you have multiple streams (eg muiltiple connection links coming out of a single output port of a transformer or source feature type) the FIRST one you connected or drew is the first one that will fire, that is, where data will flow. And as soon as that feature has gone as far as it can, the second link drawn will have a feature sent down it.

Normally one would not care about this but there are some obscure cases where it can make a difference (such as when writing to tables that have foreign key constraints on them, or when global variables are involved). This Clipper example workspace is a good illustration of a case where the order of processing is important.

An edited link is classed the same as a newly drawn link, so if a link is placed and then edited (for example moved to another transformer and then back again) then the original order is not retained.

See this example workspace for a (contrived) illustration of this concept.