Chapter 5. Using the Workflow Manager Screen – Advanced

In the previous chapter, we discussed the basics of the Workflow Manager screen. In this chapter, we will take forward what we covered in the previous chapter. We will talk about the advanced topics of the Workflow Manager screen. We will start the chapter with a discussion on various tasks. As mentioned in the previous chapter, tasks are the basic building blocks of Workflow Manager. Later in the chapter, we will discuss worklet, parameter files, scheduling, and so on.

Working with tasks

As mentioned in the previous chapter, tasks are the basic building blocks of workflows. Every task has a different functionality, as every transformation has a different functionality. We need to use tasks as per our requirement in the workflow or worklet. Tasks can be created as reusable or as nonreusable.

You can create reusable tasks in Task Developer and nonreusable tasks in Workflow Manager.

Before we talk about each task in detail, let's take a look at the different tasks that we have:

Name of task

Details

Session task

This is used to execute a mapping.

Email task

This is used to send success or failure e-mail notifications.

Command task

This is used to execute Unix shell or Perl scripts or commands. It can also be used to execute DOS commands in Windows.

Timer task

This is used to add some time gap or delay between two tasks.

Assignment task

This is used to assign a value to a workflow variable.

Control task

This is used to control the flow of the workflow by stopping or aborting the workflow in the case of an error.

Decision task

This is used to check the status of multiple tasks and hence control the execution of the workflow based on the condition defined in the decision task.

Event Wait task

This is used to wait for a particular event to occur. Usually, it is called the file watcher task.

Event-Raise task

This is used to trigger user-defined events.

Link task

This is used to link tasks to each other. You can also define conditions in the link to control the execution of the workflow.

Before we move on, let's talk about an important topic. Consider that we have two workflows: wf_WORKFLOW1 and wf_WORKFLOW2. The Wf_WORKFLOW1 workflow contains the session task and the command task. We have a requirement in which wf_WORKFLOW1 triggers wf_WORKFLOW2 upon successful completion.

For the session task and the command task, wf_WORKFLOW1 will be called the parent workflow.

For wf_WORKFLOW2, wf_WORKFLOW1 will be called the top-level workflow, because wf_WORKFLOW1 triggers wf_WORKFLOW2.

..................Content has been hidden....................

You can't read the all page of ebook, please click here login for view all page.
Reset