From 869cb83c35a0655c0a227e6148ebef9431eca038 Mon Sep 17 00:00:00 2001 From: Cassandra Coyle Date: Fri, 25 Jul 2025 13:12:02 -0500 Subject: [PATCH] feedback Signed-off-by: Cassandra Coyle --- examples/src/main/java/io/dapr/examples/workflows/README.md | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/examples/src/main/java/io/dapr/examples/workflows/README.md b/examples/src/main/java/io/dapr/examples/workflows/README.md index 4ba406851..064a86633 100644 --- a/examples/src/main/java/io/dapr/examples/workflows/README.md +++ b/examples/src/main/java/io/dapr/examples/workflows/README.md @@ -684,7 +684,7 @@ Key Points: ### Cross-App Pattern -The cross-app pattern allows workflows to call activities that are hosted in different Dapr applications. This is useful for microservices architectures where activities are distributed across multiple services, service mesh scenarios, or multi-tenant applications where activities are isolated by app ID. +The cross-app pattern allows workflows to call activities that are hosted in different Dapr applications. This is useful for microservices architectures where activities are distributed across multiple services, or multi-tenant applications where activities are isolated by app ID. The `CrossAppWorkflow` class defines the workflow. It demonstrates calling activities in different apps using the `appId` parameter in `WorkflowTaskOptions`. See the code snippet below: ```java @@ -885,7 +885,6 @@ The workflow demonstrates: This pattern is particularly useful for: - Microservices architectures where activities are distributed across multiple services -- Service mesh scenarios where different apps handle different types of activities - Multi-tenant applications where activities are isolated by app ID ### Suspend/Resume Pattern