Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
lookup_table_junction [2011/07/24 21:12]
hermann [Group] 		lookup_table_junction [2026/08/28 03:27] (current)
hermann Sync from local documentation review
Line 3: Line 3:
 ===== Description ===== ===== Description =====
  
-This functor chooses one from two possible ​lookup tables produced from different ​execution pipelines.+Picks the first available lookup table from two possible execution pipelines, so a lookup table still reaches the rest of the model even when one of the pipelines that could produce it does not run.
  
 ===== Inputs ===== ===== Inputs =====
  
-^ Name            ^ Type                                  ^ Description ​                                ​^ +^ Name  ^ Type  ^ Description ​ ^ 
-| Possible Table 1 | [[Lookup Table Type | Lookup Table]] | Lookup table output from an execution ​path. | +| Possible Table 1  | [[Lookup Table Type]] ​ | Lookup table produced by one possible ​execution ​pipeline.  | 
-| Possible Table 2 | [[Lookup Table Type | Lookup Table]] | Lookup table output from an execution ​path. |+| Possible Table 2  | [[Lookup Table Type]] ​ | Lookup table produced by another possible ​execution ​pipeline.  | 
 + 
 +===== Optional Inputs ===== 
 + 
 +None.
  
 ===== Outputs ===== ===== Outputs =====
  
-^ Name   ​^ Type                                 ​^ Description ​         ^ +^ Name  ^ Type  ^ Description ​ ^ 
-| Table  | [[Lookup Table Type | Lookup Table]] | Lookup table chosen. |+| Table  | [[Lookup Table Type]] ​ | Lookup table picked.  |
  
 ===== Group ===== ===== Group =====
Line 22: Line 26:
 ===== Notes ===== ===== Notes =====
  
-First, this functor verifies whether there is a valid input in "Possible Table 1", if not, it chooses as input "Possible Table 2". It is a convenient way to provide an alternate table in case an execution ​pipeline does not return ​a valid table. ​If "Possible Table 2" is not set, the functor will return a void output.+The inputs are checked ​in order — Possible Table 1, then Possible Table 2 — and the first one that has a value is passed to the output. If neither input has a value, the output is left without one, which allows chaining several junctions together ​to combine more than two possible pipelines. 
 + 
 +This functor is typically placed after a container whose execution ​is conditional,​ such as [[If Then]] or [[Skip On Error]], so a default lookup ​table is still available when that container'​s content does not run or does not finish. 
 + 
 +This functor was previously known as "JoinLookupTable"; that name is still accepted for backward compatibility with existing scripts.
  
 ===== Internal Name ===== ===== Internal Name =====