Tasks

Tasks are actions performed by a person, an application or both. Tasks are atomic activities — they’re very specific and can’t be broken down into a smaller tasks.

Tasks appear as rectangles with rounded corners. The default color of the outline and the marker changes according to the type of task.

Task

A Task is a non-specific task.

Service Task

A Service Task is a task that doesn’t require human interaction. It’s performed automatically by a web application or an external software service such as an automated application.

img

Service Task attributes

Fill in this field in the Attributes tab:

  • Implementation

    Specifies the technology used to send and receive messages.

    Use one of these values:

    Value Description
    ##WebService Web service technology or a URI that identifies other technology or coordination protocol. The default value.
    ##unspecified The implementation technology is unspecified.

Send Task

A Send Task is a task that sends a message to an external participant (organizational units, people or systems). When the message has been sent, the task is complete.

Use a Message Flow to show the flow of messages between participants.

img

Send Task attributes

Fill in these fields in the Attributes tab:

  • Message Reference

    The ID of the Message that is sent or received by the Task.

    Click to view the list of message IDs and select an ID.

  • Implementation

    Specifies the technology used to send and receive messages.

    Use one of these values:

    Value Description
    ##WebService Web service technology or a URI that identifies other technology or coordination protocol. The default value.
    ##unspecified The implementation technology is unspecified.

If you haven’t already defined the Message Definition at a global process level, you can define it in the Message tab:

  • Message

    The message that’s sent or received by a participant at the start, end or during or a process.

    • To add a message, click Add.

    • To remove a message, select the message from the list then click Remove.

    • To complete or edit a message, select the message from the list and fill in these fields:

      Field Description
      Name The name of the message.
      Description A description of the message.
      Item Definition The data type of the message.

Receive Task

A Receive Task is a task that waits for a message to arrive. When the message is received, the task is completed.

You can use a Message Flow to show the flow of messages between participants.

img

Receive Task attributes

Fill in these fields in the Attributes tab:

  • Message Reference

    The ID of the Message that is sent or received by the Task.

    Click to view the list of message IDs and select an ID.

  • Implementation

    Specifies the technology used to send and receive messages.

    Use one of these values:

    Value Description
    ##WebService Web service technology or a URI that identifies other technology or coordination protocol. The default value.
    ##unspecified The implementation technology is unspecified.

If you haven’t already defined the Message Definition at a global process level, you can define it in the Message tab:

  • Message

    The message that’s sent or received by a participant at the start, end or during or a process.

    • To add a message, click Add.

    • To remove a message, select the message from the list then click Remove.

    • To complete or edit a message, select the message from the list and fill in these fields:

      Field Description
      Name The name of the message.
      Description A description of the message.
      Item Definition The data type of the message.

Script Task

A Script Task represents a script that is executed during process execution. When the script has been executed, the task is completed.

img

Script Task attributes

Define this attribute in the Code tab.

  • Code

    The script source format and code.

    Script format: Click to view the list of available script formats and select one.

    Code: Type the script code.

Manual Task

A Manual Task is a task that’s performed by a person.

img

User Task

A User Task is used for Tasks performed by a person.

img

User Task attributes

Fill in this field in the Attributes tab:

  • Resource Reference

    The ID of the Resource that is associated with the Activity.

    Click to view the list of resources and select a resource ID.

 

If you haven’t already defined the Resource Definition at a global process level, you can define it in the Resource tab:

  • Resource

    Defines the resource that performs or is responsible for the activity. The resource can be a specific individual, a group, an organizational role or position, or an organization.

    • To add a resource, click Add.

    • To remove a resource, select the resource from the list then click Remove.

    • To complete or edit a resource, select the resource from the list and fill in these fields:

      Field Description
      Name The name of the resource — it can be a real name or role.
      Description A description of the resource.

Business Rule Task

A Business Rule Task provides a mechanism for a process to provide input to a Business Rules Engine and obtain the output.

img

Business Rule Task attributes

Fill in this field in the Attributes tab:

  • Implementation

    Specifies the technology used to send and receive messages.

    Use one of these values:

    Value Description
    ##WebService Web service technology or a URI that identifies other technology or coordination protocol. The default value.
    ##unspecified The implementation technology is unspecified.