EasyVista Service Manager

easyvista service manager is an it service management solution that automates and streamlines it service delivery easyvista service manager is a comprehensive it service management (itsm) platform that streamlines service delivery and support this connector enables seamless integration with swimlane turbine, allowing users to automate the creation, retrieval, and updating of tickets within easyvista by leveraging this integration, swimlane turbine users can enhance their itsm processes, reduce manual effort, and improve response times, ultimately leading to more efficient incident management and service delivery the easyvista service manager connector integrates with swimlane turbine to create, view and update tickets prerequisites before you can use the easyvista service manager connector for turbine, you'll need access to the easyvista api this requires the following http bearer authentication using the following parameters url the endpoint url for accessing easyvista service manager token name the bearer token used for authentication http basic authentication using the following parameters url the endpoint url for accessing easyvista service manager username the username for authenticating with easyvista service manager password the password associated with the username for authentication capabilities this connector provides the following capabilities get ticket post ticket update ticket notes easyvista service manager rest api documentation can be found api documentation https //wiki easyvista com/xwiki/bin/view/documentation/integration/webservice%20rest/rest%20api%20 %20create%20an%20incident request/ in the case of post ticket https //wiki easyvista com/xwiki/bin/view/documentation/integration/webservice%20rest/rest%20api%20 %20create%20an%20incident request/ , you must use at least one of the json objects below in the body of the http request the subject can be specified with catalog guid (use in preference) or catalog code if catalog guid is wrong, the process stops without reading catalog code additional documentation easyvista service manager connector documentation https //docs swimlane com/connectors/easyvista service managereasyvista service manager api documentation https //wiki easyvista com/xwiki/bin/view/documentation/integration/webservice%20rest/rest%20api%20 %20create%20an%20incident request/ configurations http basic authentication authenticates using username and password configuration parameters parameter description type required url a url to the target host string required username username string required password password string required verify ssl verify ssl certificate boolean optional http proxy a proxy to route requests through string optional http bearer authentication authenticates using bearer token configuration parameters parameter description type required url a url to the target host string required token token string required verify ssl verify ssl certificate boolean optional http proxy a proxy to route requests through string optional actions get ticket obtain detailed information for a specified ticket in easyvista service manager, including incidents, service requests, change requests, investment requests, problems, and events requires the rfc number as a path parameter endpoint url /requests/{{rfc number}} method get input argument name type required description path parameters rfc number string required ticket number parameters fields string optional parameters for the get ticket action parameters formatdate string optional parameters for the get ticket action input example {"parameters" {"fields" "available field 1,comment","formatdate" "/m/y ==> last update format friday/nov/2018"},"path parameters" {"rfc number" "s161123 000034"}} output parameter type description status code number http status code of the response status string status value href string output field href analytical charge path string output field analytical charge path available field 1 string output field available field 1 available field 2 string output field available field 2 available field 3 string output field available field 3 available field 4 string output field available field 4 available field 5 string output field available field 5 available field 6 string output field available field 6 budget effective string output field budget effective budget id string unique identifier budget planned string output field budget planned can be duplicated string output field can be duplicated click 2 get install result string result of the operation comment object output field comment comment href string output field comment href creation date ut string output field creation date ut delay string output field delay department path string output field department path description object output field description description href string output field description href dynamic details object output field dynamic details dynamic details href string output field dynamic details href effective change date end string output field effective change date end output example {"status code" 200,"status" "ok","response headers" {},"json body" {"href" "https //{your server}/api/v1/{your account}/requests/s161123 000034","analytical charge path" "","available field 1" "","available field 2" "","available field 3" "","available field 4" "","available field 5" "","available field 6" "","budget effective" "","budget id" "","budget planned" "","can be duplicated" "0","click 2 get install result" "","comment" {"href" "https //{your server}/api/v1/{your account}/requests/comm post ticket create a new ticket in easyvista service manager, including incidents, service requests, change requests, investment requests, problems, and events endpoint url /requests method post input argument name type required description requests array optional parameter for post ticket requests catalog guid string optional identifier for the subject of the ticket requests catalog code string optional identifier/code for the subject of the ticket requests assetid string optional unique identifier requests assettag string optional parameter for post ticket requests asset name string optional name of the resource requests urgency id string optional identifier of the urgency level requests severity id string optional identifier of the severity level requests external reference string optional parameter for post ticket requests phone string optional phone number of the requestor requests requestor identification string optional unique identifier requests requestor mail string optional parameter for post ticket requests requestor name string optional name of the resource requests location id string optional unique identifier requests location code string optional parameter for post ticket requests department id string optional unique identifier requests department code string optional parameter for post ticket requests recipient id string optional unique identifier requests recipient identification string optional unique identifier requests recipient mail string optional parameter for post ticket requests recipient name string optional name of the resource requests origin string optional identifier of the origine (examples are phone, email) requests description string optional description of the object requests parentrequest string optional parameter for post ticket requests ci id string optional unique identifier input example {"json body" {"requests" \[{"catalog code" "46","catalog guid" "44","assetid" "","assettag" "","asset name" "","urgency id" "1","severity id" "40","external reference" "","phone" "93 63 65 23","requestor identification" "","requestor mail" "morley\@itassetservices com","requestor name" "","location id" "","location code" "","department id" "","department code" "","recipient id" "","recipient identification" "","recipient mail" "leblanc\@itassetservices com","recipient name" "","origin" "3","description" "request created via rest api","parentrequest" "","ci id" "","ci asset tag" "","ci name" "","submit date" "","impact id" 8,"title" ""}]}} output parameter type description response code number output field response code status string status value href string output field href output example {"response code" 201,"status" "created","response headers" {},"json body" {"href" "https //{your server}/api/v1/{your account}/requests/i161019 000003"}} update ticket modify a specified ticket in easyvista service manager, including incident, service request, change request, investment request, problem, and event requires the rfc number as a path parameter endpoint url /requests/{{rfc number}} method put input argument name type required description path parameters rfc number string required ticket number analytical charge id string optional unique identifier asset id number optional unique identifier asset serial string optional parameter for update ticket asset tag string optional parameter for update ticket available field 1 string optional parameter for update ticket ci string optional parameter for update ticket ci id number optional unique identifier ci serial string optional parameter for update ticket comment string optional parameter for update ticket continuity plan id string optional unique identifier description string optional parameter for update ticket external reference string optional parameter for update ticket impact id number optional unique identifier known problems id number optional unique identifier net price cur id string optional unique identifier origin tool id number optional unique identifier owner id string optional unique identifier owning group id string optional unique identifier release id string optional unique identifier rental net price cur id string optional unique identifier request origin id string optional unique identifier requestor phone string optional parameter for update ticket root cause id string optional unique identifier submit date ut string optional parameter for update ticket input example {"json body" {"analytical charge id" "","asset id" 27618,"asset serial" "mgtrdf","asset tag" "10164r","available field 1" "available field 1 test","ci" "sql rdb it ","ci id" 1,"ci serial" "kd78qgjyu","comment" "here, your comment","continuity plan id" "cp01","description" "here, your description","external reference" "external ref test","impact id" 1,"known problems id" 1,"net price cur id" "eur","origin tool id" 1,"owner id" "leblanc, fred","owning group id" "desktop usa","release id" "rel01","rental net price cur id" "eur","request origin id" "fax","requestor phone" "93 63 65 23","root cause id" "virus","submit date ut" "07/22/2017","system id" "supervisor","urgency id" 1},"path parameters" {"rfc number" "s161123 000034"}} output parameter type description response code number output field response code status string status value href string output field href output example {"response code" 201,"status" "ok","response headers" {},"json body" {"href" "https //{your server}/api/v1/{your account}/requests/i161019 000003"}} response headers header description example content type the media type of the resource application/json date the date and time at which the message was originated thu, 01 jan 2024 00 00 00 gmt