Did you place EPM-demote handler arguments on Checker_Review task?
If not if you need to place the below arguments
It looks like you need a Reject Path back to the Self_Review task. Without it, TC does not know where to Reject to. So essentially the Checker_Review task simply restarts which results in the Decision being reset to No Decision.
From the Checker_Review task, create a path (arrow) back to Self_Review. Then right click on the arrow and set it to a Reject path.
I tried this, but this handler just directs the rejected task to specified one. If You want to reject it to previous task, this option is not necessary.
The problem is that the field Desicison remains with comment No Decision. This is due to handler EPM-demote-on-reject.
In the notificatino email it looks:
I do not understand it. The problem is not that the the rejected process is rejected nowhere. It comes back to Self_control (or self review) - to previous task - this works fine (I guess this is done due to EPM-demote-on-reject), but the problem is that the display of Decision field is as No Desicision.
I know about this workaround to define reject path, but when it comes back to self_review I can not define email notification just in case of rejection. In this case also the handler EPM-demote-on-reject must be erased.
I'm not sure that I'm following you exactly.
For a notification only on Reject, you can use the EPM-notify-report handler (with the -report=rejection argument) on the Perform-Signoffs task under Checker_Review . Be careful of the placement (refer to TC Documentation) for rejection only.
OOTB behavour will show the Checker_Review task as failed after rejecting it.
The way that I have it configured that the demote happens and then the email is sent.
The demote resets to “No Decision”
I made a slight change and reordered the handlers.
Note you cannot just move them. I deleted the EPM-Demote-on-reject and created again
You can test this scenario and let me know.