Steps to reproduce
- log in as srmanager4, create and submit a requisition
- log in as smanager4 and authorize the requisition
- log in as dsrmanager and approve the requisition
- log in as psupervisor and REJECT the requisition
- again submit and authorize the requisition
- dsrmanager should see the requisition and be able to approve it
- psupervisor should not be able to see the requisition and approve it
- dsrmanager can't approve the requisition - it is not visible on the approve screen
- psupervisor can approve the requisition but he should not
the same behaviour is for an emergency requisition
Probably the source of the bug: since the SN is not reset, we are immediately brought to the second approval after authorization.
Set the supervisory node to null when the requisition is rejected.