[Task testing] Handle waiting states of common elements (receive task, service task, user task) #69
Description
Is your feature request related to a problem? Please describe.
The current experience of using the task testing feature looks like this:
Camunda_Modeler_0x8Yw76HQc.mp4
- after deploying and creating a process instance the task testing feature will show a loading indicator until the process instance is finished (canceled in the case of task testing)
- users must go to Operate to find out what is happening and why the process instance isn't finished
- Operate doesn't help users understand why the process instance isn't finished (e.g. user task with form waiting for completion)
Here are some scenarios that are frustrating:
Service task with job worker either not starting or finishing the job
- indefinite loading state
- process instance active in Operate with no hint what to do
Camunda_Modeler_IKUuQuh06Z.mp4
What you see in Operate:
User task with form waiting for completion
- indefinite loading state until user task is completed
Camunda_Modeler_daSpbWrKSM.mp4
What you see in Operate:
Receive task waiting for message
Camunda_Modeler_S1tmIt5RoD.mp4
What you see in Operate:
Describe the solution you'd like
- 🧑🦱 when a task is executing I want to understand what is blocking task completion
- 🧑💻 in order to help users understand what is blocking task completion I want to query a single orchestration cluster endpoint
- there are existing orchestration cluster endpoints (
search-jobs,search-user-tasks,search-message-subscriptions) which could be made accessible through a single endpoint initially
- there are existing orchestration cluster endpoints (
Describe alternatives you've considered
Play handles some of these scenarios with the added ability to complete tasks directly from the UI:
However, all of these are custom implementations using various existing endpoints (search-jobs, search-user-tasks, search-message-subscriptions).