Hi Clint,
I think this would be a useful addition to the REST API. I have got an alternative idea for the method design, keeping it closer to the resource representation, because suspending and activating is like updating a single property on the execution:
@PUT
@Path("/suspended")
void updateSuspensionState(SuspensionStateDto dto);
with the Dto corresponding to something like {"suspended": true} and depending on the value you could either suspend or activate the process instance.
Then we could in the future also build a @GET @Path("/suspended") method, if needed.
What do you think?
Best regards
Thorben