It seems that if I suspend a process that has active user tasks there is no way of identifying the tasks that are suspended or (which would be better) to tell the taskService to exclude them from the result set.
Did I miss something?
If not does this sound like a reasonable enhancement to TaskQuery?
To prevent activity on the process instance for a period of time (mostly human activity but perhaps service tasks too), but with the expectation that the instance will (or may) be reactivated at a future state.
Maybe it helps to consider an analogy to having your bank account suspended (both at ATM and face to face at branch) until you call a dedicated fraud team to reset security after some suspicious activity on the account.