Contents x
    Salesforce - Create Case
    • 22 Sep 2024
    • 2 Minutes to read
    • Print
    • Dark
      Light
    • PDF
    Contents

    Salesforce - Create Case

    • Updated on 22 Sep 2024
    • 2 Minutes to read
    • Print
    • Dark
      Light
    • PDF
    Article summary

    Salesforce - Create Case creates a case in Salesforce for:

    • Assets that match the results of the selected saved query, and match the Enforcement Action Conditions, if defined or assets selected on the relevant asset page.

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

    Note:

    General Settings

    • 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 the first connected adapter credentials.
      • Select Adapter Connection - Select which adapter connection to use for this Enforcement Action.
      NOTE
      To use this option, you must successfully configure a Salesforce.

    Required Fields

    These fields must be configured to run the Enforcement Set.

    • Title (default: Axonius-created ticket) - Enter a title for the case. It is recommended to use a short description of the case as a title. The default title is "Axonius-created ticket".

    • Account ID - ID of the account associated with this case.

    • Contact ID - ID of the associated contact.

    • Description - Enter a description of the case.

    • Compute Node - The Axonius node to use when connecting to the specified host. For more details, see Connecting Additional Axonius Nodes.

    Additional Fields

    These fields are optional.

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

    • 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.
    • 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.

    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

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

    Was this article helpful?
    What's Next