As a facility manager, I want to authorize a requisition created at my facility (before sending it on for approval at a higher level) So that I can delegate responsibility for creating the requisition while still having a final review before the requisition is submitted.
Note: I do not know the genesis of this requirement and whether it is critical that it be in place for 3.0 (i.e. Malawi)
user (which user is determined by the supervisory node up) can view the submitted requisition
mechanism to 'approve' the submitted requsition
requisition status changes to 'authorized'
if approved, authorization is sent for approval
Behavior functions as in current OpenLMIS 2.0 system, where after a requisition is saved, it moves to "need authorization" state.
Important Note: The authorization step is optional. NOTE: unclear whether this exists in 2.0, but this step should be optional. An administrator can configure (via upload or CRUD) whether a requisition must be authorized by a supervisor before being sent from the facility.