5.1.25.2. Edit Connector

Scan connectors can be created and edited in the SAFEQ Cloud web UI on the “Connectors” tab in the “Scan Workflows” section.

*Because connectors are required in order to be able to create workflows, they are available behind the same permission set.
The user doing this configuration must have the “ViewScanWorkflow” permission to access the section. Additionally, permissions “CreateScanWorkflow”, “ModifyScanWorkflow”, and “DeleteScanWorkflow” are required for their respective actions to be enabled.

Adding/editing a Connector

1. Go to “Scan Workflows” > “Connectors”.
2. To add a workflow, click the “Add” button.
3. To modify a connector, click the edit icon aside from the selected workflow.

The form is the same for adding and editing a connector and consists of several sections with a specific set of fields.

General

Fields with basic information about the Connector.

Configuration

Fields specific to a selected connector type. Initially, only the “Connector type” field is available, upon selecting a type, its customizable fields are shown below.

*In this instance, there are no additional configurable fields, because the SMTP configuration is taken from the WPS service configuration.
Currently, only the “Email (SMTP)” connector type is available.

Failure behavior

Fields that control the behavior of the Workflow Processing System in case of job processing failure.

Notifications

Fields that allow setting up notifications for the Workflow Processing System.

*Currently, only failure notifications are available.
There are various dynamic placeholders that can be used, as described in section Workflow variables.

Deleting a connector

A connector can be deleted by the user with the “DeleteScanWorkflow” permission, either directly from the list, or via the “Delete” button in the individual connector’s detail.

Connector deletion when used by a workflow

In case one or more workflows exist, that are using the connector, it is not possible to delete it, and a message detailing up to 10 workflows that reference it is presented instead.