Working with Manual Tasks

A manual task is a task that must be performed by a person. For example, a manual task could involve a technician who travels to a customer's home to install a phone line. The system displays the description of the manual task in the Task web client worklist and query list.

After you have created a manual task entity using the Manual Task wizard or the Create Task wizard, you can start modeling the task data and assigning other attributes. When modeling manual tasks, see "Defining Manual Task Behaviors" for more information.

Related Topics

About Tasks

Task Editor

Defining Manual Task Behaviors

The Manual Task editor Task Data tab enables you to define behaviors at the task level. Behaviors provide a way to extend the functionality and appearance of task data. Each behavior type performs an action; for example, calculating or validating data, or displaying fields in read-only or read-write modes. When you define a behavior at the task level, the behavior applies only to the task.

When defining behaviors at the task level, you can use the Task editor Task Data tab to create the behavior, the Properties view for the behavior to refine the behavior information, and the Task editor Behaviors tab to view all of the behaviors defined for a task.

To define a behavior at the task level:

  1. From the Studio menu, select Show Design Perspective.

  2. Use the Studio Projects view.

  3. Double-click the manual task entity for which you are defining the behavior.

    Design Studio displays the task in the Manual Task editor.

  4. In the Task Data area, select the data node upon which to model the behavior.

    See "Task Editor Task Data Tab" for more information about the fields on this tab.

  5. Right-click in the Behaviors area and select Add Behavior.

  6. Select a behavior from the list.

    Note:

    The Calculation, Event, and Lookup behavior types cannot be defined for structured data elements. These behaviors are not relevant because structured data elements do not represent actual data and cannot be acted upon in this way.

    Design Studio adds the behavior to the Behaviors area. Each behavior type enables you to dynamically control a specific aspect of your order data model.

  7. In the Behaviors area, click the behavior to open the Properties view.

    The Properties view is displayed with the set of properties that you must define for the corresponding behavior type. See "Working with Behaviors" for more information.

  8. Click Save.

Note:

After you define the behavior properties, you can click the Task editor Behaviors tab review all of the behavior properties information defined for the task. See "Task Editor Behaviors Tab" for more information.