Siebel Business Process Framework: Task UI Guide > Task UI Concepts > Language Concepts for Task UI >

Task Instance

Task instance refers to a single instance of a particular task definition. A new task instance is created every time a particular kind of task is started, either by the end user, or by a long-running business process. The relationship between a task instance and a task definition is similar to the relationship between an object and a class in an object-oriented programming language.

Each task instance owns its own state, consisting of task properties and navigation history. Data in the associated business object is generally shared, except for the data in transient business components, which are unique to a specific task instance.

The life span of a task instance can often coincide with the life span of the associated task transaction, but that is not necessarily the case. The task instance might not even use a task transaction, or it might use a series of task transactions (by way of intermediate commits).

Tasks can be launched in ways other than a call through the task pane. A task can be started in the following ways:

• From an ad-hoc view. See Configuring the Ad-Hoc UI for Task Instantiation.

  You can do this using:

  • The Context pane. See Context Pane.
  • A push button. See Configuring Buttons for Task Instantiation.
  • Application and applet menu items. See Configuring Menus for Task Instantiation.
  • A link.
• From iHelp. See Configuring iHelp Links for Task Instantiation.
• From a long-running workflow. See the topic on configuring long-running workflows to invoke tasks in Siebel Business Process Framework: Workflow Guide.
• From a script. See Writing Scripts to Instantiate Tasks.

NOTE:  When you are configuring task initiation, it is important to consider access control. For an end user to launch a task, that user must have the appropriate responsibility associated with the task.

See also:

• UI Task
• Task Session