We’re implementing a process which includes some waiting stages. The example scenario:
- User creates an order
- System waits for the account to have enough money and deducts (may be several hours or days)
- User continues according to the process.
We’re implementing a custom frontend. Basically each screen is a separate user task in the process.
When the first task is completed via the Java API the call doesn’t return until the next user task is reached.
Is that a correct behavior?
The other question is what is the best approach to implement the waiting states? For example a process is stuck somewhere between user tasks. What would you do to let the user know what is going on in the process? There may be several waiting states in one process.