Documentation Campaign Campaign Web User Interface

Guardrails and limitations for workflows

Last update: February 29, 2024

When working in Campaign Web user interface with workflows created or modified in Campaign client console, the guardrails and limitations listed below apply.

Please note that, while this page identifies key considerations when working with workflows in the console and the web user interface, it does not encompass every potential incompatibility between the two interfaces.

Workflow activities

Workflow activities that are not supported yet in Campaign Web user interface are read-only and displayed as incompatible activities. You can still execute the workflow, send messages, check the logs, etc. Workflow activities that are available both in the Campaign Web user interface and the Campaign client console are editable.

Console	Web

When a Query or an Enrichment activity is configured with additional data in the console, the enrichment data is taken into account in Campaign Web and passed into the outbound transition, but it cannot be edited.

Console	Web

In the console, the Enrichment activity can perform both reconciliation and enrichment. If you have defined, in the client console, reconciliation settings in the Enrichment activity, it will be displayed as a Reconciliation activity in Campaign Web user interface.

Console	Web

Workflow canvas

When creating a new workflow in Campaign Web user interface, the canvas only supports one entry point. However, if you created a worflow in the console with multiple entry points, you can open and edit it in Campaign Web user interface.

Console	Web

The positioning of the nodes is refreshed everytime an activity is added or removed. If you create a workflow in the console, modify it using Campaign Web user interface and re-open it in the console, you may notice some minor positioning imperfections. This has no impact on the workflow’s processes and tasks.