var uri = 'https://docs.google.com/forms/d/e/1FAIpQLSdw1y-_z7_O1tSWNFkiDliribqAz5IrqAiJJ6u2KsbEvICTqw/viewform?usp=pp_url&entry.876121135=' + document.location.href; Roles are associated with a department, have a standard billing rate, and are assigned to resources for billing purposes. To attach the new attachment to the notification email, select Include Attachments in Email on the notification panel. Want to learn about upcoming enhancements? Notes can be searched and viewed from one place using the Global Notes Search, accessed from > Home >Search > Global Notes Search or > Reports > Other >General. For additional information, refer to. All users can view attachments they uploaded. The Action Type specifies the type of activity scheduled by the to-do or associated with the note and the actionType View controls where the Note or To-do appears in the user interface. This entity describes an Autotask Ticket. This entity contains the attachments for the ConfigurationItems entity. function SendLinkByMail(href) { Associates a Skill with a Resource to provide information about the skills or abilities of the resource. This entity describes an Autotask Notification, as listed in the Notification History page. Wherever it is available, it tracks essential information about the record. The Autotask REST API Getting started REST API security and authentication REST API revision history Working in the API Introduction to the Autotask REST API Introduction to REST API calls Autotask REST API resources Good to know. Provide feedback for the Documentation team. If the ticket category was configured to display them, additional ticket fields appear in this section on time entries and notes. If you have not clicked the Get current Status link, it will be the date and time you opened the page. For information about dialog boxes and how they differ from browser pages, refer to Minimizing Dialog Boxes. The RMA ticket category cannot be edited through the API. The purchase approval option is available through Autotask procurement. A project defines and organizes a group of related tasks, events, and documents. Access deactivation for version 1.5 began in Q1 2022 and will enter its concluding phases in October 2022. This entity describes an Autotask Company. It mirrors the fields found on the. If a ticket is created or updated with a sub-issue type that is excluded from the associated contract, the ticket's ContractID will be updated to that of the exclusion contract, if it exists. What video game is Charlie playing in Poker Face S01E07? For more information, refer to Notification panel. This field is required unless the supplied ticket category or the user's default ticket category has both the Due Date and Due Time configured. This entity describes an Autotask To-Do, a scheduled item associated with a Company that appears on the user's Autotask calendar. This entity represents associations between assets and documents in Autotask. A SubscriptionPeriod stores the information for an individual billing period item associated with an Autotask Subscription. This entity represents articles created by Knowledgebase users in Autotask. The Autotask REST API presents selected Autotask resources as programming objects that allow the client to perform actions on them. Edit: oh and for the REST API, the ID field isn't needed, just so you are aware. TicketCategory default values will be applied unless another value is passed in. 2. This entity describes an internal cost created for a resource-role combination for time entries on a specified contract. Autotaskwill automatically assign the record number that follows the prefix. How can I explain to my manager that a project he wishes to undertake cannot be performed by the team? NOTE Although the Autotask interface now allows multiple resources on a ticket, the current versions of the Web Services API do not support this feature. function SendLinkByMail(href) { On update, a TicketCategory cannot be updated to another TicketCategory that is inactive. On notes that can become a notification email, attachments can be included. Autotask users manage Tickets through a number of modules including Service Desk, Home, CRM, and Contracts. If the ticket category = 'RMA', the InstalledProductID is required. In Autotask, you can create ticket categories that are identified as API-Only. If an association is removed from a resource and that pairing is set as the default, that default is not removed. According to their documentation it requires the URI https://webservices4.autotask.net/atservicesrest/v1.0/Tickets and then the body contains the JSON formatted data: But this doesn't seem to work either and Datto are taking forever to respond to support tickets these days. Review the setting of the Internal Only check box. A resource can be associated with multiple LOBs; entities cannot. This entity enables your authorized third-party apps or modules to query the categories that can be associated with an opportunity in Autotask. Any entities or attachments that the account creates will be attributed to "APIUser." For detailed information, refer to The task or ticket stopwatch. The status code getting printed here is 401! Need troubleshooting help? Some users wanted a benchmark of the new API. You can make this a default setting. If the ticket category has only the due date or only the due time configured, then the API Ticket.DueDateTime will be required, and not supplying a value will return an error message. This entity's purpose is to describe a location associated with an Autotask Quote that defines address information for a shipToLocationID and/or billToLocationID. Attachments are external documents that are associated with an Autotask Account, Task, Ticket, Task or Ticket Note, Time Entry, Asset, Asset Note, Project, or Opportunity entity. Thanks for your feedback. With the granular ticket security features implemented in the 2016.1 release, the API Ticket entity will respect the View, Add, and Edit permissions assigned to the logged in end user, EXCEPT the API will not respect the 'Mine + Accounts' setting. Refer to Autotask Integration and Monitors. If the Contract Service or Bundle is associated to an SLA, then use that ID. This entity's purpose is to describe a Resource - Role relationship. This entity describes notes created by an Autotask user and associated with a Product entity. Head on over to our Community Forum! This entity describes visual identifiers that you can use to categorize and search for Companies. This entity's purpose is to describe a modular component that can be added to any ticket or task. Did any DOS compatibility layers exist for any UNIX-like systems before DOS started to become outmoded? The ArticlePlainTextContent entity contains the plain text version of body content held by a Knowledgebase article. 2. A Department is an association the application can use to manage resources, especially when assigning project tasks. For example, when updating an entity, you may not be able to update all fields within the entity. Resource access URLs for all entities appear in the next section of this article. This entity's purpose is to describe a Work Type billing (or allocation) code that has been excluded from a Contract. For information about the currently-available entities and fields, consult the individual descriptions in the section of this article. The Entities list provides a link to additional information about the entity and its standard Autotask fields. This entity's purpose is to describe a template that defines the content and appearance of an Autotask Invoice. If you select a different note type, keep in mind that it might be set to a different Publish option. Here is the code I tried (after authenticating). I have taken the Resource location "15" from the below page on autotask because while creating the api user I have selected the location as "Headquarters". The Note Type field defaults to Task Summary. Basic Incoming Email Processing is available to all Autotask customers at no additional cost, and includes: The Add Ticket Email Service (ATES) mailbox, which is already set up One additional active custom mailbox. While this is not possible in the UI, in the API, you can create tickets with a ticket category of 'API.'. Every resource is associated with a location. This entity describes the Resource and Role through the Queue association. If there is no Asset SLA, then check the Contract Service or Bundle SLA. It has code to get popular entities like accounts, tickets, contacts etc. Have an idea for a new feature? About note types. This entity represents company (account)categories in Autotask. IMPORTANT If the New/Edit Time Entry or New/Edit Note dialog is saved on the Edit Task or Edit Ticket page, both the details panel and main canvas will be updated. Currently, the API provides the following actions: GET, PUT, PATCH, POST, and DELETE. If you send the content back, the Rich Text and all images that it contains will be lost. It outlines the steps that must be performed to complete the ticket or task. The time zone and holiday set of the associated location are applied to the resource's time entries and schedules. If you open this dialog box or page from the Edit [Entity] page, the section containing this field will not appear, and this field will not be editable. The function of this entity is to describe the default settings for fields associated with the specified ticket category. If the setting Enable [Entity] Stopwatch is cleared for the entity category, the stopwatch will not appear. The Web Services API stores and returns all time data in Coordinated Universal Time (UTC). /*]]>*/Want to tell us more? This entity manages the tags associated with tickets in Autotask. This entity's purpose is to describe a geographic area where billing items have the same tax rate. IMPORTANT The SOAP API entered a limited enhancement phase in Q4 2020. These are referred to as Reference fields. On entities like ticket, task, note, and to-do, the Description field is a core part of the data record. Refer to WebhookExcludedResources (REST). If a ticket already has checklist items, the checklist library is appended to the end of the list of checklist items. ProjectID must be associated with the same Account as the Ticket (Ticket.AccountID). and not visible to the API user when inspecting the Extension Callout on edit and when creating a new Extension Callout. If the asset is associated to an SLA, then use that ID. CreatorResourceID can return a ContactID. This entity describes an Autotask Quote Item. In addition, a stumbling block I noted was to double check the AssignedResourceID has the actual role assigned via AssignedResourceRoleID. The ticket SLA is defaulted in using the following logic: Check the asset. This check box is enabled when the Internal check box is selected. Also create Note/Attachment on # incident(s) (tickets only). A billing item may or may not be included in an invoice and billed to the customer. Connect and share knowledge within a single location that is structured and easy to search. Such ticket categories are hidden everywhere you select a ticket category . IMPORTANT Except in the case of certain entities, when the APIreceives a request to update a field that contains Rich Text, the APIwill update the text-only version of the field and overwrite the data in the Rich Text field with plain text. What sort of strategies would a medieval military use against a fantasy giant? resource and child collection access URLs, Resource and child collection access URLs, Finding resource and child access URLs of REST API entities, Allow impersonation of resources with this security level, ArticleConfigurationItemCategoryAssociations, WebhookExcludedResources (REST), ConfigurationItemBillingProductAssociations, Using Swagger UIto explore REST API requests, Need troubleshooting help? The function of this entity is to describe the Resource - Service Desk Role association and takes some functionality from the ResourceRoleQueue entity, since Resource - Queue associations no longer require a Role association. Append to Resolution on # incident(s) (tickets only). For example, although the client can create certain resources, not all resources accept a create call. To subscribe to this RSS feed, copy and paste this URL into your RSS reader. TicketType must = Incident before the ticket can be associated with a ProblemTicketID. You might want to work with Autotask API's own Visual Studio solutions which are linked on their web services page. I changed some values just in case they are sensitive. This entity's purpose is to describe a billing Work Type (Allocation Code) that is excluded from the contract to which the set applies. Refer to. For example, when creating a Ticket Note you must supply the id for the Ticket that the note will be associated with. This object associates a Product entity with a PurchaseOrder entity. Find centralized, trusted content and collaborate around the technologies you use most. If the API receives an invalid prefix, it will automatically generate one and assign it to the resource. Click New; Tip - click the images to make them larger Billing milestones define tangible work or measured progress that must be completed before billing can take place. This entity describes an Autotask project task assigned to a service call. If a ticket has TicketType not equal to 'Change Request' and it has data in one or more the fields that are exclusive to Change Request tickets, then the ticket can be saved. window.open(uri); 5. This entity contains the categories that hold Knowledgebase articles in Autotask. The fields that do appear show the following differences: A Keep Current option is available and is the default. It was a requirement for soap though as the other reply says. Only form templates that are available to all selected tickets categories can be selected. If the ticket does not have a value for a role, the check box for that recipient will still be enabled, because they can still be selected on the Notification panel. Do not confuse it with Currency local term selection, which is not available when using Multi-currency. For child collection access URLs and specific entity names, refer to the individual articles linked in the List of Entities section of this article. DocumentConfigurationItemCategoryAssociations. This entity describes an Autotask resource assigned to a ticket that is assigned to a service call. [CDATA[*/ This entity's purpose is to describe a serial number associated with an Inventory Item. Head on over to our Community Forum! This field is editable for tickets whose ticket category is 'RMA.' The function of this entity is to describe the number of units of a specific service bundle with an association to a Recurring Service contract for a specific date range.