Add partner node extended property to supervisory node model

Description

A way to support splitting requisitions and supply partners having their own approval/fulfillment workflow is to assign them a supervisory node. This node would be related to the "main" node through a partner node property. Then one factor to determine if a requisition should be split is if the next node has partner nodes.

This includes changes to the UI to manage this property.

Acceptance criteria:

  • a new extraData field should be added to supervisory node resource

    • There can be multiple partner nodes so the field should support many partner nodes

  • UI changes have been moved to OLMIS‌-5628

  • The GET /api/supplyPartners endpoint should be able to retrieve several partners by ids.

    • GET /api/supplyPartners?id={‌{id1}‌}&id={‌{id2}‌}&…

Activity

Show:
Joanna Szymańska
October 26, 2018, 1:19 PM

Thank you for the explanations, indicated endpoints work correctly, and the new field "extraData" is visible and accepts all values.

Łukasz Lewczyński
October 26, 2018, 9:18 AM
Edited

Please verify:

  • that you can retrieve several supply partners by ids

  • there is a new extraData field in the supervisory node

  • you can add an entry with any key - for instance supplyPartnerIds - with a list value - for example, a list of supply partners. For now, the list is not validated so you can put any values.

Nikodem Graczewski
October 24, 2018, 3:56 PM

to create a ticket for editing supervisory nodes and mark it as a blocker for this one.

to update the ticket with adding and removing supply partners.

Is it a problem if the supply partner related table is visible if some implementation is not using them?

Łukasz Lewczyński
October 22, 2018, 11:35 AM

I added acceptance criteria and left two questions related to them.

Done

Assignee

Łukasz Lewczyński

Reporter

Chongsun Ahn

Labels

Story Points

2

Time tracking

0m

Time remaining

27h

Components

Sprint

None

Fix versions

Priority

Major