A TaskBean is the basic building block of a Job. A Job can contain one or more TaskBeans. A TaskBean can be added at any position within the TaskBean chain (between two existing TaskBeans, at the end of the chain, or at the beginning of the chain).
When a TaskBean is created, it is assigned a TaskBean id that can never change. The name and description of the TaskBean can be edited at any time if desired.
When adding a new TaskBean, the most important settings is selecting the actual TaskBean Component from the available TaskBeans found in the TaskBean repository. This is at the bottom of the screen. Once selected the associated TaskBean Customizer will appear (if the TaskBean has a Customizer). The Customizer allows you to set the JavaBean properties that are exposed for the given TaskBean and access other attributes of a TaskBean. If the TaskBean does not have a TaskBean Customizer, then an appropriate message will appear informing the user that there is no Customizer. Not all TaskBeans need or have a Customizer, but it is expected most will have one.
Once a the TaskBean Component type is selected and saved, it can't be changed. If you wish to change it, you must delete the TaskBean and create a new one.
If the selected TaskBean has a Customizer it will be displayed at the bottom of the screen. The Customizer will normally allow the user to edit the properties of the input JavaBean associated with TaskBean. The Customizer can also perform any other function like accessing a local filesystem for viewing or editing. Customizers will normally save any associated input JavaBeans to a persistent store that is provided by the supporting Container as provided by the TaskBean API.
When a TaskBean is disabled, it will not be executed when the Job is run. It will essentially be skipped over.
The error dependency settings control how the Job proceeds with its execution if the TaskBean produces certain kinds of errors. This is often needed when the Job is made up of multiple TaskBeans.
If the TaskBean has an input and/or output JavaBean, the user has the option of saving the input and/or output JavaBean when the Job is run. This allows the Job to log exactly what inputs the TaskBean used when it ran and what outputs it generated. This is a very powerful auditing tool for the user. Using this, the user can view exactly how the Job was run and under what conditions. The input/output JavaBean can be viewed using the Job Tracker tool.