From e9e3513dd148ed67b272db9df587c24f68d9ff1f Mon Sep 17 00:00:00 2001 From: Hannah Hunter Date: Thu, 2 Feb 2023 17:40:43 -0600 Subject: [PATCH] remove management from language Signed-off-by: Hannah Hunter --- .../building-blocks/workflow/howto-manage-workflow.md | 8 ++++++-- .../building-blocks/workflow/workflow-patterns.md | 2 +- 2 files changed, 7 insertions(+), 3 deletions(-) diff --git a/daprdocs/content/en/developing-applications/building-blocks/workflow/howto-manage-workflow.md b/daprdocs/content/en/developing-applications/building-blocks/workflow/howto-manage-workflow.md index bea13ab7b..57f94591a 100644 --- a/daprdocs/content/en/developing-applications/building-blocks/workflow/howto-manage-workflow.md +++ b/daprdocs/content/en/developing-applications/building-blocks/workflow/howto-manage-workflow.md @@ -8,12 +8,16 @@ description: Manage and expose workflows Now that you've [set up the workflow and its activities in your application]({{< ref howto-author-workflow.md >}}), you can start, terminate, and get information about the workflow using HTTP API calls. For more information, read the [workflow API reference]({{< ref workflow_api.md >}}). -{{< tabs ".NET" HTTP >}} +{{< tabs ".NET SDK" HTTP >}} {{% codetab %}} -Manage your workflow within your code. In the `OrderProcessingWorkflow` example from the [Author a workflow]({{< ref howto-author-workflow.md >}}) guide, the workflow is registered in the code and then exposed using... +Manage your workflow within your code. In the `OrderProcessingWorkflow` example from the [Author a workflow]({{< ref "howto-author-workflow.md#write-the-workflow" >}}) guide, the workflow is registered in the code. You can then start, terminate, and get information about the workflow: + +```csharp + +``` {{% /codetab %}} diff --git a/daprdocs/content/en/developing-applications/building-blocks/workflow/workflow-patterns.md b/daprdocs/content/en/developing-applications/building-blocks/workflow/workflow-patterns.md index dc29c6ef1..13734d1cb 100644 --- a/daprdocs/content/en/developing-applications/building-blocks/workflow/workflow-patterns.md +++ b/daprdocs/content/en/developing-applications/building-blocks/workflow/workflow-patterns.md @@ -138,7 +138,7 @@ The end-to-end flow is illustrated in the following diagram. The challenge with implementing the asynchronous request-reply pattern is that it involves the use of multiple APIs and state stores. It also involves implementing the protocol correctly so that the client knows how to automatically poll for status and know when the operation is complete. -The Dapr workflow management HTTP API supports the asynchronous request-reply pattern out-of-the box, without requiring you to write any code or do any state management. The following `curl` commands illustrate how the workflow APIs support this pattern. +The Dapr workflow HTTP API supports the asynchronous request-reply pattern out-of-the box, without requiring you to write any code or do any state management. The following `curl` commands illustrate how the workflow APIs support this pattern. ```bash curl -i -X TODO