Products
ITSM Service Desk Integrations...
Connection Integration
4 min
activate connects to service desk products through a range of integration methods depending on the capabilities of the target system the preferred approach is through a publicly available and documented api supported connection types include direct api soap web service the api must provide at least the following functions to support a useful integration request logging — ability to create and categorise service requests so they are routed to the correct queue end user accounts — ability to create, update, delete, and query user accounts users must typically exist in the service desk before a ticket can be logged, so activate can create the user automatically as part of its onboarding process integration levels the level of integration depends on the business requirements and the available api functions there are three main levels of integration, listed in order of increasing functionality request / incident logging only activate logs service requests in the service desk when a workflow requires a manual fulfilment step end users can also log manual requests for actions not automated within activate request status synchronisation in addition to request creation, activate monitors the service desk for status updates workflows can pause until a manual fulfilment task is marked complete before continuing with automated steps full integration provides a two way connection between activate and the service desk end users can view ticket details directly in the activate portal, including status and work notes they may also add information or close tickets if permitted required functions by integration type the table below summarises the api functions required for each level of integration true 165,165,165,166left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type legend p – primary requirement o – optional capability