The time zone and holiday set of the associated location are applied to the resource's time entries and schedules. This entity describes a ticket category applied to tickets in Autotask to specify features and fields that appear on the ticket detail. How to handle a hobby that makes income in US. /*Autotask: Ticketing and Asset Tracking Integration 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. Refer to Creating Knowledgebase articles from tickets. This entity's purpose is to describe a deliverable item that represents a pre-defined unit of work performed for a set price and billed at regular intervals; for example, a 'Disk Backup' performed for one computer. If a form template uses a value or provides content that is not allowed in a field by the category or the user's security settings, the field will not be updated. This entity describes an individual business unit that has an association with a company in Autotask. You can only associate it with a Quote entity. This entity's purpose is to describe a note created by an Autotask user and associated with a Ticket entity. What could be the reason? It allows you to compensate for the Block Hour fixed rate by applying a multiplier to specific role rates. Ticket - Autotask To learn more, refer to The Rich Text editor. This entity represents time off requests submitted by Autotaskusers. This entity contains attachments for Knowledgebase articles in Autotask. Logon to the Datto (AutoTask) PSA. From the pull-down menu, The note will only be added to the incidents of problem tickets, not incidents of Change Request tickets. This entity describes one or more account contacts assigned to a Ticket, other than the Ticket Contact (Ticket.contactID). and not visible to the API user when inspecting the Extension Callout on edit and when creating a new Extension Callout. You can also retrieve this information with the Web Services API call The getEntityInfo() SOAPAPIcall. [CDATA[*/ To attach the new attachment to the notification email, select Include Attachments in Email on the notification panel. This entity records existing associations between tags and Knowledgebase articles in Autotask. The API user security level has access to contact impersonation for tickets. To verify and configure these settings perform the following steps. An API user is a special type of account required for communication with the Autotask API. If the ticket category is associated to an SLA, then use that ID. This entity describes a transaction where a specified quantity of an InventoryProducts or an InventoryStockedItems entity is transferred from the items current InventoryLocation to a different InventoryLocation. Can Query is not included because non-queryable fields are listed under a separate heading. Contracts specify a billing arrangement with a Company. This check box only appears for notes and time entries on problem tickets associated with one or more incidents. /**/Want to tell us more? I changed some values just in case they are sensitive. Visit our SOAPAPIlifecycle FAQ article to learn more. This entity's purpose is to describe a cost associated with an Autotask Project. Want to talk about it? This entity describes an Autotask Allocation Code. The returned body will be super useful going forward if you can get it though! The following table describes the standard Autotask field objects for this entity. This entity describes an Autotask Quote Item. This entity's role is to describe any sort of note created by an Autotask user and associated with a Company entity as opposed to a Ticket Note. import requests. This object associates a Product entity with a PurchaseOrder entity. This entity describes notes created by an Autotask user and associated with a Task entity. The company handles all billing for the business unit. rev2023.3.3.43278. Checklists are an optional feature on the ticket page that display numbered items to be completed in order to finish work on a ticket. In Autotask, you can create ticket categories that are identified as API-Only. The status field describes how close a ticket is to resolution, or how close a task is to completion. It also controls if this section is automatically expanded when the time entry or note is opened for creating or editing. In Autotask, sales orders are associated to Opportunities. Cost items can be billable or non-billable. Contact Groups are an association of contacts, from one or more companies, that allow PSA users to send bulk email and create notes and/or to-dos simultaneously for all included contacts. 5. For a list of all currently available entities, refer to the , or check the Online Help's table of contents. If you set the status of selected tickets to Complete, and one or more tickets have incomplete to-dos, a confirmation message will ask if you want to complete associated to-dos. Thanks for your feedback. This entity contains notes for Knowledgebase articles in Autotask. Using notes in Autotask The Ticket entity will support the Ticket Category: The following fields are not editable when ticket category is RMA: AccountID, InstalledProductID, TicketType. This entity represents associations between asset categories and documents in Autotask. Set up the Autotask trigger, and make magic happen automatically in Microsoft Excel. Task & Ticket Statuses - Autotask The Autotask REST API This entity contains attachments for documents in Autotask. The selected recipients are added to the To: field; CC: and BCC: fields are not populated. For example, when creating a Ticket Note you must supply the id for the Ticket that the note will be associated with. This check box only appears for notes and time entries on problem tickets associated with one or more incidents. The Status defaults to the current status of the parent entity when the page or dialog box is opened. Does anyone have sample code for how to create a ticket using the REST API. Visit our SOAP API lifecycle FAQ article to learn more. When you enable the Organizational Structure feature in Autotask, this object describes an Autotask Resource association with an organizational structure pairing of OrganizationalLevel1 and OrganizationalLevel2 (OrganizationalLevelAssociation entity). Invoices include Billing Items that have been approved and posted and are being billed to a customer or presented for information purposes only. Currently, the API provides the following actions: GET, PUT, PATCH, POST, and DELETE. The change request approval process is part of the Autotask Change Management feature set. To obtain complete field information specific to your Autotask implementation, use theGETAPIcalls described in the resource and child collection access URLs section of this document. This entity's purpose is to describe a billing milestone for an Autotask Fixed Price type Contract. Notes have a property called Note Type. In the Quick Notification (Notify via "To") section, you can use check boxes to quickly add common role-based notification recipients to the note or time entry notification email. Create an API account in Autotask - Partner Docs You can update an existing Ticket that has a Resource + Role combination that uses an inactive role. ConfigurationItemSslSubjectAlternativeName. Automatically Close Ticket using the API Extension Callout - N-able Incidents on Change Request tickets will not be updated. The application records an error when the maximum number of retries (5) have occurred for an event, but the payload could not be delivered. IssueType and SubIssueType are never required in the API. But does anyone know what should be used to create a ticket? A ticket can have additional assets even if there is no primary asset. TicketCategory - Autotask To view attachments uploaded by other users, Can view time entry internal notes, internal notes, and internal attachments (on Ticket Detail and CRM Detail screens) or Can view time entry internal notes, internal notes, and internal attachments (on Task Detail screens) About Autotask Integration and Configuration - WatchGuard This entity describes an Autotask Task. Thanks for your feedback. ProjectID must be associated with the same Account as the Ticket (Ticket.AccountID).