Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

This Integration allows customers to create incident tickets in ServiceNow straight from the Universal Controller. A typical Use Case is the creation of creating a ticket in ServiceNow in the event of a Task failure within the Universal Controller.

...

Template NameExtension NameExtension Version
ServiceNow Incidentue-servicenow-incident2.01.0

Refer to Changelog for version history information.

...

Tested with Python version 3.7.6 and 3.11.6 and with the Universal Agent bundled Python distribution.

...

  • Universal Agent for Windows x64 Version 7.12.0.0 and later with Python options installed.
  • Universal Agent for Linux Version 7.12.0.0 and later with Python options installed.

...

Universal Controller Version 7.12.0.0 and later.

Network and Connectivity Requirements

...

This integration is tested on ServiceNow San DiegoVancouver. It should be compatible with newer versions of ServiceNow as long as ServiceNow backward compatibility is preserved.

...

  • Actions
    • Create a ServiceNow Incident.
  • Authentication
    • Authentication using ServiceNow Credentials.
    • Authentication using OAuth2
  • Input/Output
    • Capability to send the output of any task instance as an incident attachment.

...

Modifications of this integration, applied by users or customers , before or after import, might affect the its supportability of this integration. For more information, refer to Integration Modifications.

Configure Universal Task

For a new Universal Task, create a new task , and enter the required input fields.

...

The input fields for this Universal Extension are described below.

FieldInput typeDefault valueTypeDescription
ActionRequiredCreate IncidentChoiceAction performed upon the task execution. Available actions.
  • Create Incident
ServiceNow Instance URLRequired-TextURL of the ServiceNow instance.
Authentication TypeRequired

Basic Authentication

Choice

Authentication method to use. Available methods,

  • Basic Authentication

  • Oauth2 (ServiceNow API endpoint)

ServiceNow CredentialsRequired-CredentialsCredentials for accessing ServiceNow via API. The Credentials definition should be as follows.
  • ServiceNow username as "Runtime User".
  • ServiceNow password as "Runtime Password".
Client CredentialsOptional-Credentials

Credentials for authenticating using OAuth2 (retrieving access token). The Credentials definition should be as follows.

  • Client ID as "Runtime User"
  • Client Secret as "Runtime Password"

Required when Authentication Type is Oauth2 (ServiceNow API)

CallerOptional-Dynamic ChoiceUser who reported or is affected by this incident.
CategoryOptional-Dynamic ChoiceThe category for incident creation. If not provided, the default category defined on ServiceNow will be considered.
SubcategoryOptional-Dynamic ChoiceThe subcategory for incident creation. The choice of Subcategory depends on the previous choice of Category.
ImpactOptional-Dynamic ChoiceThe impact of the created incident
UrgencyOptional-Dynamic ChoiceThe urgency of the created incident.
Assigned ToOptional-Dynamic ChoiceThe user is primarily responsible for treating this incident in ServiceNow.
Assignment GroupOptional-Dynamic ChoiceAssignment group that is responsible for working on this incident in ServiceNow.
Short DescriptionRequired-TextShort description of the incident.
DescriptionOptional-Large TextDescription of the incident.
Attach Output SourceRequired-- None --ChoiceParameter controlling whether an attachment will be attached to the incident and the source of it. The following options are available.
  • -- None --
  • Sibling Task Instance
  • Any Task Instance
Output TypeOptionalAllChoiceThe type of output to be used as an attachment. The following options are available.
  • All
  • Standard Output
  • Standard Error
Required when Attach Output Source is “Sibling Task” or “Any Task Instance”.
Number of linesOptional100IntegerThe number of lines to be retrieved from the task instance output. The extension will provide up to the specified number of lines, less if there are not enough lines generated.

Required when Attach Output Source is “Sibling Task” or “Any Task Instance”.

The value must be greater than 0.
Task Instance IDOptional-TextUUID of the task instance, the output of which is attached. UAC Functions can be used to resolve the required Task Instance ID. For more information, the reader can refer to the task examples.

Required when Attach Output Source is “Sibling Task” or “Any Task Instance”.
UC URLOptional-TextBase URL of the target Universal Controller.

Required when Attach Output Source is “Sibling Task” or “Any Task Instance”.
UC CredentialOptional-
Credential for accessing the Controller.

The Credentials definition should be as follows.
  • UA Controller username as "Runtime User".
  • UA Controller password as "Runtime Password".
Required when Attach Output Source is “Sibling Task” or “Any Task Instance”.


Note

Using empty values for dynamic choice fields will result in ServiceNow setting a default value for the field if one exists.

...

Example of creation of an incident.

Image RemovedImage Added

Create an Incident with an attachment from a Sibling Task

Example of creation of creating an incident with an attachment from a sibling task within a workflow. The workflow is configured to create a ServiceNow incident when a task fails.


An example workflow where a ServiceNow Incident Universal Task follows the Failure transition of a SQL Task is followed by a ServiceNow Incident Universal Task is provided below.


An example of a task configured to use the information from the failed Universal Task Instance as an attachment for creating a ServiceNow Incident is provided below.

Image RemovedImage Added

Create an Incident from any Task Instance

Example of creation of an incident from any Task Instance.The best


Best practice to configure such a scenario within UAC is the followingshown below.

Step 1: Create a Monitor Task that monitors for the failure of tasks by configuring related " Monitor Details".

Step 2: Configure the ServiceNow Incident task. The created Incident Task propagates the output of the failed Task Instance as an attachment to ServiceNow. For that, a Task Monitor trigger is required. More information on this on Step 3.

Image RemovedImage Added

Step 3: Create a Task Monitor Trigger linked to the Monitor Task (on Step 1), which controls the action that needs to be taken when the monitor successfully monitors a failure, in this case, the trigger of an incident ticket configured on Step 2.

Create Incident using OAuth2 authentication

Image Added

Task Output

Exit Codes

...

An example of the Extension Output for the creation of creating a ServiceNow Incident using Oauth the output of a Task Instance ID as an attachment is presented below.

Code Block
languagejs
titleExtension Output
{
    "exit_code": 0,
    "status_description": "SUCCESS: ServiceNow Incident Create Incident executed successfully!",
    "changed": true,
    "invocation": {
        "extension": "ue-servicenow-incident",
        "version": "2.

...

1.0",
        "fields": {
            "action": "Create Incident",
            "authentication_type": "Oauth2 (ServiceNow API endpoint)",
            "servicenow_instance_url": "https://

...

dev123456.service-now.com",
            "servicenow_credentials_username": "****",
            "servicenow_credentials_password": "****",
            "caller": 

...

null,
            "category": "

...

Software",
            "subcategory": "

...

Operating System",
            "impact": "2 - Medium",
            "urgency": "

...

2 - 

...

Medium",
            "assigned_to": "

...

Jewel 

...

Agresta",
            "assignment_group": "

...

RMA 

...

Approvers",
            "short_description": "

...

Short Decription",
            "description": "

...

Long description",
            "attach_output_source": null,
            "output_type": null,
            "number_of_lines": null,
            "task_instance_id": null,
            "uc_url": null,
            "uc_credentials_username": null,
            "uc_credentials_password": null,
            "client_credentials_id": "f7338f849cad4fffbc4dd2fd9976a32b",
            "client_credentials_secret": "****"
        }
    },
    "result": {
        "code": 201,
        "ticket_number": "

...

INC0010056",
        "sys_id": "

...

5115d027a30f383f6df5209c5e27a117"
    }
}


STDOUT and STDERR

STDOUT and STDERR provide additional information to the User. The populated content can be changed in future versions of this extension without notice. Backward compatibility is not guaranteed.

Anchor
imintegration modificationim
integration modification

Integration Modifications

Modifications applied by users or customers , before or after import , might affect the supportability of this integration. The following modifications are discouraged to retain the support level for this integration.

...

Users and customers are encouraged to report defects , or feature requests at Stonebranch Support Desk.

...

Anchor
Changelog
Changelog

Changelog

ue-servicenow-incident-2.1.0 (2024-02-15)

  • Enhancements: Added support for OAuth2 authentication method
  • Breaking Changes: This integration is no longer importable on Universal Controller 7.1 or runnable on Agent version 7.1.

ue-servicenow-incident-2.0.0 (2023-09-14)

...