Changes between Version 11 and Version 12 of BluePrint/Requests/2.0
- Timestamp:
- 09/19/21 21:09:41 (21 months ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
BluePrint/Requests/2.0
v11 v12 39 39 === Cons === 40 40 * Still end up with 2 separate Requests systems 41 41 42 == Proposal 2 == 42 43 Replace both req_need & req_req (& associated tables) with: … … 69 70 * End up with a single Requests system 70 71 === Cons === 71 * Using pe_id for requester means that we are directly accessing a n 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) 72 73 * HRM (~mandatory model) has a link to Req (optional module) which should be avoided 74 73 75 == SHARE == 74 76 There are also some models which are just used by SHARE & should be moved to that template (as share_*):