Cherwell Service Management

the cherwell service management connector allows for seamless integration with swimlane turbine, enabling the automation of incident and security event management cherwell service management is a comprehensive it service management (itsm) solution that enables organizations to automate service desk operations and manage it services efficiently this connector allows swimlane turbine users to integrate with cherwell, providing streamlined incident management, security event handling, and ticketing capabilities directly within the swimlane platform enhance your security automation workflows with the ability to create, update, close, and retrieve tickets and security events, ensuring rapid response and resolution of it issues and security incidents asset setup or prerequisites to utilize the cherwell service management connector within swimlane turbine, ensure you have the following prerequisites custom authentication with cherwell credentials, which includes cherwell server url the base url for your cherwell service management instance username your cherwell user account name password your cherwell account password api client id the unique identifier for your api client registered in cherwell capabilities the cherwell service management integration provides the following capabilities get current tickets by business object get current tickets for incidents and security events get business object fields create, close, update, or retrieve an incident by id create, close, update, or retrieve a security event by id notes about get current tickets filters list of available operators operator description eq equals specified value gt greater than specified value lt less than specified value contains contains specified value startswith starts with specified value filters can be built as follows field,operator,value for example; incidentid,eq,102401 this filter should be passed to querystrings input field configurations cherwell asset authenticates using cherwell credentials configuration parameters parameter description type required url the url of the cherwell instance string required username account username string required password account password string required client id api client id string required verify ssl verify ssl certificate boolean optional http proxy a proxy to route requests through string optional actions close security event closes a specified security event in cherwell service management using the provided seceventid input argument name type required description seceventid string required the unique identifier for the security event that needs to be closed output parameter type description status code number http status code of the response reason string response reason phrase example \[ { "status code" 200, "reason" "ok", "response headers" {}, "json body" {} } ] close ticket closes an incident ticket in cherwell service management using the provided incidentid input argument name type required description incidentid string required the unique identifier for the incident ticket that needs to be closed output parameter type description status code number http status code of the response reason string response reason phrase example \[ { "status code" 200, "reason" "ok", "response headers" {}, "json body" {} } ] create security event create a new security event in cherwell service management with specified priority, source, date/time, and details input argument name type required description priority string required the priority level of the security event allowed values are low, normal, and high eventsource string required the source or origin of the security event eventdatetime string required the date and time when the security event occurred details string required additional information or description of the security event recid string optional a unique identifier for the security event record eventoperationstypeid string optional the id of the event operations type eventoperationstypename string optional the name of the event operations type createddatetime string optional the date and time when the event was created createdby string optional the name of the person who created the event createdbyid string optional the id of the person who created the event createdculture string optional the culture or language settings under which the event was created lastmoddatetime string optional the date and time when the event was last modified lastmodby string optional the person or system that last modified the event lastmodbyid string optional the identifier of the person or system that last modified the event ownedby string optional the name of the person or team responsible for managing the event ownedbyid string optional the identifier of the person or team responsible for the event ownedbyteam string optional the team responsible for managing the security event ownedbyteamid string optional the identifier for the team managing the event eventoperationsid string optional the identifier of the event operational process reportedby string optional the name of the person or entity that reported the security event reportedbyemail string optional the email address of the person who reported the event reportedbyphone string optional the phone number of the person who reported the event discovery string optional information about how the event was discovered eventci string optional the configuration item related to the security event status string optional the current status of the security event output parameter type description status code number http status code of the response reason string response reason phrase example \[ { "status code" 200, "reason" "ok", "response headers" {}, "json body" {} } ] create ticket generates a new incident ticket in cherwell service management with details like customer name, description, priority, service, and source input argument name type required description customerdisplayname string required the name of the customer reporting the issue (e g , max megalos) summary string optional a brief summary of the issue description string required a detailed description of the problem (e g , cannot print to network printer) priority string required the urgency of the issue, ranging from low to high service string required the affected service, such as e mail, desktop management, or network services category string optional a broad classification of the issue, covering areas like network access, anti virus, or misc software subcategory string optional a more specific breakdown of the category, such as new account, password reset, or request new computer source string required how the issue was reported, whether via walk in, e mail, phone, or another method lastmodbyid string optional the id of the user who last modified the ticket createdbyemail string optional the email address of the user who created the ticket (e g , user\@example com mailto\ user\@example com ) comments string optional additional comments or updates about the ticket (e g , withdrawn by henri bryce) recurringincident string optional whether the incident is recurring (e g , 'false') reviewbydeadline string optional a deadline by which the incident should be reviewed (e g , 2/14/2018 12 00 00 am) customertypeid string optional the customer type identifier nextstatusonestep string optional information about the next status step for the ticket ownedbymanager string optional the name of the manager responsible for the ticket (e g , gina mehra) level3escalationteam string optional the team handling the third level escalation (e g , 3rd level support) tasksonhold string optional whether tasks related to the incident are on hold (e g , 'false') nextstatustext string optional the next status text for the incident sla key string optional the service level agreement key (e g , platinum incident) error message string optional any error messages associated with the ticket cidowntimeinminutes string optional the duration of configuration item downtime, in minutes (e g , 300) withdraw string optional whether the incident has been withdrawn (e g , 'false') customersubscriptionlevel string optional the customer subscription level (e g , gold) sctfired string optional whether an sct (service configuration template) was fired output parameter type description status code number http status code of the response reason string response reason phrase example \[ { "status code" 200, "reason" "ok", "response headers" {}, "json body" {} } ] get business object fields retrieves field definitions for a specified business object in cherwell service management using the business object name input argument name type required description busobjname string required specifies the name of the business object for which field definitions are to be retrieved this value should match an existing business object in cherwell service management, such as 'incident' or 'securityevent' the field is required for the action to function properly output parameter type description status code number http status code of the response reason string response reason phrase example \[ { "status code" 200, "reason" "ok", "response headers" {}, "json body" {} } ] get current incidents retrieve a list of current incidents from cherwell service management without requiring additional parameters input argument name type required description querystrings string optional allows for optional filtering of incidents based on specific criteria for example, to filter incidents with a specific incident id, use incidentid,eq,102401 limit number optional specifies the maximum number of incidents to retrieve in the response this field is optional and helps control the size of the result set output parameter type description status code number http status code of the response reason string response reason phrase example \[ { "status code" 200, "reason" "ok", "response headers" {}, "json body" {} } ] get current security events retrieve the latest security events from cherwell service management for analysis and tracking input argument name type required description querystrings string optional allows for optional filtering of security events based on specific criteria for instance, you can filter by incident id using incidentid,eq,102401 limit number optional specifies the maximum number of security events to return in the response this optional field helps manage the volume of data returned by the action output parameter type description status code number http status code of the response reason string response reason phrase example \[ { "status code" 200, "reason" "ok", "response headers" {}, "json body" {} } ] get current tickets retrieve all current tickets from cherwell service management using the specified business object name input argument name type required description busobjname string required the name of the cherwell business object from which tickets will be retrieved querystrings string optional query strings to filter the search the format should be a comma separated list specifying the field, operator, and value limit number optional the maximum number of tickets to retrieve in the response output parameter type description status code number http status code of the response reason string response reason phrase example \[ { "status code" 200, "reason" "ok", "response headers" {}, "json body" {} } ] get security event by id retrieve detailed information for a specific security event by its unique id in cherwell service management input argument name type required description seceventid string required the unique identifier for the security event that you want to retrieve output parameter type description status code number http status code of the response reason string response reason phrase example \[ { "status code" 200, "reason" "ok", "response headers" {}, "json body" {} } ] get ticket by id retrieve detailed information for a specific incident ticket in cherwell service management using the incidentid input argument name type required description incidentid string required the unique identifier for the incident ticket you want to retrieve output parameter type description status code number http status code of the response reason string response reason phrase example \[ { "status code" 200, "reason" "ok", "response headers" {}, "json body" {} } ] update incident updates an existing incident in cherwell service management using the provided incidentid input argument name type required description incidentid string required updates an existing incident in cherwell service management using the provided incident id customerdisplayname string optional specifies the display name of the customer description string optional provides a description of the incident or issue priority string optional defines the priority level of the incident service string optional specifies the service involved in the incident category string optional categorizes the type of issue subcategory string optional provides a more specific categorization under the main category source string optional identifies the source of the incident lastmodbyid string optional indicates the id of the user who last modified the incident createdbyemail string optional provides the email address of the user who created the incident comments string optional allows for additional comments or notes on the incident recurringincident string optional specifies if the incident is recurring reviewbydeadline string optional sets a deadline for reviewing the incident customertypeid string optional identifies the type of customer nextstatusonestep string optional defines the next status step for the incident ownedbymanager string optional specifies the manager who owns the incident level3escalationteam string optional indicates the team responsible for level 3 escalation tasksonhold string optional specifies whether tasks are on hold for this incident nextstatustext string optional provides text for the next status update sla key string optional identifies the sla key associated with the incident error message string optional provides an error message, if applicable cidowntimeinminutes string optional tracks the downtime of the configuration item in minutes withdraw string optional indicates whether the incident has been withdrawn customersubscriptionlevel string optional defines the customer's subscription level sctfired string optional tracks if an sct (service catalog template) was triggered output parameter type description status code number http status code of the response reason string response reason phrase example \[ { "status code" 200, "reason" "ok", "response headers" {}, "json body" {} } ] update security event updates a specific security event in cherwell service management using the provided seceventid input argument name type required description seceventid string required the unique identifier of the security event to be updated priority string optional defines the priority level of the security event possible values are low, normal, high eventsource string optional the source from which the security event was generated eventdatetime string optional the date and time when the event occurred details string optional additional information or details about the security event recid string optional the record id associated with the security event eventoperationstypeid string optional the identifier for the type of operation performed on the event eventoperationstypename string optional the name corresponding to the type of operation performed on the event createddatetime string optional the timestamp of when the security event was created createdby string optional the individual or system that created the security event createdbyid string optional the id of the person or system who created the security event createdculture string optional the cultural settings applied during the event creation lastmoddatetime string optional the timestamp of the last modification made to the event lastmodby string optional the individual or system that last modified the event lastmodbyid string optional the id of the person or system who last modified the event ownedby string optional the owner of the security event ownedbyid string optional the id of the individual or team owning the security event ownedbyteam string optional the team responsible for managing the security event ownedbyteamid string optional the id of the team responsible for the security event eventoperationsid string optional the unique identifier for the operations performed on the event reportedby string optional the person or system who reported the security event reportedbyemail string optional the email address of the individual who reported the event reportedbyphone string optional the phone number of the individual who reported the event discovery string optional information on how the security event was discovered eventci string optional the configuration item (ci) associated with the event output parameter type description status code number http status code of the response reason string response reason phrase example \[ { "status code" 200, "reason" "ok", "response headers" {}, "json body" {} } ] notes incidents or security events in workflow go through these states new incident is created, recorded (initial details), classified, and assigned to an owner assigned incident is assigned to an owner in progress the incident is being investigated/fulfilled and resolved by an owner pending the incident is temporarily paused (stop the clock) resolved the incident has been resolved and is waiting to be closed closed the incident is closed reopened the incident is reopened because the issue was not fixed or reoccurred