backport 3546 (#3553)

camunda · Jun 5, 2024 · 9fc5a06 · 9fc5a06
1 parent 5dab3ec
commit 9fc5a06
Show file tree

Hide file tree

Showing 4 changed files with 4 additions and 4 deletions.
diff --git a/docs/components/best-practices/development/routing-events-to-processes.md b/docs/components/best-practices/development/routing-events-to-processes.md
@@ -151,7 +151,7 @@ You can also use [`CreateProcessInstanceWithResult`](/apis-tools/zeebe-api/gatew
 As soon as you have multiple possible starting points, you have to use named messages to start process instances. The API method is [`PublishMessage`](/apis-tools/zeebe-api/gateway-service.md#publishmessage-rpc):
 
 ```java
-client.newPublishMessageComment()
+client.newPublishMessageCommand()
   .messageName("message_invoiceReceived") // <1>
   .corrlationKey(invoiceId) // <2>
   .variables( // <3>

diff --git a/...ersion-8.1/components/best-practices/development/routing-events-to-processes.md b/...ersion-8.1/components/best-practices/development/routing-events-to-processes.md
@@ -155,7 +155,7 @@ You can also use [`CreateProcessInstanceWithResult`](/apis-tools/grpc.md/#create
 As soon as you have multiple possible starting points, you have to use named messages to start process instances. The API method is [`PublishMessage`](/apis-tools/grpc.md/#publishmessage-rpc):
 
 ```java
-client.newPublishMessageComment()
+client.newPublishMessageCommand()
   .messageName("message_invoiceReceived") // <1>
   .corrlationKey(invoiceId) // <2>
   .variables( // <3>

diff --git a/...ersion-8.2/components/best-practices/development/routing-events-to-processes.md b/...ersion-8.2/components/best-practices/development/routing-events-to-processes.md
@@ -155,7 +155,7 @@ You can also use [`CreateProcessInstanceWithResult`](../../../apis-tools/grpc.md
 As soon as you have multiple possible starting points, you have to use named messages to start process instances. The API method is [`PublishMessage`](../../../apis-tools/grpc.md#publishmessage-rpc):
 
 ```java
-client.newPublishMessageComment()
+client.newPublishMessageCommand()
   .messageName("message_invoiceReceived") // <1>
   .corrlationKey(invoiceId) // <2>
   .variables( // <3>

diff --git a/...ersion-8.3/components/best-practices/development/routing-events-to-processes.md b/...ersion-8.3/components/best-practices/development/routing-events-to-processes.md
@@ -155,7 +155,7 @@ You can also use [`CreateProcessInstanceWithResult`](../../../apis-tools/grpc.md
 As soon as you have multiple possible starting points, you have to use named messages to start process instances. The API method is [`PublishMessage`](../../../apis-tools/grpc.md#publishmessage-rpc):
 
 ```java
-client.newPublishMessageComment()
+client.newPublishMessageCommand()
   .messageName("message_invoiceReceived") // <1>
   .corrlationKey(invoiceId) // <2>
   .variables( // <3>