.NET - How to start a workflow - DaprWorkflowComponent

[panagiotiskompis]

I have a question regarding the Dapr workflows.

Page: https://docs.dapr.io/getting-started/quickstarts/workflow-quickstart/

await daprClient.StartWorkflowAsync(
workflowComponent: DaprWorkflowComponent,
workflowName: nameof(OrderProcessingWorkflow),
input: orderInfo,
instanceId: orderId);

What is the DaprWorkflowComponent? In the other building blocks like state store, that was the name described in the YAML config
e.g. pub sub

apiVersion: dapr.io/v1alpha1
kind: Component
metadata:
name: name here

Based on the page: https://docs.dapr.io/reference/api/workflow_api/

"However, Dapr comes with a built-in dapr workflow component that is built on Dapr Actors. No component file is required to use the built-in Dapr workflow component."

No component file is required. So what is the name that I should add there since I dont have YAML file? Am I missing something?

[panagiotiskompis]

It seems that "dapr" is the default value. I didn't find any mention about that anywhere, based on an example I discovered it.
Page: https://docs.dapr.io/developing-applications/building-blocks/workflow/howto-manage-workflow/

Why not adding the default value in the method StartWorkflowAsync?

[dapr-bot]

This issue has been automatically marked as stale because it has not had activity in the last 60 days. It will be closed in the next 7 days unless it is tagged (pinned, good first issue, help wanted or triaged/resolved) or other activity occurs. Thank you for your contributions.

[WhitWaldo]

@panagiotiskompis The various workflow methods on the Dapr.Client will be removed in 1.15. You're encouraged to install and use the Dapr.Workflow package.

Further, there is no StartWorkflowAsync method any longer. Rather, use the ScheduleNewWorkflowAsync method on the DaprWorkflowClient which does not have a DaprWorkflowComponent name argument. The first argument on ScheduleNewWorkflowAsync instead has you provide the name of the workflow you want to start.

[panagiotiskompis]

Thank you for your answer!

[WhitWaldo]

While they haven't yet been merged, I wrote up several PRs yesterday that demonstrate how to approach the various scenarios described in the documentation using the latest .NET APIs:

Task Chaining
Monitor
External interaction
Async operations
Sub-workflows
Fan in/Fan out