Page tree

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 5 Current »

triggerCallbackAction URL configuration is flexible and client-specific now. Historically, the URL for the workflow's trigger callback action was defined in the parameters column as an additional field. That approach lacked flexibility, as any URL change required manual updates via SQL directly in the database, which was inefficient.

Now callback URLs are configurable through the config, with the ability to override it at the client level. Users can define or modify the callback URLs without need for manual database changes.

The config is client specific, so for each (task) client the users are able to define other URLs.

Config option name: runtimeOptions.task.workflow.webhooks

Sample value: { "handleAllFinishOfARole" : "https://www.callbackaction.de/test",  "handleAfterImport" : "https://www.anoterUrl.com/api" }


Proper entry with a specific trigger for the needed callback must be configured / exist in workflow_action table before!


Examples of the predefined triggers:

Trigger

In Step

By Role

User State

Action Class

Action

Parameters

handleAllFinishOfARole

reviewing

reviewer

finished

editor_Workflow_Actions

triggerCallbackAction


handleAfterImport

reviewing

reviewer

finished

editor_Workflow_Actions

triggerCallbackAction


After defining triggerCallbackAction for a specific trigger, the triggered URL can be overwritten in the config.

  • No labels