Epic:

- a boolean field indicating whether a program should display non fully supply fields was added. This should be used on the UI.

- saving and editing requisition templates. Templates are unique per program.

- creating periods related to schedules is possible. Validation is present.

- changing name is possible through updates. Currently there is no dependency on the name anywhere.]

- requisition template columns have an order field. Displaying in an ordered manner is left to the UI.

- Schedules can be created and updated. Schedules are currently not associated with programs!
There exists an entity mapping a schedule to a program, but it is not used for any validations etc.

- currently this is only a field in the requisition line.
The acceptance criteria should be reviewed.

- A non full supply attribute has been added to programs. No calculations were done as part of this ticket, as they are not mentioned in the acceptance criteria. Is this covered by a different ticket?

 - Skippable flag is added to a program.
Currently we have no period validation when creating a requisition.

- A column of the requisition template can be mark as displayed/non-displayed

- Attributes marking a column as non-movable have been. However the program columns itself hasn't been added - we need a ticket which will encompass adding the predefined columns and their calculations.

  - Same as above

- Beginning balance was added and is calculated, but currently is not directly tied to the requisition template, since we are missing predefined columns.

- Names can be edited

Epic: 

- Saving basic requisitions is possible. As mentioned previously there is no validation check for periods when creating a requisition. Make sure the SDR edit is properly translated to MVC edit.

- Deleting was implemented and only initiated requisitions can be deleted.

- Done similar to v2 - you create a requisition with a skipped status. There might be a better solution however. Investigate!

 -
A requisition object can be created through the API with the initiated status. This is just creating a basic object and tying with the mentioned fields. The template does not come in to play here.

- Stock on hand is not calculated. 

- The field "requested quantity" is required

Template - missing letters representations (can be done on UI??). Missing calculation formulas and calculation logic.

Epic

- Converting to orders is done. Order file is generated during the print action. Status check on the requisition is missing.

 - Requisitions can be rejected and go back to initiated status. Only authorized requisitions can be rejected here. RBAC and audit log is not present. 

Epic

 - skipping is currently configured as a global variable. When it is configured, it's possible to approve an unauthorized requisition. There is a disrepancy between checks in reject/approve requisition - approve does not take this into consideration. We should switch this to the save phase (set status to authorized during submit), instead of doing this on the read phase.

- and endpoint for searching trough requisitions has been added. It allows searching as described in the acceptance criteria.

- authorize and approve seem to be  mixed up in the acceptance, it should be re-checked. Authorizing is done and changes status from submitted to authorized. Rbac and audit log are not present.