Changes between Version 11 and Version 12 of BluePrint/Requests/2.0


Ignore:
Timestamp:
09/19/21 21:09:41 (21 months ago)
Author:
Fran Boon
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • BluePrint/Requests/2.0

    v11 v12  
    3939=== Cons ===
    4040* Still end up with 2 separate Requests systems
     41
    4142== Proposal 2 ==
    4243Replace both req_need & req_req (& associated tables) with:
    … …  
    6970* End up with a single Requests system
    7071=== Cons ===
    71 * Using pe_id for requester means that we are directly accessing an SE, which is bad for permissions (can't differentiate by instance_type)
     72* Using pe_id for requester means that we are directly accessing a !SuperEntity, which is bad for permissions (can't differentiate by instance_type)
    7273* HRM (~mandatory model) has a link to Req (optional module) which should be avoided
     74
    7375== SHARE ==
    7476There are also some models which are just used by SHARE & should be moved to that template (as share_*):