transformations:call
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
transformations:call [2021/05/26 15:01] – [Use cases] dmitry | transformations:call [2021/06/05 01:26] – craigt | ||
---|---|---|---|
Line 27: | Line 27: | ||
\\ | \\ | ||
=====Remarks===== | =====Remarks===== | ||
- | The called process - whether a module in the same project file, or a different project file - needs to start with an [[transformations: | ||
- | - Set up an Input action in a new module (or project file). | ||
- | - In the //calling// process, add and configure the Call action pointing to the new target module or project file. | ||
- | - Back in the //called// process, select " | ||
- | |||
The //Call// action' | The //Call// action' | ||
+ | |||
+ | The //Call// action, and the //Call// action paired with the //Input// action, are powerful ways to make your workflows more flexible. | ||
+ | * Module A calls Module B (without passing a dataset or parameters). | ||
+ | |||
+ | * Module A calls Module B, passing along its dataset (to Module B's Input action). | ||
+ | |||
+ | * Module A calls Module B, passing along its dataset and parameters (to Module B's Input action). Module B can use the passed parameters to manipulate the passed dataset (as settings in actions or values in calculations). Module B could also return the modified dataset back to the //calling// module, as well as pass it along to a third module, along with the parameter(s) (creating a chain). | ||
\\ | \\ | ||
=====Examples===== | =====Examples===== | ||
- | **Call | + | Calling |
- | {{ transformations: | + | {{ transformations: |
\\ \\ \\ | \\ \\ \\ | ||
- | **Call | + | Calling |
- | {{ transformations: | + | {{ transformations: |
transformations/call.txt · Last modified: 2021/07/18 00:54 by craigt