Salesforce - Update Ticket

Salesforce - Update Ticket updates the indicated tickets in Salesforce 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 must be configured to run the Enforcement Set.

  • 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 the Salesforce 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 Salesforce adapter connection.

Additional Fields

These fields are optional.

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

💡

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.

  • Domain (required) - The full URL of the Salesforce server.

  • User Name and Password (required) - The credentials for a user account that has the Required Permissions to perform this action.

  • User Secret (required) - The Salesforce security token associated with a user account to perform this action.

  • Consumer Key (required) - A consumer key associated with a user account that has the Required Permissions to perform this action.

  • Consumer Secret (required) - A consumer secret associated with a consumer key.

  • Authentication Flow - The authentication method used to connect the adapter.

Ticket Additional Settings

  • Additional fields - Specify additional fields to be added as key/value pairs in a JSON format.
    For example:

    {"field1": "value1", "field2": "value2"}

    If one of the specified fields is invalid, the request might fail.

  • Map Axonius fields to vendor fields - Use the Field Mapping Wizard to map Axonius fields to fields in external systems. In this way, you can transfer data found in Axonius into the external system as part of the configuration of relevant enforcement actions. The wizard shows you which fields exist on the Axonius system, allowing you to map them easily.

    📘

    Note:

    For details, see Axonius to External Field Mapping.


Ticket Main Settings

  • Ticket Status - Enter the updated ticket status.
  • Ticket Assignee - Enter the assignee for the updated tickets.
  • Ticket Comments - Enter comments to add to the tickets.
  • Ticket IDs To Update - Ticket IDs are populated from Dynamic Values / IFTTT , or manually input separated by a comma (,). See Creating Enforcement Action Dynamic Value Statements to learn more about Dynamic Value statement syntax.

APIs

Axonius uses the Salesforce API.

Required Permissions

Version Matrix

This Enforcement Action has only been tested with the versions marked as supported, but may work with other versions. Please contact Axonius Support if you have a version that is not listed and it is not functioning as expected.

VersionSupportedNotes
Salesforce 5.0Yes