ServiceCallTasks
NOTE This entity works in combination with the Service Call and other Service Call related entities. Before working with this entity, review the topic ServiceCalls.
This entity describes an Autotask project task assigned to a service call. Service calls are instances of time scheduled to perform work for an account. A project task associated with a service call describes work that must be performed during the scheduled time.
Users create tasks through the Projects module and can assign tasks to a service call through the Projects module, the Service Desk module, or Dispatcher's Workshop.
A ServiceCallTasks entity is associated with a ServiceCall entity and requires a serviceCallID value; for additional information, refer to ServiceCalls.
NOTE You can refer to the Online Help to find root and child access URLs of the entity you wish to query. Refer to Finding resource and child access URLs of REST API entities for more information.
Entity details
| Entity Name: | ServiceCallTasks |
|
Entity Path: |
/atservicesrest/v1.0/ServiceCallTasks |
|
Parent Entity: |
|
| Can Create: |
|
| Can Update: | |
| Can Query: |
|
| Can Delete: |
|
| Can Have UDFs: |
IMPORTANT Requests to this entity require special handling. Refer to the Entity URLs and relationships section of this article for details.
Entity URLs and relationships
- If this entity has a Parent relationship, you must perform all Create, Update, and Delete actions on the parent entity.
- If this entity is a child of a parent, you can leverage our Swagger instance to find the URLs you should use in your API calls. For more information, refer to Finding resource and child access URLs of REST API entities.
- To learn how to access Swagger, refer to Using Swagger UI to explore REST API requests.
| Parent | |
| URLs | ServiceCallTasks/query (GET, POST)
ServiceCallTasks/{id} (GET) ServiceCallTasks/query/count (GET) ServiceCallTasks/entityInformation (GET) ServiceCallTasks/entityInformation/fields (GET) ServiceCallTasks/entityInformation/userDefinedFields (GET) |
Conditions and requirements
- This entity will be read-only if the module with which it is associated is not active. For more information, refer to Activations.
- All tasks and tickets associated with a service call must be for the same account. There are no parent/child account loopholes.
- A single task or ticket can be associated with multiple service calls at the same time.
- Any resource can create service calls and associate or disassociate tasks and tickets to service calls.
- API will respect the system setting "Automatically complete service calls when completing the last non-complete task or ticket associated with the service call" . When this rule is enabled and the last open task associated with the service call is set to complete, the service call is set to complete.
Field definitions
About this table
The following table describes the standard Autotask fields for this entity. Refer to the following articles for more information about working with these fields:
- The entityInformation REST API call
- Making basic query calls to the REST API
- Advanced query features of the REST API
To learn how to query picklist endpoints, refer to Understanding picklists.
Notes
- For string datatypes, the number in parentheses ( ) indicates the maximum number of characters allowed.
- LT indicates Local Term.
- If this entity has child collections, they will appear in a Child collection access URLs or an Entity URLs and relationships drop-down in the Entity details section of this article.
- You can call the /query/count/ endpoint of a resource to determine how many records a collection holds.
| Field Name | Datatype | Read-Only | Is Required | Reference Name | Picklist |
|---|---|---|---|---|---|
| id | long |
|
|
||
| serviceCallID | integer |
|
ServiceCalls | ||
| taskID | integer |
|
Tasks |
