Task Editor Details Tab

The Task editor Details tab appears for manual, automated, activation, and transformation task types.

Use the Details tab to define attributes that you can use to extend the task definition.

For all tasks in a process, there are properties that you define in Design Studio that the OSM server requires to properly execute the task. These properties include the order with which the task is associated, the amount of time in which you expect the task to complete, the group responsible for completing the task, and the manner in which the tasks are assigned. You configure these details on the Task editor Details tab. The Details tab also contains properties that enable you to add or remove a parent task (and its inherited data), and to model the data node on which a multi-instance process relies to create multiple instances of the task.

Field	Use
Extends	Select an existing or create a new task to extend this task (the task's data is inherited) by clicking the Select button. To create a new task that this task would be an extension of, click New. After you have selected or created an task, click Open to access the Task editor. Click Clear (red X) to clear the selected value from the field. Using task inheritance, you can leverage existing task data when building new, similar tasks. See "About Task Extensions and Inheritance" for more information.
Order	The order associated with a task determines the overall data set that will be available to the task when you model the task data. Note: If you are planning to use the task for an order (OrderA) and also an order (OrderB) that is extended from that order, you must select the parent order (OrderA) here.
Pivot Node	(Optional) Select the Pivot node for this task. When OSM executes the corresponding task at run-time, the system generates a separate task instance for each separate value of the pivot node in the order. For example, if the pivot node is an address field, and three addresses are included in the order, the system generates three separate task instances when this task occurs in a process. Note: OSM compensation processing does not support task pivot nodes.
Expected Duration and Calculate using Workgroup Calendar	Specify the length of time expected to complete the task. By default, the expected duration of a task is set to 1 day (system time). You can select any value up to 999 in weeks, days, hours, minutes, or seconds. You can also calculate the duration based on your workgroup calendar by selecting Calculate using Workgroup Calendar. If you have more than one workgroup with different calendars all responsible for the same task, the calculation is based on the first available workgroup that has access to the task. Expected durations can be useful during reporting and jeopardy processing.
Order Priority Offset	Select a value between 9 and -9 to differentiate this task's priority within the order. For example, if the order is created at priority 6, and this task is assigned a priority offset of -2, then this task would run at priority 4 while other tasks in the order would run at priority 6. Similarly, you could assign a task a priority offset of +2 which would mean that the task would run at a slightly higher priority than other tasks in the order.
Responsibility	Select which department or team is responsible for this task. The default value is System. You can select System or enter a value that is meaningful within the context of your system topology. This field is only visible to the reporting API.
Namespace Based on Task Name	(Automated, Activation, and Transformation tasks only) Select this option to use a namespace for the task that is based on the task name.
Assignment Algorithm	(Manual tasks only) (Optional) Select the algorithm to use when automatically assigning tasks to users. OSM provides two default algorithms: Load Balancing and Round Robin. The Load Balancing algorithm attempts to distribute tasks based on a user's current workload. The OSM server assigns tasks after determining which user in the workgroup has the fewest number of assigned tasks. The Round Robin algorithm assigns tasks in a predefined order among the users in the workgroup. You can add custom assignment algorithms to OSM, using OSM's cartridge management tools. For custom algorithms, you must manually enter the algorithm name in the Assignment Algorithm field. If you do not specify an algorithm in this field, you must manually assign tasks.
JNDI Name	(Manual tasks only) Enter the JNDI name for custom assignment algorithms.
Transformation Manager	(Transformation tasks only) Enter the name of the transformation manager to be called when this transformation task is reached. Do any of the following: Click Select to select an existing transformation manager. Click New to create a new transformation manager. See "Creating New Transformation Managers" for more information. Click Open to open the selected transformation manager in the Transformation Manager editor.
Order Component	(Transformation tasks only) Enter the name of the order component that provides context for this transformation task and assists in order item selection. Do any of the following: Click Select to select an existing order component. Click New to create a new order component. See "Creating New Order Component Specifications" for more information. Click Open to open the selected order component in the Order Component editor. If you are not using the default provided automation plug-in for the transformation task, this field may be optional, depending on the way your automation is written.
Update Order with Transformation Response	(Transformation tasks only) Select this option to enable OSM to persist the transformed order items on the order.

Note:

You cannot use pivot nodes to model multiple instances of activation tasks. To model multiple activation task instances, create a multi-instance subprocess that contains only the activation task.