Create BMC FootPrints Ticket
Create BMC FootPrints Ticket creates a ticket in BMC Footprints 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:
- Not all asset types are supported for all Enforcement Actions.
- See Actions supported for Activity Logs, Adapters Fetch History, and Asset Investigation modules.
- See Actions supported for Vulnerabilities.
- See Actions supported for Software.
Required Fields
These fields must be configured 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 (optional) - 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 the BMC Footprints 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 a BMC FootPrints adapter connection.
-
-
Compute Node - The Axonius node to use when connecting to the specified host. For more details, see Working with Axonius Compute Nodes.
Ticket Main Settings
These fields are optional.
- Ticket Definition ID - The unique internal identifier for the type or template of the ticket being created (e.g., Incident, Service Request, Change Request, Problem).
- Quick Template ID - The unique internal identifier for a pre-filled template used to speed up ticket creation.
- Contact Definition ID - The unique internal identifier for the type of contact being associated with the ticket.
- Select Contact - The field used to choose the specific individual who is reporting or affected by the issue.
- Assignees - The individual agent(s) or team(s) currently responsible for working on and resolving the ticket.
- Submitter - The user who created and submitted the ticket into the FootPrints system.
- Assets List - A field used to associate the ticket with one or more physical or logical Assets (Configuration Items/CIs) managed in the system.
Additional Fields
These fields are optional.
Connection and CredentialsWhen 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.
- Host Name or IP Address - The hostname or IP address of the BMC FootPrints server.
- User Name and Password - The credentials for a user account that has the Required Permissions to fetch assets.
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 Password (optional) - The password to use when connecting to the server using the HTTPS Proxy.
HTTPS Proxy User Name (optional) - The user name 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 BMC FootPrints Service Core Web Services.
Required Ports
Axonius must be able to communicate via the following ports:
- TCP port 80/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.
Updated 1 day ago
