PagerDuty Create Incident activity

Introduction

A PagerDuty Create Incident activity, using its PagerDuty connection, creates an incident in PagerDuty and is intended to be used as a target in an operation.

Create a PagerDuty Create Incident activity

An instance of a PagerDuty Create Incident activity is created from a PagerDuty connection using its Create Incident activity type.

To create an instance of an activity, drag the activity type to the design canvas or copy the activity type and paste it on the design canvas. For details, see Creating an activity instance in Component reuse.

An existing PagerDuty Create Incident activity can be edited from these locations:

• The design canvas (see Component actions menu in Design canvas).
• The project pane's Components tab (see Component actions menu in Project pane Components tab).

Configure a PagerDuty Create Incident activity

Follow these steps to configure a PagerDuty Create Incident activity:

• Step 1: Enter a name and select a service
  Provide a name for the activity and select a service.

• Step 2: Review the data schemas
  Any request or response schemas generated from the endpoint are displayed.

Step 1: Enter a name and select a service

In this step, provide a name for the activity and select a service. Each user interface element of this step is described below.

• Name: Enter a name to identify the activity. The name must be unique for each PagerDuty Create Incident activity and must not contain forward slashes / or colons :.

• Select a Service: This section displays services available in the PagerDuty endpoint. To create services, see Services and Integrations in the PagerDuty documentation.

  • Selected Service: After a service is selected, it is listed here.

  • Search: Enter any column's value into the search box to filter the list of services. The search is not case-sensitive. If services are already displayed within the table, the table results are filtered in real time with each keystroke. To reload services from the endpoint when searching, enter search criteria and then refresh, as described below.

  • Refresh: Click the refresh icon or the word Refresh to reload services from the PagerDuty endpoint. This may be useful if services have been added to PagerDuty. This action refreshes all metadata used to build the table of services displayed in the configuration.

  • Selecting a Service: Within the table, click anywhere on a row to select a service. Only one service can be selected. The information available for each service is fetched from the PagerDuty endpoint:

  • Name: The name of the service.

  • Description: The description of the service.

  Tip

  If the table does not populate with available services, the PagerDuty connection may not be successful. Ensure you are connected by reopening the connection and retesting the credentials.

• Save & Exit: If enabled, click to save the configuration for this step and close the activity configuration.

• Next: Click to temporarily store the configuration for this step and continue to the next step. The configuration will not be saved until you click the Finished button on the last step.

• Discard Changes: After making changes, click to close the configuration without saving changes made to any step. A message asks you to confirm that you want to discard changes.

Step 2: Review the data schemas

Any request or response schemas generated from the endpoint are displayed. Each user interface element of this step is described below.

• Data Schemas: These data schemas are inherited by adjacent transformations and are displayed again during transformation mapping.

  Note

  Data supplied in a transformation takes precedence over the activity configuration.

  The PagerDuty connector uses the PagerDuty REST API v2. Refer to Create an incident in the PagerDuty API Reference documentation for information on the schema nodes and fields.

• Refresh: Click the refresh icon or the word Refresh to regenerate schemas from the PagerDuty endpoint. This action also regenerates a schema in other locations throughout the project where the same schema is referenced, such as in an adjacent transformation.

• Back: Click to temporarily store the configuration for this step and return to the previous step.

• Finished: Click to save the configuration for all steps and close the activity configuration.

• Discard Changes: After making changes, click to close the configuration without saving changes made to any step. A message asks you to confirm that you want to discard changes.

Next steps

After configuring a PagerDuty Create Incident activity, complete the configuration of the operation by adding and configuring other activities, transformations, or scripts as operation steps. You can also configure the operation settings, which include the ability to chain operations together that are in the same or different workflows.

Menu actions for an activity are accessible from the project pane and the design canvas. For details, see Activity actions menu in Connector basics.

PagerDuty Create Incident activities can be used as a target with these operation patterns:

• Transformation pattern
• Two-transformation pattern (as the first or second target)

To use the activity with scripting functions, write the data to a temporary location and then use that temporary location in the scripting function.

When ready, deploy and run the operation and validate behavior by checking the operation logs.