Developer Workflow Guide > Human Task > Create Task Instances
  

Create Task Instances

You use the task distribution options to create instances of a Human task.
You can configure the options to create task instances based on the number of items in the data set, or you can configure options to create task instances based on the values in a column you select.
If you select the option to create task instances by text, you define a user list that you must use when you configure the task steps. If you select the option to create task instances by number of items, you do not define a user list.
Note: If you change from one task configuration policy to another, you discard the previous task configuration.

Creating Task Instances of Equal Size

You can create task instances based on the number of records or clusters in the data set. You can also specify the number of task instances to create. In each cases, you create tasks of equal size.
    1. Open a Human task.
    2. Select the Task Distribution tab, and enable task distribution.
    3. Choose to create task instances by number of items.
    4. Set the number of tasks to create, or set the number of rows or clusters in each task.

Creating Task Instances by Data Value

You can create task instances that contain all the records in the data set that have common values in a column that you select.
    1. Open a Human task.
    2. Select the Task Distribution tab, and enable task distribution.
    3. Choose to create task instances by data value.
    Optionally, specify the maximum number of records that any task instance can contain.
    4. Select a column name from the Column menu. The menu lists the column names on the resource that you specify on the Data Source tab.
    If you add a Cluster step to the Human task, select the group key column that you used in the mapping that generated the clusters. You select the group key column to ensure that the task distribution process does not split the records in a cluster into different clusters.
    Note: The Column menu has a precision of 65. The menu does not display a column name that contains more than 65 characters.
    5. Select the method that the workflow will use to assign users or groups to task instances.
    You can associate each user or group with a single value in the column, or you can associate each user or group with a range of column values.
    6. Create the assignments between the users or groups and the column data values.
    You can add the users or groups and the values to associate with them to a grid in the Task Distribution tab. Or, you can connect to an external database table that stores the lists of users, groups, and column values.
    7. To add values to the grid, select one of the following options:
    8. To add values from an external database table, browse to a database connection and select a database table. resource from the database.
    9. Optionally, select a user or group to receive any record in the data source that does not satisfy the task distribution criteria that you specify.

Rules and Guidelines for Task Distribution By Column Values

Consider the following rules and guidelines when you specify data values and user or group names for task distribution:

Setting Permissions on a Step

Enter a short description of the task here (optional).
    1. Open a Human task.
    2. Select the Permissions tab.
    The tab displays the options for viewing permissions and editing permissions.
    3. To set each permission, open the menu in the Value field. Use the menu options to select the permission that you need.

Rules and Guidelines for Step Permission Options

By default, Analyst tool users can view all data and perform any action in the task instances that they own. Use the Permissions options to specify a set of viewing permissions and editing permissions for the task instances. Apply the permissions in the step that defines the task instances.
You can use permissions to assign data to users based on the users' roles or areas of expertise. For example, you might define a series of steps in a Human task so that different users can edit different columns of workflow data. Or, you might decide to hide sensitive data, such as salaries or Social Security numbers, from one or more users.
Consider the following rules and guidelines when you set the permissions: