EasyVista Service Manager

the easyvista service manager connector integrates with swimlane turbine to create, view and update tickets prerequisites access to the service manager rest api is secured to prevent anyone who does not need access from viewing or manipulating the data this can be performed via token authentication dedicated to the service manager rest api (authentication method service manager (access token)) using an access token see the procedure https //wiki easyvista com/xwiki/bin/view/documentation/integration/webservice%20rest/#procedure restapitokensm via basic authentication using a login and password see the procedure https //wiki easyvista com/xwiki/bin/view/documentation/integration/webservice%20rest/#procedure restapiuser you can call a service manager rest api method using a url in the following format replace {your server} with the server url {your account} with the service manager account used {resource name} with the resource that is called https //{your server}/api/v1/{your account}/{resource name} capabilities this connector provides the following capabilities get ticket post ticket update ticket 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 this action allows information for a specified ticket to be obtained (a ticket includes incident, service request, change request, investment request, problem and event) endpoint url /requests/{{rfc number}} method get input argument name type required description rfc number string required ticket number fields string optional parameter for get ticket formatdate string optional date value 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 href string output field 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 href string output field href dynamic details object output field dynamic details href string output field href effective change date end string output field effective change date end 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" {}, "creation date ut" "2016 11 23t20 19 22 117z" } } ] post ticket this action allows a new ticket to be created (a ticket includes incident, service request, change request, investment request, problem and event) endpoint url /requests method post input argument name type required description requests array optional parameter for post ticket catalog guid string optional identifier for the subject of the ticket catalog code string optional identifier/code for the subject of the ticket assetid string optional unique identifier assettag string optional parameter for post ticket asset name string optional name of the resource urgency id string optional identifier of the urgency level severity id string optional identifier of the severity level external reference string optional parameter for post ticket phone string optional phone number of the requestor requestor identification string optional unique identifier requestor mail string optional parameter for post ticket requestor name string optional name of the resource location id string optional unique identifier location code string optional parameter for post ticket department id string optional unique identifier department code string optional parameter for post ticket recipient id string optional unique identifier recipient identification string optional unique identifier recipient mail string optional parameter for post ticket recipient name string optional name of the resource origin string optional identifier of the origine (examples are phone, email) description string optional description of the object parentrequest string optional parameter for post ticket ci id string optional unique identifier output parameter type description response code number output field response code status string status value href string output field href example \[ { "response code" 201, "status" "created", "response headers" {}, "json body" { "href" "https //{your server}/api/v1/{your account}/requests/i161019 000003" } } ] update ticket this method allows a specified ticket to be modified (a ticket includes incident, service request, change request, investment request, problem and event) endpoint url /requests/{{rfc number}} method put input argument name type required description 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 output parameter type description response code number output field response code status string status value href string output field href example \[ { "response code" 201, "status" "ok", "response headers" {}, "json body" { "href" "https //{your server}/api/v1/{your account}/requests/i161019 000003" } } ] 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