This sample workflow processes an expense request. The key part of this sample is to show how to complete an activity asynchronously.
- Create a new expense report.
- Wait for the expense report to be approved. This could take an arbitrary amount of time. So the activity's
Executemethod has to return before it is actually approved. This is done by returning a special error so the framework knows the activity is not completed yet.- When the expense is approved (or rejected), somewhere in the world needs to be notified, and it will need to call
client.CompleteActivity()to tell Temporal service that that activity is now completed. In this sample case, the dummy server does this job. In real world, you will need to register some listener to the expense system or you will need to have your own polling agent to check for the expense status periodically.
- When the expense is approved (or rejected), somewhere in the world needs to be notified, and it will need to call
- After the wait activity is completed, it does the payment for the expense (dummy step in this sample case).
This sample relies on an a dummy expense server to work. Get a Temporal service running here.
- You need a Temporal service running. README.md for more details.
- Start the dummy server
go run expense/server/main.go
- Start workflow and activity workers
go run expense/worker/main.go
- Start expanse workflow execution
go run expense/starter/main.go
- When you see the console print out the expense is created, go to localhost:8099/list to approve the expense.
- You should see the workflow complete after you approve the expense. You can also reject the expense.
- If you see the workflow failed, try to change to a different port number in
dummy.goandworkflow.go. Then rerun everything.