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 parameters fields string optional parameters for the create incident action values object optional value for the parameter values first name string optional name of the resource values last name string optional name of the resource values templateid string optional unique identifier values description string optional value for the parameter values detailed decription string optional value for the parameter values company string optional value for the parameter values urgency string optional value for the parameter values impact string optional value for the parameter values status string optional status value values reported source string optional value for the parameter values service type string optional type of the resource values assigned support organization string optional value for the parameter values assigned group string optional value for the parameter values assignee string optional value for the parameter values assignee login id string optional unique identifier values assigned support company string optional value for the parameter values site group string optional value for the parameter values region string optional value for the parameter values site string optional value for the parameter values status reason string optional status value values resolution string optional value for the parameter values z1d action string optional value for the parameter input example {"parameters" {"fields" "values(incident entry id,incident number,create date)"},"json body" {"values" {"first name" "first name","last name" "last name","templateid" "template instance id","description" "summary","detailed decription" "details","company" "company","urgency" "urgency","impact" "impact","status" "status","reported source" "reported source","service type" "service type","assigned support organization" "assigned support organization","assigned group" "assigned support group name","assignee" "assignee","assignee login id" "assignee login id","assigned support company" "assigned support company","site group" "site group","region" "region","site" "site","status reason" "reason","resolution" "resolution","z1d action" "create"}}} output parameter type description status code number http status code of the response reason string response reason phrase output example {} create work order create work order request endpoint url /api/arsys/v1/entry/woi\ workorderinterface create method post input argument name type required description parameters fields string optional parameters for the create work order action values object optional value for the parameter values templateid string optional unique identifier values customer first name string optional name of the resource values customer last name string optional name of the resource values summary string optional value for the parameter values wo type field 01 string optional type of the resource values reported source string optional value for the parameter values status string optional status value values priority string optional value for the parameter values service type string optional type of the resource values impact string optional value for the parameter values urgency string optional value for the parameter values z1d action string required value for the parameter input example {"parameters" {"fields" "fields=values(workorder id,requestid)"},"json body" {"values" {"templateid" "template guid","customer first name" "customer first name","customer last name" "customer last name","summary" "summary","wo type field 01" "","reported source" "detailed description","status" "status","priority" "priority","service type" "","impact" "","urgency" "","z1d action" "create"}}} 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 output 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 input example {"q" ""} output parameter type description status code number http status code of the response reason string response reason phrase output example {} 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 input example {"q" ""} output parameter type description status code number http status code of the response reason string response reason phrase output example {} 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 input example {"incidentnumber" ""} output parameter type description status code number http status code of the response reason string response reason phrase output example {} 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 input example {"workordernumber" ""} output parameter type description status code number http status code of the response reason string response reason phrase output example {} update incident update incident endpoint url api/arsys/v1/entry/hpd\ incidentinterface/{{requestid}} method put input argument name type required description path parameters requestid string required parameters for the update incident action values object optional value for the parameter values first name string optional name of the resource values last name string optional name of the resource values description string optional value for the parameter values impact string optional value for the parameter values urgency string optional value for the parameter values status string optional status value values reported source string optional value for the parameter values service type string optional type of the resource input example {"json body" {"values" {"first name" "allen","last name" "allbrook","description" "rest api incident creation","impact" "1 extensive/widespread","urgency" "1 critical","status" "assigned","reported source" "direct input","service type" "user service restoration"}},"path parameters" {"requestid" "inc0000"}} output parameter type description status code number http status code of the response reason string response reason phrase output example {} 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