Project Task Field Definitions
This topic describes some of the important body fields and sublist fields available for the project task record.
Body Fields
This section lists some of the key body fields available for this record.
company
The company field represents the project that this task is associated with. Every task must be attached to a particular project, so this field is required.
estimatedWork
The estimatedWork body field is populated in one of two ways:
-
You can explicitly specify a value for this field — but you should use this approach only if you do not plan add values to the Assignees sublist, or if you are not yet ready to populate the sublist.
-
You can enter values for the Assignees sublist, and the system uses a value derived from the sublist to populate the estimatedWork body field. In this case, the system discards any value you might have specified for the estimatedWork body field. The reason is that each Assignee in the sublist has an estimatedWork value. So if you enter values in this sublist, the system totals the Estimated Work values for each assignee and uses this sum as the value for the Estimated Work body field.
Whether or not you include a value for this field determines whether this record is saved as a project task or a milestone task. For more details on this distinction, see Project Tasks Versus Milestone Tasks.
startDate
You cannot set a value for startDate unless you have also set the constraintType body field to _fixedDate. Refer also to Adding a Project Task Example.
title
The title field is the name of the Task. In the UI, this field is labeled Name. The value you choose for this field is the one used to represent the project task on the project record. This field is required.
Sublist Fields
Two sublists are available for integration — Time Tracking and Assignees.
Assignees
You can use the Assignees sublist (assigneeList) to assign employees or vendors to a project task. Note that the only resources available for adding to the sublist are those listed as resources on the project record.
When you add a record to the Assignees sublist, each record must include values for the following:
-
resource — Used to identify the assignee.
-
estimatedWork — The total hours the resource is expect to invest. The system uses the sum of all the estimatedWork sublist values to populate the estimatedWork body field.
-
unitCost — The cost per hour of the resource’s time.
If you are adding a record and you omit one of these values for any line in the sublist, the operation fails.
In order for an employee or vendor to be added as a resource to a project record, they must have been flagged as a project resource on the employee or vendor record. For more details, see Working with Resources in Project Management.
Time Tracking
When the Time Tracking feature is enabled, the Time Tracking sublist (timeItemList) is available. This list is used to track employee hours associated with the task.
For More Information
The SOAP Schema Browser includes definitions for all body fields, sublist fields, search filters, and search joins available to this record. For details, see the SOAP Schema Browser’s project task reference page. For information on using the SOAP Schema Browser, see SOAP Schema Browser.