task command

A table step is a step within a task command that takes input parameters in the form of a table (with multiple rows and columns).

The result of a step's execution can be set either in the step's result or in the parent task command's result.

Just like an admin command, a task command should provide constructors to create and load commands.

The additional step implementation is similar to the implementation of a task command step.

Task command - consists of zero or more steps, with each step having its own parameters in addition to the task's parameters.

Listing 8 shows the complete example of a command definition file that has both the admin command and task command.

A task command extension contains additional steps added to an already existing command.

A command provider can also include extensions to a task command provided by another command provider.

A task command provider should provide methods to create and load commands similar to the admin command.

The constructor to create a step takes its parent task command and step metadata as input parameters.

A task command can be extended with additional steps.

The constructor to load a step takes its parent task command and step data as input parameters.

In Listing 12, the steps use their task command's result and then add to it.

You also can create custom tasks programmatically, and then integrate them into DTS Designer using the Register Custom Task command.

A task command has zero or more parameters and zero or more steps.

Figure 7 shows the interaction flow from the task command to the external ILOG BRMS.

Listing 11 shows an example of a task command extension provider.

A task command can have zero or more steps.

It gets the table step from the task command first, then constructs a row.

We can create a task command that has one step (getPerson) with parameters as shown in Listing 5.

Listing 7 shows an example of how to extend a task command by adding a new step.