Skip to content

Commit

Permalink
Add workflow_type to PurchaseOrder state
Browse files Browse the repository at this point in the history
This adds the `workflow_type` field to `PurchaseOrder`'s state
representation. This will mark which workflow the PurchaseOrder is/was
going through.

Signed-off-by: Davey Newhall <[email protected]>
  • Loading branch information
dnewh committed Sep 24, 2021
1 parent 6eb8ffa commit 5c11846
Showing 1 changed file with 9 additions and 6 deletions.
15 changes: 9 additions & 6 deletions text/0025-purchase-order.md
Original file line number Diff line number Diff line change
Expand Up @@ -430,6 +430,8 @@ IDs included in the `PurchaseOrder` should refer to the same organizations.
- `uid` - Unique identifier for Purchase Order
- `workflow_status` - Workflow status. Values are defined by the smart contract
workflows
- `workflow_type` - Workflow type. The name of the workflow that the Purchase
Order will proceed through.
- `buyer_org_id` - Grid Pike organization ID associated with the buying
organization defined by the XML in the purchase order's `order_xml_v3_4` field.
- `seller_org_id` - Grid Pike organization ID associated with the selling
Expand All @@ -444,12 +446,13 @@ accepted
message PurchaseOrder {
required string uid = 1;
required string workflow_status = 2;
string buyer_org_id = 3;
string seller_org_id = 4;
repeated PurchaseOrderVersion versions = 5;
string accepted_version_number = 6;
uint64 created_at = 7;
bool is_closed = 8;
required string workflow_type = 3;
string buyer_org_id = 4;
string seller_org_id = 5;
repeated PurchaseOrderVersion versions = 6;
string accepted_version_number = 7;
uint64 created_at = 8;
bool is_closed = 9;
}
```

Expand Down

0 comments on commit 5c11846

Please sign in to comment.