Freshservice - Update Problem

Freshservice - Update Problem updates existing Freshservice Problems that are returned by the selected query or selected from an asset or Tickets page. It updates only Freshservice Problems; use Freshservice - Update Ticket for Freshservice Tickets.

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

When accessing an enforcement action using the API, you must use the backend form of field names.

Use the Syntax Helper to find the correct name. In the enforcement action, enable Configure Dynamic Values and select Syntax Helper.

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 Aggregated Security Findings.
• See Actions supported for Software.

Required Fields

These fields must be configured to run the Enforcement Action.

• Use stored credentials from the Freshservice 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.

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

Additional Fields

These fields are optional. Leave a field empty or select Do not change to preserve its current value.

• Problem name - Enter the new Problem name.
• Problem description - Enter the new Problem description.
• Status code - Enter the numeric Freshservice Problem status code. Built-in codes are 1 for Open, 2 for Change Requested, and 3 for Closed. For custom statuses, use the code mapped in the Freshservice adapter's Problems Status Description Mapping.
• Priority - Select the Problem priority.
• Impact - Select the Problem impact.
• Additional fields (JSON format) - Enter JSON for fields to update, such as group_id, category, custom_fields, or analysis_fields. Values entered in the action fields take precedence over values in this JSON.

APIs

Axonius uses the Freshservice Problems API - PUT /problems/{id}.

Required Ports

Axonius must be able to communicate via the following ports:

• TCP port 443 (HTTPS) — confirm the exact port with your Freshservice administrator.

Required Permissions

The credentials used by the Freshservice adapter must be authorized to update Freshservice Problems. The patch does not specify Freshservice permission names or scopes; confirm the required access with your Freshservice administrator.

The action uses the configured Freshservice adapter connection and its authentication credentials.

To learn more about Enforcement Actions, see Enforcement Actions.