adding spring boot workflows integration (#1195)

Co-authored-by: Cassie Coyle <[email protected]>

Author: salaboy

daprdocs/content/en/java-sdk-docs/spring-boot/_index.md

@@ -122,7 +122,7 @@ Besides the previous configuration (`DaprTestContainersConfig`) your tests shoul
 The Java SDK allows you to interface with all of the [Dapr building blocks]({{< ref building-blocks >}}). 
 But if you want to leverage the Spring and Spring Boot programming model you can use the `dapr-spring-boot-starter` integration. 
 This includes implementations of Spring Data (`KeyValueTemplate` and `CrudRepository`) as well as a `DaprMessagingTemplate` for producing and consuming messages 
-(similar to [Spring Kafka](https://spring.io/projects/spring-kafka), [Spring Pulsar](https://spring.io/projects/spring-pulsar) and [Spring AMQP for RabbitMQ](https://spring.io/projects/spring-amqp)).
+(similar to [Spring Kafka](https://spring.io/projects/spring-kafka), [Spring Pulsar](https://spring.io/projects/spring-pulsar) and [Spring AMQP for RabbitMQ](https://spring.io/projects/spring-amqp)) and Dapr workflows. 
 
 ## Using Spring Data `CrudRepository` and `KeyValueTemplate`
 
@@ -277,6 +277,53 @@ public static void setup(){
 
 You can check and run the [full example source code here](https://github.com/salaboy/dapr-spring-boot-docs-examples).
 
+## Using Dapr Workflows with Spring Boot
+
+Following the same approach that we used for Spring Data and Spring Messaging, the `dapr-spring-boot-starter` brings Dapr Workflow integration for Spring Boot users. 
+
+To work with Dapr Workflows you need to define and implement your workflows using code. The Dapr Spring Boot Starter makes your life easier by managing `Workflow`s and `WorkflowActivity`s as Spring beans.
+
+In order to enable the automatic bean discovery you can annotate your `@SpringBootApplication` with the `@EnableDaprWorkflows` annotation: 
+
+```
+@SpringBootApplication
+@EnableDaprWorkflows
+public class MySpringBootApplication {}
+```
+
+By adding this annotation, all the `WorkflowActivity`s will be automatically managed by Spring and registered to the workflow engine. 
+
+By having all `WorkflowActivity`s as managed beans we can use Spring `@Autowired` mechanism to inject any bean that our workflow activity might need to implement its functionality, for example the `@RestTemplate`:
+
+```
+public class MyWorkflowActivity implements WorkflowActivity {
+
+  @Autowired
+  private RestTemplate restTemplate;
+```
+
+You can also `@Autowired` the `DaprWorkflowClient` to create new instances of your workflows. 
+
+```
+@Autowired
+private DaprWorkflowClient daprWorkflowClient;
+```
+
+This enable applications to schedule new workflow instances and raise events.
+
+```
+String instanceId = daprWorkflowClient.scheduleNewWorkflow(MyWorkflow.class, payload);
+```
+
+and
+
+```
+daprWorkflowClient.raiseEvent(instanceId, "MyEvenet", event);
+```
+
+Check the [Dapr Workflow documentation](https://docs.dapr.io/developing-applications/building-blocks/workflow/workflow-overview/) for more information about how to work with Dapr Workflows.
+
+
 ## Next steps
 
 Learn more about the [Dapr Java SDK packages available to add to your Java applications](https://dapr.github.io/java-sdk/).