Halo - Create Ticket

Halo - Create Ticket creates a HaloITSM ticket for:

  • Assets returned by the selected query or assets selected on the relevant asset page.

See Creating Enforcement Sets to learn more about adding Enforcement Actions to Enforcement Sets.

📘

Note:

Required Fields

These fields are required to run the Enforcement Action.

  • Action name - The name of this Enforcement Action. The system sets a default name. You can change the name.
  • Configure Dynamic Values - Toggle on to enter a Dynamic Value statement. See Creating Enforcement Action Dynamic Value Statements to learn more about Dynamic Value statement syntax.
  • Use stored credentials from HaloITSM Adapter - Select this option to use credentials from the adapter connection. By default, the first connection is selected.
    • When you select this option, the Select Adapter Connection drop-down becomes available. Select the adapter connection to use for this Enforcement Action.


📘

Note

To use this option, you must successfully configure an HaloITSM adapter connection.

  • Summary (default: New Ticket) - A concise description of the ticket.
  • Details (default: This is a ticket created by Axonius.) - A complete description of the ticket.
  • Ticket Type ID (default: 0) - The specific ID for the ticket's type.
  • Ticket Category (default: Category 1) - The category the ticket falls under.
  • Impact (default: 0) - The impact level of the ticket (string or number). 0 is the lowest.
  • Urgency (default: 0) - The urgency level of the ticket (string or number). 0 is the lowest.
  • Compute Node - The Axonius node to use when connecting to the specified host. For more details, see Working with Axonius Compute Nodes.

Additional Fields

These fields are optional.

💡

Connection and Credentials

When Use stored credentials from the adapter is toggled off, some of the connection fields below are required to create the connection, while other fields are optional.

  • Map Axonius fields to Halo fields - Use the Field Mapping Wizard to transfer data from Axonius assets directly into standard Halo ticket fields. The wizard shows you which fields exist on the Axonius system, allowing you to map them easily. For details, see Axonius to External Field Mapping.

  • Map Axonius fields to Halo custom fields - Use the Field Mapping Wizard to transfer data from Axonius assets directly into Halo custom fields. Similar to the above field, but for custom fields you've created within your HaloITSM system.

  • Host Name or IP Address - The hostname or IP address of the HaloITSM server.

  • Client ID and Client Secret - The credentials for a user account that has permissions to perform this Enforcement Action.

  • Tenant - Specifies the tenant in the URL. Used only with hosted solutions of Halo.

  • Verify SSL (optional) - Select whether to verify the SSL certificate of the server against the CA database inside of Axonius. For more details, see SSL Trust & CA Settings.

  • HTTPS Proxy (optional) - Connect the adapter to a proxy instead of directly connecting it to the domain.

  • HTTPS Proxy User Name (optional) - The user name to use when connecting to the server using the HTTPS Proxy.

  • HTTPS Proxy Password (optional) - The password to use when connecting to the server using the HTTPS Proxy.

  • Gateway Name - Select the Gateway through which to connect to perform the action.

APIs

Axonius uses the Halo REST API.

Required Ports

Axonius must be able to communicate via the following port:

  • 443

Required Permissions

The stored credentials, or those provided in Connection and Credentials, must have permission to perform this Enforcement Action.


For more details about other Enforcement Actions available, see Action Library.