Differences

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

--- transformations:call [2021/05/22 23:24] – craigt
+++ transformations:call [2021/06/04 16:18] – craigt
@@ Line 5: / Line 5: @@
 \\
 =====Description=====
-This action runs another project once. The input dataset of the //Call// action is passed into the called project. The called module or project should use [[transformations:input|Input]] action in order to receive the dataset.
+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 action settings, a resulting table may or may not be returned to the calling project.
+Depending on action settings, the result table of the called module (project) may or may not be returned to the calling project.
 \\
@@ Line 14: / Line 13: @@
   * Run another project without iterating.
   * Custom re-usable actions.
+  * Fail-resistant workflows.
@@ Line 27: / Line 27: @@
 \\
 =====Remarks=====
-The called process - whether a module in the same project file, or a different project file - needs to start with an [[transformations:input|Input]] action to receive the dataset sent by the //Call// action.\\
+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 called process will need to start with an [[transformations:input|Input]] action if it will be receiving the dataset of the calling workflow to work with.\\
   - 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.
+  - In the //calling// process, add and configure the Call action to point to the new target module or project file.
   - Back in the //called// process, select "Populate automatically" to connect to the data from the Call action (in called //modules// only).  For called //project files//, you'll either need to "Paste data" (copied from the data source) or "Import dataset" (from a previous-saved .dset file), to populate the //Input// with sample data.\\
-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).\\
 \\