Changes between Version 26 and Version 27 of BluePrint/Requests/2.0


Ignore:
Timestamp:
09/21/21 10:44:31 (4 months ago)
Author:
Fran Boon
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • BluePrint/Requests/2.0

    v26 v27  
    7575  <= hrm_commit (orgs) / vol_commit (individuals)
    7676  <= fin_commit (or budget_commit)
    77 => req_acquisition (inc transport_status)
     77=> req_requisition (inc transport_status)
    7878  <= inv_send
    7979  <= hrm_deploy / vol_deploy
     
    8383* These would not create a record for the external source, but just the response to it
    8484 * 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)).
    8787* req_availability
    88  * has a timeframe
     88 * has a timeframe (consumable goods would have no end)
    8989 * might be anonymous
    9090 * if not anonymous then the Location could be inferred from the PE (e.g. person=>home address,
    9191org=>office address, site=>site location) if not explicitly provided
    92 * req_acquisition
    93  * has a timeframe
     92* req_requisition
     93 * has a timeframe (consumable goods would have no end)
    9494 * might be anonymous if using a pick-up mode using an identity-proxy (i.e. ticket, or voucher)
    9595 * if not anonymous then the Location could be inferred from the PE (e.g. person=>home address,