Add v2 endpoints to RequisitionController

Description

There is a need to add a second version of several RequisitionController endpoints. These endpoints will return DTO objects which meets FTAP/Orderable versioning approach. The deleted fields will not be present in the response. The new fields representing versioned Orderable/FTAP will be added instead.

The deleted/added fields are listed in and

Acceptance criteria

  1. The endpoints should be available via "/v2/" in URL

  2. The endpoints return object reference to Orderable & FTAP

  3. Three new v2 endpoints are added to RequisitionController

    1. initiate

    2. updateRequisition

    3. getRequisition

    4. getSubmittedRequisitions

  4. The internal handling should be the same as the current one

  5. The existing endpoints should not be changed and should still work

    1. the response should be the same

There is no need to add the v2 versions of BatchRequisitionController
This issue has been created basing on design discussion

Assignee

Łukasz Lewczyński

Reporter

Paweł Cieszko

Labels

Story Points

5

Time tracking

36h

Epic Link

Components

Sprint

None

Fix versions

Priority

Major
Configure