Projecttask
A Projecttask object can be:
-
A project task or a project phase is a work package to be completed as part of a project. It includes information about the work to be done, when, by whom, and at what cost.
-
A project milestone is a reference point in your project life cycle that marks a significant event or goal the to be completed as part of a project.
Review the Usage Guidelines for the Projecttask object.
|
— |
XML |
SOAP |
REST |
Database table |
|---|---|---|---|---|
|
Object |
|
|
|
|
|
Supported Commands |
See Project Milestones, Project Phases, and Project Tasks |
— |
The Projecttask object has the following standard properties:
Projecttask object properties may also include custom fields. The object type supports the custom equal to read method and the enable_custom read attribute.
|
XML/SOAP |
REST |
Database |
Description |
|---|---|---|---|
|
|
|
|
Is everyone able to assign time/expenses to this task. |
|
|
— |
— |
[Write-only in XML API and SOAP API] A comma separated list of employee nicknames assigned to the task. Must be empty if Used only when adding or modifying objects in the XML API and SOAP API No values are returned when reading project tasks using the XML API or SOAP API. Use project task assignment [ |
|
— |
|
— |
[Read-only] The assignment groups assigned to this task. Array of internal IDs for assignment group objects. |
|
— |
|
— |
[Read-only] The users directly assigned to this task. Excludes users assigned to the task as part of an assignment group only. Array of internal IDs for user objects. |
|
— |
|
— |
A comma-delimited list of internal IDs of employees to be copied (Cc) into assignment notification email. Other possible listed values:
|
|
— |
|
— |
A comma-delimited lists of additional recipient email addresses to be copied (Cc) into assignment notification email. Used for recipients who are not SuiteProjects Pro users. |
|
— |
|
— |
The attachments associated with this task. Array of internal IDs for attachment objects. Array of |
|
|
|
|
[Read-only] Calculated finish date. See Date Fields |
|
|
|
|
[Read-only] Calculated start date of the milestone, phase or task. See Date Fields |
|
|
— |
|
Calculated, read-only classification of the project task with the following values:
|
|
|
|
|
A 1/0 field indicating if this is closed task. Additional time can not be booked against closed task. |
|
|
|
|
The internal ID of the associated cost center |
|
|
|
|
[Read-only] The date the milestone, phase or task was created. See Date Fields |
|
|
|
|
The currency for monetary values in the milestone, phase or task record. Three-letter currency code. Should be the same as the project currency. |
|
|
— |
|
[Read-only] The name of the associated customer. |
|
|
|
|
The internal ID of the associated customer. |
|
|
|
|
The category to assign to a timesheet entry assigned to this task. The feature has to be enabled for this assignment to work. |
|
where |
where |
where |
A feature, if enabled, would assign this |
|
|
— |
|
A "1/0" field indicating if the record was deleted |
|
|
— |
|
The earliest this task can finish, measured in days from project start. This field is recalculated whenever any project dates, user assignments,or user schedules are changed. See Date Fields. |
|
|
— |
|
The earliest this task can start, measured in days from project start. This field is recalculated whenever any project dates, user assignments,or user schedules are changed. See Date Fields. |
|
|
— |
|
If the use task estimating feature is turned on, this field will have the estimated total time the task will take to complete. If zero, no estimating has occurred so the estimate is the same as the plan. |
|
|
|
|
The unique external ID of the milestone, phase or task, if the record was imported from an external system. |
|
|
|
|
The finish no later than date of the task. The task must be finished by this date. See Date Fields. |
|
— |
|
— |
— |
|
|
|
|
[Read-only] The unique internal identifier of the milestone, phase or task. Assigned by SuiteProjects Pro. |
|
|
|
|
User-defined task ID. Value assigned automatically if not set when adding a project task. Must be unique for each |
|
|
— |
|
A 1/0 field indicating if any other project_tasks have us as a parent. |
|
— |
|
— |
Flag 1/0 indicating if phase is ready for recognition |
|
— |
|
— |
— |
|
|
|
|
If set to 1 then the task budget is manually entered rather than calculated by SuiteProjects Pro. |
|
|
|
|
[Required] Short description of this task. |
|
|
|
|
If set to 1, this is not billable. This is only applicable for project billing rules. |
|
|
|
|
Notes about the project task. |
|
|
|
|
The internal ID of the source project task, if this project task was copied from an existing project task. |
|
|
|
|
The internal ID of the immediate ancestor. If zero or null, this is a project-level (top-level) task or phase. |
|
|
|
|
This field is an estimate of the percentage of planned time which has been completed. It has no relation to the real time spent on a task. (A 5-hour task could consume 50 hours of work but still be only 25% complete.) |
|
|
|
|
Total number of hours the task is estimated to require. This is the total amount of time the task should take if worked on continuously by one person with no interruptions. A task with zero planned hours is also known as a milestone. |
|
|
|
|
Comma delimited list of task IDs which must complete before this task can start. |
|
|
|
|
Comma delimited list for task ID:days of lag time for predecessors. Only populated if there is a lag time. |
|
|
|
|
Comma delimited list of task ID:relationship type for predecessors. Only populated if the relationship type is not finish-to-start. |
|
|
|
|
The priority of the task (1 - 9). |
|
|
— |
|
[Read-only] The name of the associated project. |
|
|
|
|
[Required] The ID of the associated project. |
|
|
|
|
The ID of the associated project task type. Not for phases. |
|
|
|
|
The sequence number of this task. |
|
|
|
|
Optional scheduled starting date of this task. Overrides computed date Start_date. See Date Fields. |
|
|
|
|
If task budgeting is enabled, this is the total cost of the task. |
|
|
|
|
If task budgeting is enabled this is the total projected billing for the task. |
|
— |
|
— |
— |
|
|
|
|
A timetype filter. This will hold a list of the timetypes that are allowed to book time to this task. |
|
|
|
|
[Read-only] Time the record was last updated or modified. See Date Fields. |
|
|
|
|
Flag set to 1 if they are using the project level user assignment. Must not be set to |
|
— |
|
— |
[Read-only] The users assigned to this task. Includes users assigned to the task directly or as part of an assignment group. Array of internal IDs for user objects. |
Usage Guidelines
Review the following guidelines:
-
When reading
Projecttaskobjects with theallmethod, thelimitattribute applies to referencedProjectobjects instead ofProjecttaskobjects unless thefilterordeletedattributes are used. It limits the number of referencedProjectobjects and not the number ofProjecttaskobjects returned.The following code sample reads all
Projecttaskobjects associated with the first thousandProjectobjects.<Read type="Projecttask" method="all" limit="0,1000"/>To limit the number of
Projecttaskobjects, you can use a different readmethodor set thefilterattribute toall. -
Adding or modifying a project task triggers the project recalculation process in SuiteProjects Pro unless you use the
no_recalcattribute (see Add, Update and Upsert Attributes), or unless your company's account is configured never to trigger the project recalculation process in SuiteProjects Pro when a change is made using the API. -
When using the XML API, the
Projecttaskobject element accepts the attributeindex. Theindexattribute value can be any one of the column names in theproject_tasktable. This lets you referenceProjecttaskobjects by the designatedindexproperty instead of referencingProjecttaskobjects by internal ID. If you set theindexattribute toid_number, for example, you can reference predecessor tasks [predecessors] by these user-defined task numbers instead of internal IDs. The API looks up and store the internal IDs to the database.The following code sample looks up the
Projecttaskobjects associated with the same project withid_numberset to123andabcand stores their internal IDs in thepredecessorsproperty for theProjecttaskwith internal ID427.<Modify type="Projecttask"> <Projecttask index="id_number"> <id>427</id> <predecessors>123,abc</predecessors> </Projecttask> </Modify> -
You cannot delete a
Projecttaskobject if this object is referenced by an object of any of the following type. Delete any dependent objects first before you delete aProjecttaskobject.Note:You can delete a
Projecttaskobject that is referenced by otherProjecttaskobjects aspredecessors.