From 32984c31d239aa08b79cefde127d2aa16f108fbe Mon Sep 17 00:00:00 2001 From: Walter Medvedeo Date: Fri, 15 Nov 2024 16:47:47 +0100 Subject: [PATCH] Update serverlessworkflow/modules/ROOT/pages/cloud/operator/configuring-workflow-eventing-system.adoc Co-authored-by: Ricardo Zanini <1538000+ricardozanini@users.noreply.github.com> --- .../cloud/operator/configuring-workflow-eventing-system.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/serverlessworkflow/modules/ROOT/pages/cloud/operator/configuring-workflow-eventing-system.adoc b/serverlessworkflow/modules/ROOT/pages/cloud/operator/configuring-workflow-eventing-system.adoc index 704f3e205..fca6fe078 100644 --- a/serverlessworkflow/modules/ROOT/pages/cloud/operator/configuring-workflow-eventing-system.adoc +++ b/serverlessworkflow/modules/ROOT/pages/cloud/operator/configuring-workflow-eventing-system.adoc @@ -49,7 +49,7 @@ To configure a workflow-scoped eventing system you must use the fields `spec.sin To configure a workflow-scoped eventing system for the workflow outgoing events, you must use the field `spec.sink.ref` in the `SonataFlow` CR. -This information signals the SonataFlow Operator to automatically link the current workflow, to produce the events by using that Broker. +This information signals the {operator_name} to automatically link the current workflow, to produce the events by using that Broker. That includes, the {product_name} system events, and the workflow business events. The following `SonataFlow` CR fragment shows an example of such configuration: