Answers to: Can we set Case status to DONE?

Comment by Alex Suter on Alex Suter's answer

Alex Suter — Tue, 21 Mar 2017 11:55:14 -0400

No, you can't set status to DONE via API. Boundary signal would be a really nice solution for that.

A Signal Boundary Event destroys an open task of an user if a signal code is received that matches the inscribed pattern.

Comment by trungdv on Alex Suter's answer

trungdv — Tue, 21 Mar 2017 11:31:53 -0400

hi @Alex Suter ♦♦

I totally agree with you that we should set state to DESTROY, it's better than DONE in this situation. And anyway we can't set case status to DONE, right?

I think another way is we can take advantage of boundary signal to clean up the Case.

Thanks

Comment by Alex Suter on Alex Suter's answer

Alex Suter — Tue, 21 Mar 2017 11:12:22 -0400

Hi @trungdv

The logic is as follows: In the special case if task A1 is done, tasks of Task B1 and Task C1 must not be done anymore. From an user point of view I would like to see, that Task B1 and Task C1 are not really done - because nobody really did the work. They are destroyed. You also can destroy on task level ITask#destroy.

But you have to ask you the following question: Is it a good solution to have parallel tasks, when some of them not have to be done, when another task is done? The user may do some unnecessary work.

Comment by trungdv on Alex Suter's answer

trungdv — Tue, 21 Mar 2017 07:32:50 -0400

Hi @Alex Suter ♦♦

My case is:

I working on task A1 belongs to case A
task A1 have a button, and when I click on that button, case B and case C must be set to DONE (their tasks also)

Answer by Alex Suter

Alex Suter — Mon, 20 Mar 2017 10:11:29 -0400

There is no API to set the case status to DONE. A case is DONE when all tasks of the actual case are done. You have the opportunity to DESTROY ICase#destroy() a case manually. Can you explain your use case?