Types of Tasks
Tasks can be of a number of types, each of which is represented by a different icon. Tasks can be user tasks, manual tasks, service tasks, script tasks, send tasks, receive tasks or reference tasks.
User Tasks
User tasks are those that require human interaction with a software application.
User tasks can be further configured for inbound and outbound parameters. Forms can be generated from the task’s input and output parameters, representing the information you want to present to and capture from the user.
You can also generate a pageflow process from a task.
TIBCO Business Studio Forms enables you to design, view, and test the forms you need to collect user input in a business process. You can create sophisticated forms without programming, and associate them with user tasks in order to provide richer user experiences for business process participants.
Service Tasks
Service tasks can ideally complete without human interaction (for example, an automatic email notification or a web service).
Script Tasks
Script tasks contain a set of instructions written in a scripting language (usually added to the step by the solution engineer) that will be executed in the runtime environment when the process is deployed and executed.
Using the business analysis capability, you can add text to a script task to describe the desired behavior of the script. However, by switching to solution design capability or by clicking Provide Implementation Details in the Properties view for the task, you can enter JavaScript to a script task. For more information, see the relevant implementation guide.
Send Tasks
Send tasks are used to send messages to a system or person outside of the process (often using a web service).
They can be paired with a receive task or message event to form a request response operation.
Receive Tasks
Receive tasks are used to wait for a message from a system or person outside of the process (often using a web service).
This type of task can be used to start a process as long as it has no incoming sequence flow and there are no start events in the process. In this case, the envelope icon is enclosed in a circle.
On the Interface tab, you can add parameters to a receive task; however, you cannot add data fields because data fields are used internally in a process, and parameters are in this case, inputs from an external process (for more information, see Data Fields and Parameters).
Receive tasks can be paired with a send task or message event to form a request response operation.You must also ensure that incoming messages are received by the correct process instance. For more information, see Correlation Data.
