Changes between Version 26 and Version 27 of BluePrint/Requests/2.0
- Timestamp:
- 09/21/21 10:44:31 (4 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
BluePrint/Requests/2.0
v26 v27 75 75 <= hrm_commit (orgs) / vol_commit (individuals) 76 76 <= fin_commit (or budget_commit) 77 => req_ acquisition (inc transport_status)77 => req_requisition (inc transport_status) 78 78 <= inv_send 79 79 <= hrm_deploy / vol_deploy … … 83 83 * These would not create a record for the external source, but just the response to it 84 84 * e.g. an external availability request is to be processed into either a commit, or a simple "not available" response 85 * e.g. an external acquisition request would be referenced as document in the inv_send, but not establish an internal req_acquisition record.86 * The internal req_ aquisition entity would be to store outgoing requests only (if requesting to another entity in the same system then it would only be seen like this to the requesting entity, which solves the issue of both sides needing permissions to see the Request...outgoing see it as a resource, incoming see it as a document (e.g. XML or PDF)....or they see it as e.g. inv_req(like inv_recv is to an inv_send in the same system)).85 * e.g. an external requisition request would be referenced as document in the inv_send, but not establish an internal req_requisition record. 86 * The internal req_requisition entity would be to store outgoing requisitions only (if requesting to another entity in the same system then it would only be seen like this to the requesting entity, which solves the issue of both sides needing permissions to see the Request...outgoing see it as a resource, incoming see it as a document (e.g. XML or PDF)....or they see it as e.g. inv_requisition (like inv_recv is to an inv_send in the same system)). 87 87 * req_availability 88 * has a timeframe 88 * has a timeframe (consumable goods would have no end) 89 89 * might be anonymous 90 90 * if not anonymous then the Location could be inferred from the PE (e.g. person=>home address, 91 91 org=>office address, site=>site location) if not explicitly provided 92 * req_ acquisition93 * has a timeframe 92 * req_requisition 93 * has a timeframe (consumable goods would have no end) 94 94 * might be anonymous if using a pick-up mode using an identity-proxy (i.e. ticket, or voucher) 95 95 * if not anonymous then the Location could be inferred from the PE (e.g. person=>home address,