Adjust Requisition Line Item fields to use FTAP versioning

Description

There is a need to support FTAP versioning in Requisition Line Item class. We need to remove and add several fields to stop using snapshotted (copied) values and retrieve the values by fetching the referenced (versioned) entity.

Acceptance criteria

  1. Adding FTAP id and FTAP version to RLI - to reference an FTAP in RLI to handle multiple version

  2. Removing maxPeriodsOfStack from RLI entity - this field is currently snapshotted (copied) from FTAP. After adding a reference to FTAP, the FTAP fields shouldn’t be stored in RLI but retrieved from FTAP on demand.

  3. Id and version should be encapsulated in one class eg. EntityReference.

  4. There should be a migration committed for the existing RequisitionLineItems.

  5. Fix v1 endpoint handling to use calculated fields

This issue has been created basing on design discussion

 

  • Before commiting the changes, should we assume that current FTAP always represents snapshotted values?

    • Yes

  • How should we migrate already snapshotted value when orderable has been changed?

    • always use the latest version

 

Status

Assignee

Paulina Buzderewicz

Reporter

Paweł Cieszko

Labels

Story Points

5

Time tracking

80h

Epic Link

Components

Sprint

None

Fix versions

Priority

Major
Configure