Differences

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

--- transformations:call [2016/06/19 20:19] – dmitry
+++ transformations:call [2021/06/05 01:26] – craigt
@@ Line 1: / Line 1: @@
-===== Call =====
+{{ transformations:CallAction.png}}
+====== CALL ======
+Category: Workflow / Internal \\
-Runs another project once. The input dataset of Call transformation is passed into the called project. The called project should use [[transformations:input|Input]] transformation in order to receive the dataset.
+\\
+=====Description=====
+This action runs another module or project once. The input dataset of the //Call// action can passed into the called module (project). In this case, the called module or project should use [[transformations:input|Input]] action in order to receive the dataset.
-Depending on transformation settings a resulting table can be returned into the calling project, or not.
+Depending on action settings, the result table of the called module (project) may or may not be returned to the calling project.
-**Use cases**
+\\
+=====Use cases=====
   * Run another project without iterating.
-  * Custom re-usable transformations.
+  * Custom re-usable actions.
+  * Fail-resistant workflows.
-**See also**
+\\
+=====Action settings=====
+^Setting^Description^
+|Module/Project to run<sup>*</sup>|Select whether to call a module (within the current project), or an external project (.morph file), then select the\\ module, or browse to the project file.|
+|Mode|Select whether a result table will be returned, or not, or if errors will be captured.  Options: //Do not return result table//,\\ //Return table// (and select the table to be returned), or //Capture errors and continue//.|
+|Assign parameters|If values will be passed into the called module/project via parameters, select the parameter name to use,\\ and the value<sup>*</sup> being passed in.|
+<sup>*</sup> Setting can be specified using a [[:parameters|parameter]].\\
+\\
+=====Remarks=====
+The //Call// action's resultant dataset will either be the dataset returned from the called process (if "Return table" was selected), or the dataset passed to it in the current workflow (if "Do not return result table" was selected).\\
+The //Call// action, and the //Call// action paired with the //Input// action, are powerful ways to make your workflows more flexible.  Below are some situations for using Call and Input, along with parameters and returned tables:\\
+  * Module A calls Module B (without passing a dataset or parameters).  Module B, using its own independent data source, runs its actions and finishes.  Module B could //also// Call a third module (creating a chain).
+  * Module A calls Module B, passing along its dataset (to Module B's Input action).  Module B transforms this copy of the dataset and outputs it.  Again, Module B could also pass the dataset on to //another// module to further transform it.
+  * 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=====
+Calling a module (or project) without passing along a dataset.  Parameters are optional.  A dataset may or may not be returned from the called module (or project).
+{{  transformations:call_action_img1.png?640  }}
+\\ \\ \\
+Calling a module (or project) with passing along a dataset via the [[transformations:input|Input]] action.  Parameters are optional.  A dataset may or may not be returned from the called module (or project).
+{{  transformations:call_action_img2.png?640  }}
+\\
+=====See also=====
   * [[transformations:input|Input]]
+  * [[transformations:iterate|Iterate]]
+  * [[transformations:iteratecolumns|Iterate columns]]
+  * [[transformations:iteratetable|Iterate table]]