BMC Remedy

this connector allows you to perform update, create, and get operations on incidents please note that this connector only utilizes the remedy rest api, and for endpoints that require services provided by the soap api, you will need to install the generic soap connector, which is available for download from the turbine marketplace the bmc remedy connector provides a seamless connection between turbine and bmc remedy, enabling you to manage incidents efficiently this connector allows you to update, create, and retrieve incident information from bmc remedy, streamlining your incident management processes prerequisites before setting up the connector, ensure that you have the following host the host address of your bmc remedy instance username the username associated with your bmc remedy account password the password for your bmc remedy account additionally, make sure you have the necessary permissions and configuration in bmc remedy to allow api access capabilities this connector provides the following capabilities update incident update the details of an existing incident in bmc remedy fetch incidents fetches the incidents from bmc remedy create incident create a new incident in bmc remedy get incident retrieve the details of an incident from bmc remedy create work order update work order fetch work orders get work order limitations please be aware of the following limitations when using this connector certain features or functionality may not be supported in older or unsupported versions of bmc remedy asset setup to set up the asset for the bmc remedy connector, follow these steps in turbine go to the assets section in turbine click on "create new asset" to add a new asset enter the following details host the host address of your bmc remedy instance username your bmc remedy account username password your bmc remedy account password save the asset configuration 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 actions create incident creates an incident endpoint url /api/arsys/v1/entry/hpd\ incidentinterface create method post input argument name type required description fields string optional parameter for create incident values object required value for the parameter first name string optional name of the resource last name string optional name of the resource templateid string optional unique identifier description string optional parameter for create incident detailed decription string optional parameter for create incident company string optional parameter for create incident urgency string optional parameter for create incident impact string optional parameter for create incident status string optional status value reported source string optional parameter for create incident service type string optional type of the resource assigned support organization string optional parameter for create incident assigned group string optional parameter for create incident assignee string optional parameter for create incident assignee login id string optional unique identifier assigned support company string optional parameter for create incident site group string optional parameter for create incident region string optional parameter for create incident site string optional parameter for create incident status reason string optional status value resolution string optional parameter for create incident z1d action string optional parameter for create incident output parameter type description status code number http status code of the response reason string response reason phrase example \[ { "status code" 200, "response headers" { "content type" "application/json", "date" "thu, 01 jan 2024 00 00 00 gmt" }, "reason" "ok" } ] create work order create work order request endpoint url /api/arsys/v1/entry/woi\ workorderinterface create method post input argument name type required description fields string optional parameter for create work order values object required value for the parameter templateid string optional unique identifier customer first name string optional name of the resource customer last name string optional name of the resource summary string optional parameter for create work order wo type field 01 string optional type of the resource reported source string optional parameter for create work order status string optional status value priority string optional parameter for create work order service type string optional type of the resource impact string optional parameter for create work order urgency string optional parameter for create work order z1d action string required parameter for create work order output parameter type description status code number http status code of the response reason string response reason phrase createdate string date value displayid string unique identifier requestid string unique identifier example \[ { "status code" 200, "response headers" {}, "reason" "", "json body" { "createdate" "2024 02 07t08 08 23", "displayid" "wo0000000001002", "requestid" "wo0000000000702" } } ] fetch incidents fetch all incidents endpoint url /api/arsys/v1/entry/hpd\ incidentinterface/ method get input argument name type required description q string optional parameter for fetch incidents output parameter type description status code number http status code of the response reason string response reason phrase example \[ { "status code" 200, "response headers" { "content type" "application/json", "date" "thu, 01 jan 2024 00 00 00 gmt" }, "reason" "ok" } ] fetch work order fetch all workorders endpoint url /api/arsys/v1/entry/woi\ workorderinterface method get input argument name type required description q string optional parameter for fetch work order output parameter type description status code number http status code of the response reason string response reason phrase example \[ { "status code" 200, "response headers" { "content type" "application/json", "date" "thu, 01 jan 2024 00 00 00 gmt" }, "reason" "ok" } ] get incident get incident endpoint url api/arsys/v1/entry/hpd\ incidentinterface create/{{incidentnumber}} method get input argument name type required description incidentnumber string required unique identifier output parameter type description status code number http status code of the response reason string response reason phrase example \[ { "status code" 200, "response headers" { "content type" "application/json", "date" "thu, 01 jan 2024 00 00 00 gmt" }, "reason" "ok" } ] get work order get work order from bmc remedy endpoint url /api/arsys/v1/entry/woi\ workorderinterface/{{workordernumber}} method get input argument name type required description workordernumber string required parameter for get work order output parameter type description status code number http status code of the response reason string response reason phrase example \[ { "status code" 200, "response headers" { "content type" "application/json", "date" "thu, 01 jan 2024 00 00 00 gmt" }, "reason" "ok" } ] update incident update incident endpoint url api/arsys/v1/entry/hpd\ incidentinterface/{{requestid}} method put input argument name type required description requestid string required unique identifier values object optional value for the parameter first name string optional name of the resource last name string optional name of the resource description string optional parameter for update incident impact string optional parameter for update incident urgency string optional parameter for update incident status string optional status value reported source string optional parameter for update incident service type string optional type of the resource output parameter type description status code number http status code of the response reason string response reason phrase example \[ { "status code" 200, "response headers" { "content type" "application/json", "date" "thu, 01 jan 2024 00 00 00 gmt" }, "reason" "ok" } ] 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