Document is commonly used to modify documents by performing the calculateDataExtension action, the checkIn action, the checkOut action, the createProof action, the getTotalSizeForDocuments action, the isLinkedDocument action, the isProofAutoGenrationEnabled action, the move action, or the unlinkDocuments action on the document object.

Document allows you to view or modify a document object.

Document calculateDataExtension recalculates expressions in custom form fields.

Custom forms can contain calculated custom fields. These use data expressions and the name of other existing fields. The calculated field evaluates the expression and displays the result. The calculateDataExtension action recalculates the expressions in custom form fields. This can be useful when one of the fields used in the expression is updated, and the value in the calculated field must be updated as well.

Document checkIn is used to check in a document that has been checked out. Only a an admin or the user who checked out the document can check that document in. A specific document can be selected by using the DocumentIDs parameter.

Performs the checkIn action on the Document object using the documentIDs parameter.

Document checkOut is used to check out a document for review. This means the document can't be modified or updated until the user who checked the document out or an administrator checks the document back in. The DocumentIDs parameter allows you to select specific documents for checkout.

Performs the checkOut action on the Document object. The DocumentIDs parameter allows you to select specific documents for checkout.

Document completeLargeDocument

Performs the completeLargeDocument action on the Document object

Document createLargeDocument

Performs the createLargeDocument action on the Document object

Document createLinkedProofVersion

Performs the createLinkedProofVersion action on the Document object

Document createProof is used to create a proof from an existing document. You can specify field values for documentVersionID and advancedProofingOptions.

Performs the createProof action on the Document object. You can specify field values for documentVersionID and advancedProofingOptions.

Document createProofRest

Performs the createProofRest action on the Document object

Document getDocumentProofTemplate

Performs the getDocumentProofTemplate action on the Document object

Document getProofRecipients

Performs the getProofRecipients action on the Document object

Document getProofStages

Performs the getProofStages action on the Document object

Document getProofTemplate

Performs the getProofTemplate action on the Document object

Document getTotalSizeForDocuments

Performs the getTotalSizeForDocuments action on the Document object

Document isLinkedDocument allows you to check if a document has link associations with objects outside of Workfront. You can select specific documents using the documentID parameter.

Performs the isLinkedDocument action on the Document object. You can select specific documents using the documentID parameter.

Document isProofAutoGenrationEnabled is used to check if proof automation is enabled on the document object.

Performs the isProofAutoGenrationEnabled action on the Document object.

Document move

Performs the move action on the Document object

Document unlinkDocuments allows you to unlink documents from objects and/or associations made outside of Workfront.

Performs the unlinkDocuments action on the Document object to remove associations and/or objects outside of Workfront.

Document by ID is commonly used to modify a specific document with the unique ID specified by performing the calculateDataExtension action, the checkIn action, the checkOut action, the createProof action, the getTotalSizeForDocuments action, the isLinkedDocument action, the isProofAutoGenrationEnabled action, the move action, or the unlinkDocuments action on the document object.

Document by ID allows you to view or modify an existing document object by referencing its unique ID.

Document ID calculateDataExtension recalculates expressions in custom form fields for the specific Document object with the unique ID specified.

Custom forms can contain calculated custom fields. These use data expressions and the name of other existing fields. The calculated field evaluates the expression and displays the result. The calculateDataExtension action recalculates the expressions in custom form fields. This can be useful when one of the fields used in the expression is updated, and the value in the calculated field must be updated as well.

Document checkIn by ID is used to check in a document with the corresponding {ID} that has been checked out. Only a an admin or the user who checked out the document can check that document in. A specific document can be selected by using the DocumentIDs parameter.

Performs the checkIn action on the Document object with the corresponding {ID}.

Document checkOut by ID is used to check out a document with the corresponding {ID} for review. This means the document can't be modified or updated until the user who checked the document out or an administrator checks the document back in. The DocumentIDs parameter allows you to select specific documents for checkout.

Performs the checkOut action on the Document object with the corresponding {ID}.

Document completeLargeDocument

Performs the completeLargeDocument action on the Document object

Document createLargeDocument

Performs the createLargeDocument action on the Document object

Document createLinkedProofVersion

Performs the createLinkedProofVersion action on the Document object

Document createProof ID is used to create a proof from an existing document with the corresponding {ID}. You can specify field values for documentVersionID and advancedProofingOptions.

Performs the createProof action on the Document object with the corresponding {ID}. You can specify field values for documentVersionID and advancedProofingOptions.

Document createProofRest

Performs the createProofRest action on the Document object

Document getDocumentProofTemplate

Performs the getDocumentProofTemplate action on the Document object

Document getProofRecipients

Performs the getProofRecipients action on the Document object

Document getProofStages

Performs the getProofStages action on the Document object

Document getProofTemplate

Performs the getProofTemplate action on the Document object

Document getTotalSizeForDocuments

Performs the getTotalSizeForDocuments action on the Document object

Document isLinkedDocument ID allows you to check if a document with the corresponding {ID} has link associations with objects outside of Workfront.

Performs the isLinkedDocument action on the Document object with the corresponding {ID}.

Document isProofAutoGenrationEnabled ID is used to check if proof automation is enabled on the document object with the corresponding {ID}.

Performs the isProofAutoGenrationEnabled action on the Document object with the corresponding {ID}.

Document move

Performs the move action on the Document object

Document unlinkDocuments ID allows you to unlink the document(s) with the corresponding {ID}(s) from objects and/or associations made outside of Workfront.

Performs the unlinkDocuments action on the Document object(s) with the corresponding {ID}(s) to remove associations and/or objects outside of Workfront.

Allows you to modify an existing Optask (Issue) object using the acceptWork, Issue approveApproval, Issue assign, Issue assignMultiple, Issue calculateDataExtension, Issue convertToProject, Issue convertToTask, Issue linkExternalObject, Issue markDone, Issue markNotDone, Issue move, Issue moveToTask, Issue recallApproval, Issue rejectApproval, Issue replyToAssignment, Issue unacceptWork, Issue unassign, or Issue unlinkExternalObject objects/endpoints.

Modify an existing Issue object.

Optask (Issue) acceptWork is used to accept work that has been assigned to an Issue object.

Performs the acceptWork action on the Issue object

Optask (Issue) approveApproval by Issue is commonly used to approve an approval that is associated with an Issue by using the userID parameter, the approvalUsername parameter, the approvalPassword parameter, the auditNote parameter, the AuditUserIDs parameter, or the sendNoteAsEmail parameter.

Performs the approveApproval action on the Issue object

Optask (Issue) assign allows you to assign an Issue object to a particular user.

Performs the assign action on the Issue object

Optask (Issue) assignMultiple allows you to assign an Issue object to groups of users by specifying field values for userIDs, roleIDs,and/or teamID.

Performs the assignMultiple action on an Issue object, allowing you to assign an issue object to multiple users at once, based on the userIDs, roleIDs,and/or teamID parameters.

Issue bulkMove

Performs the bulkMove action on the Issue object

Issue calculateDataExtension recalculates expressions in custom form fields.

Custom forms can contain calculated custom fields. These use data expressions and the name of other existing fields. The calculated field evaluates the expression and displays the result. The calculateDataExtension action recalculates the expressions in custom form fields. This can be useful when one of the fields used in the expression is updated, and the value in the calculated field must be updated as well.

Optask (Issue) convertToProject is used to convert an Issue object into a Project object. You can also specify field values for the project, exchangeRate, and options parameters.

Allows you to convert an existing Issue object into a Project object. You can also specify field values for the project, exchangeRate, and options parameters.

Optask (Issue) convertToTask is used to convert an Issue object into a Task object. You can also specify field values for the parameters task and options.

Allows you to convert an existing Issue object into a Task object. You can also specify field values for the parameters task and options.

Issue copyIssue

Performs the copyIssue action on the Issue object

Optask (Issue) LinkExternalObject is commonly used to link an external object to a specific issue with the unique ID specified by using the objID parameter, the linkedObjectID parameter, the integrationType parameter, the URL parameter, or the params parameter.

Performs the linkExternalObject action on the Issue object. Additional parameters include objID parameter, the linkedObjectID, the integrationType, the URL, or the params.

Optask (Issue) markDone can be used to change the status of an Issue to 'done'.

Allows you to change the status of an Issue to 'done'.

Optask (Issue) markNotDone can be used to change the status of an Issue to 'not done'. You can also specify a field value for the parameter assignmentID.

Allows you to change the status of an Issue to 'not done'. You can also specify a field value for the parameter assignmentID.

Optask (Issue) move allows you to move an Issue to another Project. You can specify the project by using the parameter projectID.

Allows you to move an Issue to another Project by specifying the field value for the parameter projectID field.

Optask (Issue) moveToTask allows you to move an Issue to another Task. You can specify the Task by using the parameters projectID and parentID.

Allows you to move an Issue to another Task by specifying the field values for the parameters projectID and parentID.

Optask (Issue) RecallApproval is commonly used to recall an Issue from the approval process.

When objects in Workfront are submitted for approval, it is sometimes necessary to recall them from the approval process. When a user recalls an Issue approval, the Issue returns to the status it was in prior to the initiation of the approval process. RecallApproval by Issue removes an Issue from the approval process and returns it to its prior status.

Optask (Issue) rejectApproval by Issue is commonly used to reject an approval process that is associated with an issue by using the userID parameter, the approvalUsername parameter, the approvalPassword parameter, the auditNote parameter, the AuditUserIDs parameter, or the sendNoteAsEmail parameter.

Performs the rejectApproval action on the Issue object

Issue replyToAssignment

Performs the replyToAssignment action on the Issue object

Issue unacceptWork

Performs the unacceptWork action on the Issue object

Optask (Issue) unlinkExternalObject by Issue ID commonly used to unlink an external object from an Issue with the corresponding {ID} by using the objID parameter, the linkedObjectID parameter, or the integrationType parameter.

Work sometimes requires access to objects (such as documents or folders) that are stored outside of Workfront. These objects can be linked to an Issue, so that the object is available from inside Workfront. UnlinkExternalObject by Issue ID unlinks a previously-linked object from an Issue with the corresponding {ID}.

Optask (Issue) unlinkExternalObject by Issue commonly used to unlink an external object from an Issue by using the objID parameter, the linkedObjectID parameter, or the integrationType parameter.

Work sometimes requires access to objects (such as documents or folders) that are stored outside of Workfront. These objects can be linked to an Issue, so that the object is available from inside Workfront. UnlinkExternalObject by Issue ID unlinks a previously-linked object from an Issue.

Optask by ID (or issue by ID in the GUI) is commonly used to modify a specific Issue with the unique ID specified by performing the acceptWork action, the approveApproval action, the assign action, the assignMultiple action, the calculateDataExtension action, the convertToProject action, the convertToTask action, the linkExternalObject action, the markDone action, the markNotDone action, the move action, the moveToTask action, the recallApproval action, the rejectApproval action, the replyToAssignment action, the unacceptWork action, the unassign action, or the unlinkExternalObject action on the Issue object

Optask by ID allows you to view or modify an existing issue object by referencing its unique ID.

Optask (Issue) acceptWork by ID is used to accept work on an Issue that is defined by the corresponding {ID}.

Performs the acceptWork action on the Issue object defined by the corresponding {ID}.

Optask (Issue) ID approveApproval is commonly used to approve an approval that is associated with the specific Issue associated with the unique {ID} in the object path. More specific approvals can be made by using the userID parameter, the approvalUsername parameter, the approvalPassword parameter, the auditNote parameter, the auditUserIDs parameter, and/or the sendNoteAsEmail parameter.

Users can create Approval Processes for Projects, Tasks, or Issues as a way to ensure that work is proceeding as desired. If an approval process is associated with an Issue, the Issue must be approved according to the approval process before it can move forward. Issue ID approveApproval allows a designated user to approve the approval of a specific Issue with the unique ID specified.

Optask (Issue) assign by ID allows you to assign an Issue with the corresponding {ID} object to a particular user.

Performs the assign action on the Issue object

Optask (Issue) assignMultiple by ID allows you to assign an Issue object by {ID} to groups of users by specifying field values for userIDs, roleIDs,and/or teamID.

Performs the assignMultiple action on the Issue object that corresponds with the specified {ID}, allowing you to assign an issue object to multiple users at once, based on the userIDs, roleIDs,and/or teamID parameters.

Issue bulkMove

Performs the bulkMove action on the Issue object

Issue ID calculateDataExtension recalculates expressions in custom form fields in the specific Issue object with the unique ID specified.

Custom forms can contain calculated custom fields. These use data expressions and the name of other existing fields. The calculated field evaluates the expression and displays the result. The calculateDataExtension action recalculates the expressions in custom form fields. This can be useful when one of the fields used in the expression is updated, and the value in the calculated field must be updated as well.

Optask (Issue) convertToProject is used to convert an Issue object with the corresponding {ID} into a Project object. You can also specify field values for the project, exchangeRate, and options parameters.

Allows you to convert an existing Issue object with the corresponding {ID} into a Project object. You can also specify field values for the project, exchangeRate, and options parameters.

Optask (Issue) convertToTask is used to convert an Issue object with the corresponding {ID} into a Task object. You can also specify field values for the parameters task and options.

Allows you to convert an existing Issue object with the corresponding {ID} into a Task object. You can also specify field values for the parameters task and options.

Issue copyIssue

Performs the copyIssue action on the Issue object

Optask (Issue) LinkExternalObject is commonly used to link an external object to a specific Issue with the corresponding {ID} by using the linkedObjectID parameter, the integrationType parameter, the URL parameter, or the params parameter.

Performs the linkExternalObject action on the Issue object with the corresponding {ID}. Additional parameters include objID parameter, the linkedObjectID, the integrationType, the URL, or the params.

Optask (Issue) markDone can be used to change the status of an Issue with corresponding {ID} to 'done'.

Allows you to change the status of an Issue with the corresponding {ID} to 'done'.

Optask (Issue) markNotDone can be used to change the status of an Issue with the corresponding {ID} to 'not done'. You can also specify a field value for the parameter assignmentID.

Allows you to change the status of an Issue with the corresponding {ID} to 'not done' by specifying a value for the assignmentID field. You can also specify a field value for the parameter assignmentID.

Optask (Issue) move allows you to move an Issue with the corresponding {ID} to another Project. You can specify the project by using the parameter projectID.

Allows you to move an Issue with the corresponding {ID} to another Project by specifying the field value for the parameter projectID field.

Optask (Issue) moveToTask allows you to move an Issue with the corresponding {ID} to another Task. You can specify the Task by using the parameters projectID and parentID.

Allows you to move an Issue with the corresponding {ID} to another Task by specifying the field values for the parameters projectID and parentID.

Optask (Issue) RecallApproval is commonly used to recall an Issue with the corresponding {ID} from the approval process.

When objects in Workfront are submitted for approval, it is sometimes necessary to recall them from the approval process. When a user recalls an Issue approval, the Issue returns to the status it was in prior to the initiation of the approval process. RecallApproval by Issue ID removes an Issue with the corresponding {ID} from the approval process and returns it to its prior status.

Optask (Issue) rejectApproval by Issue ID is commonly used to reject an approval process that is associated with an Issue by using the userID parameter, the approvalUsername parameter, the approvalPassword parameter, the auditNote parameter, the AuditUserIDs parameter, or the sendNoteAsEmail parameter.

Performs the rejectApproval action on the Issue object with the corresponding {ID}.

Issue replyToAssignment

Performs the replyToAssignment action on the Issue object

Issue unacceptWork

Performs the unacceptWork action on the Issue object

Issue unassign

Performs the unassign action on the Issue object

Issue unlinkExternalObject

Performs the unlinkExternalObject action on the Issue object

Project is commonly used to modify a project by performing the approveApproval action, the attachTemplate action, the calculateDataExtension action, the calculateFinance action, the calculateTimeline action, the linkExternalObject action, the recallApproval action, the rejectApproval action, the setBudgetToSchedule action, or the unlinkExternalObject action on the project object.

Project allows you to view or modify existing project objects.

Project approveApproval is commonly used to approve an approval that is associated with the project by using the userID parameter, the approvalUsername parameter, the approvalPassword parameter, the auditNote parameter, the auditUserIDs parameter, or the sendNoteAsEmail parameter.

Users can create Approval Processes for Projects, Tasks, or Issues as a way to ensure that work is proceeding as desired. If an approval process is associated with a project, the project must be approved according to the approval process before it can move forward. Project approveApproval allows a designated user to approve the approval of a project.

Project attachTemplate is commonly used to attach a template to the project by using the templateID parameter, the predecessorTaskID parameter, the parentTaskID parameter, the excludeTemplateTaskIDs paramater, or the options parameter.

Templates are used to capture repeatable processes, information, and settings associated with projects. Once a Template has been created, it can be used as a blueprint for Projects. Attaching a Template to a Project allows the project to use the processes, information, and settings in the template without the user setting them manually. Project attachTemplate allows a user to attach a Template to a Project.

Project calculateDataExtension recalculates expressions in custom form fields.

Custom forms can contain calculated custom fields. These use data expressions and the name of other existing fields. The calculated field evaluates the expression and displays the result. The calculateDataExtension action recalculates the expressions in custom form fields. This can be useful when one of the fields used in the expression is updated, and the value in the calculated field must be updated as well.

Project calculateFinance is commonly used to calculate the finances for a project.

Users can keep track of finances at the Project and Task levels, as well as limited financial information for Issues. Project managers can manually update some financial fields for a project, while other financial data is calculated automatically by Workfront. Project calculateFinance allows Workfront to calculate finances across the project.

Project calculateTimeline is commonly used to calculate the timeline for the project.

Timelines in Workfront can be affected a variety of factors. For example, a Project Timeline will be calculated when a project is created, based on Start Date, Completion Date, or Duration, but it can also be affected by external factors such as personnel taking time off. Project calculateTimeline allows Workfront to use these factors to calculate the timeline of a project.

Project linkExternalObject is commonly used to link an external object to the project by using the objID parameter, the linkedObjectID parameter, the integrationType parameter, the URL parameter, or the params parameter.

Work sometimes requires access to objects (such as documents or folders) that are stored outside of Workfront. These objects can be linked to a Project, so that the object is available from inside Workfront. Project linkExternalObject links an external object to a Project.

Project recallApproval is commonly used to recall the project from the approval process.

When objects in Workfront are submitted for approval, it is sometimes necessary to recall them from the approval process. When a user recalls a project approval, the project returns to the status it was in prior to the initiation of the approval process. Project recallApproval removes a project from the approval process and returns it to its prior status.

Project rejectApproval is commonly used to reject an approval process that is associated with the Project by using the userID parameter, the approvalUsername parameter, the approvalPassword parameter, the auditNote parameter, the auditUserIDs parameter, or the sendNoteAsEmail parameter.

Performs the rejectApproval action on the Project object

Project setBudgetToSchedule is commonly used with to set the budget of a project to match the schedule of the project.

When estimating allocation of resources in the Capacity Planner, a user can select to set the budgeted hours to match the planned hours. Project setBudgetToSchedule sets the budgeted hours of a project to match the planned hours of that project.

Project unlinkExternalObject is commonly used to unlink an external object from a project by using the objID parameter, the linkedObjectID parameter, or the integrationType parameter.

Work sometimes requires access to objects (such as documents or folders) that are stored outside of Workfront. These objects can be linked to a Project, so that the object is available from inside Workfront. Project unlinkExternalObject unlinks a previously-linked object from a project.

Project updateBusinessCaseSource

Performs the updateBusinessCaseSource action on the Project object

Project by ID is commonly used to modify a specific project with the unique ID specified by performing the approveApproval action, the attachTemplate action, the calculateDataExtension action, the calculateFinance action, the calculateTimeline action, the linkExternalObject action, the recallApproval action, the rejectApproval action, the setBudgetToSchedule action, or the unlinkExternalObject action on the project object.

Project by ID allows you to view or modify an existing project object by referencing its unique ID.

Project ID approveApproval is commonly used to approve an approval that is associated with the unique {ID} in the object path. More specific approvals can be made by using the userID parameter, the approvalUsername parameter, the approvalPassword parameter, the auditNote parameter, the auditUserIDs parameter, and/or the sendNoteAsEmail parameter.

Users can create Approval Processes for Projects, Tasks, or Issues as a way to ensure that work is proceeding as desired. If an approval process is associated with a project, the project must be approved according to the approval process before it can move forward. Project ID approveApproval allows a designated user to approve the approval of a specific project with the unique ID specified.

Project ID attachTemplate is commonly used to attach a template to a specific project with the unique ID specified by using the templateID parameter, the predecessorTaskID parameter, the parentTaskID parameter, the excludeTemplateTaskIDs paramater, or the options parameter.

Templates are used to capture repeatable processes, information, and settings associated with projects. Once a Template has been created, it can be used as a blueprint for Projects. Attaching a Template to a Project allows the project to use the processes, information, and settings in the template without the user setting them manually. Project ID attachTemplate allows a user to attach a Template to a specific Project with the unique ID specified.

Project ID calculateDataExtension recalculates expressions in custom form fields in the specific Project object with the unique ID specified.

Custom forms can contain calculated custom fields. These use data expressions and the name of other existing fields. The calculated field evaluates the expression and displays the result. The calculateDataExtension action recalculates the expressions in custom form fields. This can be useful when one of the fields used in the expression is updated, and the value in the calculated field must be updated as well.

Project ID calculateFinance is commonly used to calculate the finances for the specific project with the unique ID specified.

Users can keep track of finances at the Project and Task levels, as well as limited financial information for Issues. Project managers can manually update some financial fields for a project, while other financial data is calculated automatically by Workfront. Project ID calculateFinance allows Workfront to calculate finances across the specific project with the unique ID specified.

Project ID calculateTimeline is commonly used to calculate the timeline for the specific project with the unique ID specified.

Timelines in Workfront can be affected a variety of factors. For example, a Project Timeline will be calculated when a project is created, based on Start Date, Completion Date, or Duration, but it can also be affected by external factors such as personnel taking time off. Project ID calculateTimeline allows Workfront to use these factors to calculate the timeline of the specific project with the unique ID specified.

Project ID linkExternalObject is commonly used to link an external object to a project by using the objID parameter, the linkedObjectID parameter, the integrationType parameter, the URL paramater, or the params parameter.

Work sometimes requires access to objects (such as documents or folders) that are stored outside of Workfront. These objects can be linked to a Project, so that the object is available from inside Workfront. Project ID linkExternalObject links an object to a specific Project with the unique ID specified.

Project ID recallApproval is commonly used to recall the specific project with the unique ID specified from the approval process.

When objects in Workfront are submitted for approval, it is sometimes necessary to recall them from the approval process. When a user recalls a project approval, the project returns to the status it was in prior to the initiation of the approval process. Project ID recallApproval removes the project with the specified ID from the approval process and returns it to its prior status.

Project ID rejectApproval is commonly used to reject an approval associated with a specific project with the unique ID specified by using the userID parameter, the approvalUsername parameter, the approvalPassword parameter, the auditNote parameter, the auditUserIDs parameter, or the sendNoteAsEmail parameter.

Users can create Approval Processes for Projects, Tasks, or Issues as a way to ensure that work is proceeding as desired. If an approval process is associated with a project, the project must be approved according to the approval process before it can move forward. If it is rejected, the status will either return to its previous status or move to another status. based on the Approval Process settings. Project ID rejectApproval allows a designated user to reject the approval of a specific project with the unique ID specified.

Project ID setBudgetToSchedule is commonly used to set the budget of the specific project with the unique ID specified to match the schedule of the project.

When estimating allocation of resources in the Capacity Planner, a user can select to set the budgeted hours to match the planned hours. Project ID setBudgetToSchedule sets the budgeted hours of a specific project with the unique ID specified to match the planned hours of that project.

Project ID unlinkExternalObject is commonly used to unlink an external object from a specific project with the unique ID specified by using the objID parameter, the linkedObjectID parameter, or the integrationType parameter.

Work sometimes requires access to objects (such as documents or folders) that are stored outside of Workfront. These objects can be linked to a Project, so that the object is available from inside Workfront. Project ID unlinkExternalObject unlinks a previously-linked object from a specific project with the unique ID specified.

Project updateBusinessCaseSource

Performs the updateBusinessCaseSource action on the Project object

Task is commonly used to modify a task by performing the acceptWork action, the approveApproval action, the assign action, the assignMultiple action, the bulkCopy action, the bulkMove action, the calculateDataExtension action, the calculateDataExtensions action, the convertToProject action, the linkExternalObject action, the markDone action, the markNotDone action, the move action, the recallApproval action, the rejectApproval action, the replyToAssignment action, the unacceptWork action, the unassign action, the unassignOccurrences action, or the unlinkExternalObject action on the task object.

Task allows you to create, view, or modify Task objects.

Task acceptWork is used to accept work that has been assigned to a Task object.

Performs the acceptWork action on the Task object

Task approveApproval is commonly used to approve an approval that is associated with the task by using the userID parameter, the username parameter, the password parameter, the auditNote parameter, the auditUserIDs parameter, or the sendNoteAsEmail parameter.

Performs the approveApproval action on the Task object

Task assign allows you to assign a Task object to a particular user by using the objID parameter or the objCode parameter.

Performs the assign action on the Task object

Task assignMultiple allows you to assign a Task object to groups of users, such as teams, by using the userIDs parameter, the roleIDs parameter, or the teamID parameter.

Performs the assignMultiple action on the Task object

Task bulkCopy allows you to copy multiple Tasks at once by using the taskIDs parameter, the projectID parameter, the parentID parameter, or the options parameter.

Performs the bulkCopy action on the Task object

Task bulkMove allows you to move multiple Tasks at once by using the taskIDs parameter, the projectID parameter, the parentID parameter, or the options parameter.

Performs the bulkMove action on the Task object

Task calculateDataExtension recalculates expressions in custom form fields.

Custom forms can contain calculated custom fields. These use data expressions and the name of other existing fields. The calculated field evaluates the expression and displays the result. The calculateDataExtension action recalculates the expressions in custom form fields. This can be useful when one of the fields used in the expression is updated, and the value in the calculated field must be updated as well.

Task calculateDataExtensions recalculates expressions in custom form fields.

Custom forms can contain calculated custom fields. These use data expressions and the name of other existing fields. The calculated field evaluates the expression and displays the result. The calculateDataExtensions action recalculates the expressions in custom form fields. This can be useful when one of the fields used in the expression is updated, and the value in the calculated field must be updated as well.

Task convertToProject is used to convert a Task object into a Project object by using the project parameter or the exchangeRate parameter.

Performs the convertToProject action on the Task object

Task linkExternalObject is commonly used to link an external object to the task by using the objID parameter, the linkedObjectID parameter, the integrationType parameter, the URL parameter, or the params parameter.

Work sometimes requires access to objects (such as documents or folders) that are stored outside of Workfront. These objects can be linked to a Task, so that the object is available from inside Workfront. Task linkExternalObjec links an objectTask

Task markDone is used to mark a Task as Done by using the status parameter.

Performs the markDone action on the Task object

Task markNotDone is used to mark a Task as Not Done, using the assignmentID parameter.

Performs the markNotDone action on the Task object

Task move is used to move a Task to a different Project or Parent Task, using the projectID parameter, the parentID parameter, or the options parameter.

Performs the move action on the Task object

Task recallApproval is commonly used to recall the Task from the approval process.

When objects in Workfront are submitted for approval, it is sometimes necessary to recall them from the approval process. When a user recalls a task approval, the task returns to the status it was in prior to the initiation of the approval process. Task recallApproval removes a task from the approval process and returns it to its prior status.

Task rejectApproval is commonly used to reject an approval process that is associated with the Task by using the userID parameter, the username parameter, the password parameter, the auditNote parameter, the auditUserIDs parameter, or the sendNoteAsEmail parameter.

Performs the rejectApproval action on the Task object

Task replyToAssignment

Performs the replyToAssignment action on the Task object

Task unacceptWork

Performs the unacceptWork action on the Task object

Task unassign is used to unassign a User from a Task using the userID parameter.

Performs the unassign action on the Task object

Task unassignOccurrences

Performs the unassignOccurrences action on the Task object

Task unlinkExternalObject is commonly used to unlink an external object from a Task by using the objID parameter, the linkedObjectID parameter, or the integrationType parameter.

Work sometimes requires access to objects (such as documents or folders) that are stored outside of Workfront. These objects can be linked to a Task, so that the object is available from inside Workfront. Task unlinkExternalObject unlinks a previously-linked object from a Task.

Task by ID is commonly used to modify a specific task with the unique ID specified by performing the acceptWork action, the approveApproval action, the assign action, the assignMultiple action, the bulkCopy action, the bulkMove action, the calculateDataExtension action, the calculateDataExtensions action, the convertToProject action, the linkExternalObject action, the markDone action, the markNotDone action, the move action, the recallApproval action, the rejectApproval action, the replyToAssignment action, the unacceptWork action, the unassign action, the unassignOccurrences action, or the unlinkExternalObject action on the task object.

Task by ID allows you to view or modify an existing task object by referencing its unique ID.

Task ID acceptWork Task acceptWork is used to accept work that has been assigned to a specific Task object with the unique ID specified.

Performs the acceptWork action on the Task object

Task approveApproval is commonly used to approve an approval that is associated with the specific task that has the unique ID specified by using the userID parameter, the username parameter, the password parameter, the auditNote parameter, the auditUserIDs parameter, or the sendNoteAsEmail parameter.

Users can create Approval Processes for Projects, Tasks, or Issues as a way to ensure that work is proceeding as desired. If an approval process is associated with a task, the task must be approved according to the approval process before it can move forward. Task ID approveApproval allows a designated user to approve the approval of a specific task with the unique ID specified.

Task assign allows you to assign a specific Task object with the unique ID specified to a particular user by using the objID parameter or the objCode parameter.

Performs the assign action on the Task object

Task ID assignMultiple allows you to assign a specific Task object with the unique ID specified to groups of users, such as teams, by using the userIDs parameter, the roleIDs parameter, or the teamID parameter.

Performs the assignMultiple action on the Task object

Task bulkCopy by Task ID allows you to copy multiple Tasks at once by using the taskIDs parameter, the projectID parameter, the parentID parameter, or the options parameter.

Performs the bulkCopy action on the Task object

Task bulkMove allows you to move multiple Tasks at once by using the taskIDs parameter, the projectID parameter, the parentID parameter, or the options parameter.

Performs the bulkMove action on the Task object

Task ID calculateDataExtension recalculates expressions in custom form fields in the specific Task object with the unique ID specified.

Custom forms can contain calculated custom fields. These use data expressions and the name of other existing fields. The calculated field evaluates the expression and displays the result. The calculateDataExtension action recalculates the expressions in custom form fields. This can be useful when one of the fields used in the expression is updated, and the value in the calculated field must be updated as well.

Task ID calculateDataExtensions recalculates expressions in custom form fields in the specific Task objects with the unique IDs specified.

Custom forms can contain calculated custom fields. These use data expressions and the name of other existing fields. The calculated field evaluates the expression and displays the result. The calculateDataExtensions action recalculates the expressions in custom form fields. This can be useful when one of the fields used in the expression is updated, and the value in the calculated field must be updated as well.

Task convertToProject is used to convert a specific Task object with the unique ID specified into a Project object by using the project parameter or the exchangeRate parameter.

Performs the convertToProject action on the Task object

Task ID linkExternalObject is commonly used to link an external object to the specific task with the unique ID specified by using the objID parameter, the linkedObjectID parameter, the integrationType parameter, the URL parameter, or the params parameter.

Work sometimes requires access to objects (such as documents or folders) that are stored outside of Workfront. These objects can be linked to a Project, so that the object is available from inside Workfront. Task ID linkExternalObject links an object to a specific Task with the unique ID specified.

Task ID markDone is used to mark a specific Task with the unique ID specified as Done by using the status parameter.

Performs the markDone action on the Task object

Task ID markNotDone is used to mark a specific Task with the unique ID specified as Not Done, using the assignmentID parameter

Performs the markNotDone action on the Task object

Task ID move is used to move a specific Task with the unique ID specified to a different Project or Parent Task, using the projectID parameter, the parentID parameter, or the options parameter.

Performs the move action on the Task object

Task recallApproval is commonly used to recall the specific Task with the unique ID specified from the approval process.

When objects in Workfront are submitted for approval, it is sometimes necessary to recall them from the approval process. When a user recalls a task approval, the task returns to the status it was in prior to the initiation of the approval process. Task recallApproval removes a specific task with the unique ID specified from the approval process and returns it to its prior status.

Task ID rejectApproval is commonly used to reject an approval process that is associated with the specific Task with the unique ID specified by using the userID parameter, the username parameter, the password parameter, the auditNote parameter, the auditUserIDs parameter, or the sendNoteAsEmail parameter.

Performs the rejectApproval action on the Task object

Task replyToAssignment

Performs the replyToAssignment action on the Task object

Task unacceptWork

Performs the unacceptWork action on the Task object

Task ID unassign is used to unassign a User from a specific Task with the unique ID specified by using the userID parameter.

Performs the unassign action on the Task object

Task unassignOccurrences

Performs the unassignOccurrences action on the Task object

Task ID unlinkExternalObject is commonly used to unlink an external object from a specific Task with the unique ID specified by using the objID parameter, the linkedObjectID parameter, or the integrationType parameter.

Work sometimes requires access to objects (such as documents or folders) that are stored outside of Workfront. These objects can be linked to a Task, so that the object is available from inside Workfront. Task ID unlinkExternalObject unlinks a previously-linked object from a specific Task with the unique ID specified.

Company Replace OR Company calculateDataExtension

Replaces the Company object OR Performs the calculateDataExtension action on the Company object

Company calculateDataExtension recalculates expressions in custom form fields

Custom forms can contain calculated custom fields. These use data expressions and the name of other existing fields. The calculated field evaluates the expression and displays the result. The calculateDataExtension action recalculates the expressions in custom form fields. This can be useful when one of the fields used in the expression is updated, and the value in the calculated field must be updated as well.

Company Replace

Replaces the Company object

Company Edit OR Company Replace OR Company calculateDataExtension

Modifies the Company having {ID} OR Replaces the Company object OR Performs the calculateDataExtension action on the Company object

Company calculateDataExtension recalculates expressions in custom form fields for the specific Company object with the unique ID specified.

Custom forms can contain calculated custom fields. These use data expressions and the name of other existing fields. The calculated field evaluates the expression and displays the result. The calculateDataExtension action recalculates the expressions in custom form fields. This can be useful when one of the fields used in the expression is updated, and the value in the calculated field must be updated as well.

Company Replace

Replaces the Company object

Document Folders is commonly used to modify a Document Folder by using the getFolderSizeInBytes action, the isLinkedFolder action, the isSmartFolder action, or the unlinkFolders action.

Document Folders allows you to create, view, or modify Document Folders.

Document Folders getFolderSizeInBytes is used to return the size of the folder in bytes, using the folderID parameter, the recursive parameter, or the includeLinked parameter.

Performs the getFolderSizeInBytes action on the Document Folders object

Document Folders isLinkedFolder is used to is used to return a boolean with a value of true if a given Document Folder is linked from a source outside Workfront, and false if it is not.

Performs the isLinkedFolder action on the Document Folders object

Document Folders isSmartFolder is used to is used to return a boolean with a value of true if a given Document Folder is a smart folder, and false if it is not.

Performs the isSmartFolder action on the Document Folders object

Document Folders unlinkFolders

Performs the unlinkFolders action on the Document Folders object

Document Folders by ID is commonly used to modify the specific Document Folder with the unique ID specified by using the Edit action, the getFolderSizeInBytes action, the isLinkedFolder action, the isSmartFolder action, or the unlinkFolders action.

Document Folders by ID allows you to view or modify the specific Document Folder with the unique ID specified.

Document Folders getFolderSizeInBytes by Document Folder ID is used to return the size of the folder that is associated with the specific Document Folder with the unique ID specified in bytes, using the folderID parameter, the recursive parameter, or the includeLinked parameter.

Performs the getFolderSizeInBytes action on the Document Folders object

Document Folders isLinkedFolder by Document Folders ID is used to return a boolean with a value of true if a specific Document Folder with the unique ID specified is linked from a source outside Workfront, and false if it is not.

Performs the isLinkedFolder action on the Document Folders object

Document Folders isSmartFolder by Document Folders ID is used to return a boolean with a value of true if a specific Document Folder with the unique ID specified is a smart folder, and false if it is not.

Performs the isSmartFolder action on the Document Folders object

Document Folders unlinkFolders

Performs the unlinkFolders action on the Document Folders object