For a workflow, in a method, an "Execute Workflow" service needs to be ran. This will move it to the next status and run the Complete Event on its current status. Here is what that looks like in the logs of the Execute Workflow service
It cant communicate anything about the final state of the complete event. It returns what status it moves to, but it cant tell anything about what happened in the Complete Event. This is a really good setup when the Complete Event was only going to send an email (very simple workflow use), but for more complex uses, it is necessary to know what happens when it runs.
This could be relevant when:
- We need to know if the sent email was succesful
- the complete status is performing some validation and when it fails we need to tell the user why it failed
See in this workflow, if the workflow request is at "SupplyChainFinance", when the executeworkflow service is ran, it will go to the "CostingIntegration" status and run the arrival event. That status performs an action and if it errors, automatically sends it to "ErrorCostingIntegration".
So this means that when the ExecuteWorkflow service was ran it could want to know info from:
- SupplyChainFinance complete
- CostingIntegration arrival
- CostingIntegration complete
- ErrorCostingIntegration arrival
- ErrorCostingIntegration complete
The ExecuteWorkflow service is waiting for these to finish before it returns the logs, so I think it would be possible to return some message from any of those.
Can we make "MethodOutput", or some other service return, return a node in the execute workflow service to relay information back about what happened. This could be called from any of the Events that ran which were triggered by the execute workflow service.
Translation