Salesforce - Create Case
- 23 Feb 2025
- 2 Minutes to read
- Print
- DarkLight
- PDF
Salesforce - Create Case
- Updated on 23 Feb 2025
- 2 Minutes to read
- Print
- DarkLight
- PDF
Article summary
Did you find this summary helpful?
Thank you for your feedback
Salesforce - Create Case creates a case 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:
- Not all asset categories 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 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.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.
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.
- 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
- The value supplied in User Name and Consumer Key must have permissions to manage users, as per Salesforce - Get User Information for Multiple Users.
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.
| Version | Supported | Notes |
|---|---|---|
| Salesforce 5.0 | Yes |
For more details about other Enforcement Actions available, see Action Library.
Was this article helpful?