Join Processor

the join processor combines the output of multiple input processors into a single message when multiple inputs are connected to it, you must define a connector for each why use the join processor use this processor when a flow needs to merge fields from separate input processors into one output message, rather than processing each input independently how it works output mode controls the shape of the combined output map produces standard json, useful when the output feeds something like a database array produces all the combined values as an array use array sort order to arrange the array's values in ascending or descending order map field prefix optionally adds a prefix to each field name in the combined output leave it empty if you don't need one input source determines what identifies each value's origin in the output the device name, or the name of the connecting wire definition if you choose device name, the input must include devicename and tagname fields parameters important when input source is set to device name, the input must include devicename and tagname fields parameter details output mode the shape of the combined output map or array see the important note below array sort by the field to sort array values by when output mode is set to array tag, definition, id, or time array sort order whether to sort the array in ascending or descending order input source what identifies each value's origin in the output the device name or the connecting wire definition name map field prefix an optional prefix added to each field name in the combined output field the field from each input to join, such as device, tagname, or value defaults to value pass through value determines whether the processor's output is the joined value or the original unchanged input value related topics use the join processor function docid\ zj7h7vqrqdopbs sapguq