Hi
I am currently working on a camunda headless implementation. There is an external UI (built in Angular) talking to Camunda and to external business services (microservices). The role of camunda is a little more than just orchestration of apis.
Following is the approach which I have in mind.
For eg. when the user submits a form, the UI sends a REST API call to Camunda to complete the task. Camunda captures the form data and sends it to a third party business service which would insert/update the data in its system, returns a response to Camunda. Camunda then looks at the response and completes the task, retrieves the next task and sends it to UI
In short,
UI → Camunda (sends request to)-> Microservice (returns back with response to)-> Camunda (completes the task, gets next task) → Sends it to UI
[Start] → [Task 1] → [Task 2/End]
Should I model this task as a User Task or a Service Task ?
If I model as User Task, I am not sure how to accept the incoming request, perform an async operation(microservice call) and complete the task and retrieve the next task.
If I model as a Service Task, how do I stop the user at Task 1 if he has not filled up all the mandatory fields in the UI ?
Please let me know a solution to this problem and your thoughts about my approach in connecting with the micro services.
Thanks
Shameer Salim