- 22 Sep 2024
- 2 Minutes to read
- Print
- DarkLight
- PDF
Freshservice - Update Assets
- Updated on 22 Sep 2024
- 2 Minutes to read
- Print
- DarkLight
- PDF
Freshservice - Update Assets updates a Freshservice asset 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.
All Freshservice field names are case sensitive. To check a field name, fetch the asset with a curl command and check the RAW data in Axonius. See Service Desk API for Developers | Freshservice.
- 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.
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 Freshservice adapter - Select this option to use the first connected Freshservice adapter credentials.
- 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 Freshservice adapter connection.
* The API key used for the adapter connection must be for a user with permissions to update an asset.
Required Fields
These fields must be configured to run the Enforcement Set.
- Map Axonius fields to Freshservice fields- This field is only for mapping mandatory fields, such as the name field. (To map custom fields, use the Map Axonius fields to Freshservice type fields field under Additional Fields.) Use the Field Mapping Wizard to map Axonius fields to fields in Freshservice. This allows you to transfer data found in Axonius into Freshservice. The wizard shows you which fields exist on the Axonius system, allowing you to map them easily.NOTE
For details, see Axonius to CMDB Field Mapping.
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.
- Freshservice domain - The hostname or IP address of the Freshservice server.
- API Key – Specify the API Key provided by Freshservice.
- 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.
- Throttle API Requests - Select this option to only use 90% of the API total rate limit bandwidth. For example: If a customer has 3000 total API calls allowed per hour, axonius will only produce 2700 calls, and leave the remaining 10% available.
- Map Axonius fields to Freshservice type fields - Use the Field Mapping Wizard to map Axonius fields to type fields in Freshservice. This field is used to map custom fields defined in Freshservice and MUST be typed exactly as they appear in Freshservice.
- Adjust Date fields to ISO-8601 format - Select to have dates adjusted to the ISO-8601 format.
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.
For more details about other Enforcement Actions available, see Action Library.