Trade of devices

[forste]

The trade of documents is implemented here #76

1) Add supplier to temporary lot & convert to incoming

On backend, this should convert the temporary lot to an incoming lot and create an associated trade for all devices of that lot

@cayop what's the API endpoint to add a supplier to an temporary lot and change a temporary lot to an incoming lot?

2) Add receiver to temporary lot & convert to outgoing

On backend, this should converts the temporary lot to an outgoing lot and create an associated trade for all devices of that lot

@cayop what's the API endpoint to add a receiver to an temporary lot and change a temporary lot to an outgoing lot?

3) Add device to incoming lot & add to trade

On backend, devices get added to the trade of the lot automatically

The device added to the trade is only confirmed by the user having added the device.

4) Add device to outgoing lot & add to trade

On backend, devices get added to the trade of the lot automatically

The device added to the trade is only confirmed by the user having added the device.

5) Action Trade for devices

On backend, this creates an outgoing lot and an associated trade with the selected devices

5) Action confirmtrade for devices

When the 2nd user confirms the trade, the ownership (control in DH) is changed automatically

6) Action revoke for devices

7) Action confirmrevoke for devices

When the 2nd user confirms the trade, the ownership (control in DH) is changed automatically

8) Show status confirmed / non-confirmed for trade and revoke for devices

[cayop]

There are one test for the first part of the classic use case in dhub

All endpoints for enveriment trade are the same of every action.

1) The supplier is added when the action trade is created.
The params for to do one trade is:

request_post = {
        'type': 'Trade',
        'devices': [],
        'userFrom': scrap.email,
        'userTo': manager.email,
        'price': 10,
        'date': "2020-12-01T02:00:00+00:00",
        'lot': lot['id'],
        'confirm': True,
 }

We can change this behaviour, because now we need pass the both users. We can send one user and force that the api use the validate user in the api for the other user.

2) the same structure than the 1)

3)* and 4) we don't to do nothing new in the frontend

5)
the params for one confirmation is like this:
Confirm

request_confirm = {
         'type': 'Confirm',
         'action': trade.id,
         'devices': [
             device1.id, device2.id, ...
         ]
     }

Revoke

request_revoke = {
         'type': 'Revoke',
         'action': trade.id,
         'devices': [
             device1.id, device2.id, ...
         ]
     }

Confirm Revoke

request_confirm_revoke = {
         'type': 'ConfirmRevoke',
         'action': revoke.id,
         'devices': [
             device1.id, device2.id, ...
         ]
     }

Pay attention that confirm and revoke are actions that go against the trade action.
While "confirm revoke" is a action that goes against the revoke action

[forste]

Hi @cayop,

thanks for your response.

Regarding 1) and 2), what is the URL of the endpoint? where does the POST go to? (e.g. POST /trade)

[cayop]

The endpoint is the same of the actions:

POST

http://api.testing.usody.com:8080/usodybeta/actions/