Commands are the tasks performed within the chain, based on a connection with a datasource. For more complex chains, this can include commands triggered by a variety of conditions.
Note: Before you add a chain, ensure your organization sets up the connections required to enable commands with its data sources.
To run specific commands serially—one after the other, with each waiting for the previous command to finish—or simultaneously in parallel, you can group them together.
Adding a Command to a Chain
- In the chain, select the command to perform:
- To add a new command to the chain, under Available BizApps, click its connection, and then move the command to where it should occur in the chain.
- To duplicate an existing command, select its node, click Copy , and move the new node to where it should occur in the chain.
Note: To add a command as the first node of the chain, move it to Start.
- To link the command to its previous and next nodes in the chain, click and drag lines between their node's ports.
Note: To change a node's position in the chain, unlink it from other nodes, and then move it to where it should occur. To move multiple nodes at once, hold SHIFT as you select them.
- Select the new node, and click Edit .
- Enter the command's parameters:
- Under Basic Info, enter a unique name and description to help identify the command and its intent.
- To run the command multiple times, for each item in list, select Iterator . and enter the items or list output to iterate against.
- Under Command Properties, enter the command's inputs, based on the connector.
- Click Save.
Managing Commands as a Group
To run specific commands in serial—one after the other, with each waiting for the previous command to finish—or simultaneously in parallel, group them together.
- To create a command group, drag a command to another in the group, and drop when Add appears.
- To add a command to an existing group, drag the command to the group, and drop when the group's Add appears.
To edit the group, such as to set up how its commands run:
- Select the group, and click Edit .
- Under Group type, choose how to run its commands.
- To run the commands one-after-another, select Serial .
- To run the commands simultaneously, select Parallel .
- To run the group multiple times, such as against multiple items of an earlier output in the chain, enable Iterator . and enter the items or list output to iterate against.
- For a serial group, under Reorder Nodes, sort the commands in the order they should run.
- Click Save.
To just sort the nodes within a serial group from the chain, select the group, click Reorder , arrange the nodes as necessary, and click Stop Reordering.
Running Only a Single Command or Group
To ease testing and quick iterations as you build chains, you can execute a single command or command group within a chain.
- From Wdata Chains, click Build, and select Execute from the chain's menu.
- For the command or group to run, click Execute this command .
- Click Run Chain.
Skipping a Command
To develop branching logic, or as part of developing a chain, you may need to skip a command to force a specific result. You can also set up conditional logic to automatically return a specific result based on set rules.
- In the chain, select the command's node, click Edit , and select Skip .
- Choose whether to automatically return a result of info , warning , or error for the command when skipped.
- To skip the command only if specific criteria is met, specify when. Build the conditional logic as a group you add rules and other groups of rules to, each joined with an AND or OR boolean.
- If all conditions must be true to skip, select AND.
- If only one condition must be true to skip, select OR.
You can add rules based on various data types:
|String||Two or more characters|
|Integer||Any whole, non-decimal numeric value|
|Date||Any date string or Date variable|
|Float||Any numeric value|
To verify whether data meets the criteria to skip the command, pair it with an operator and value:
Is not blank
Matches RegExp, for regular expression
- Click Save.
Managing a Command's Error Handling
To trap or ignore errors for a command:
- In the chain, click the command's node, click Edit , and select Error handling .
- Under Error actions , choose what to do if the command fails.
- To follow the chain branching logic, select Continue with chain.
- To stop the chain completely, select Exit chain.
- To stop the chain temporarily, such as to remedy the issue, select Pause chain. To restart the chain after the issue is resolved, select the command in the chain, and click Resume.
- To stop the command if it takes longer than it should, under Timeout conditions , enter its maximum duration in seconds.
- To retry a command if its data source is intermittent or unavailable, enter the number of retries to attempt and how many seconds to wait between attempts.
- Under Error conditions , choose when to ignore an error, such as when creating a remote directory that already exists.
- Under Output interpretation , choose whether to fail a command based on whether it's output is found. If you select Fail if output(s) found, enter the file format of the output to scan for.
- Click Save.
Removing a Command from a Chain
To remove a command from a chain, click its node, click Delete, and then click Delete.
Note: To help ensure the logic of the chain, you can't delete a command if its parent has multiple siblings or branches on its same level.