108 | | * Using pe_id for requester means that we are directly accessing a !SuperEntity, which is bad for permissions (can't differentiate by instance_type) |
109 | | * use this for just 1 instance_type at a time: variable single type NOT mixed type (mixed type can be seen as poor UX by users, as well as the permission issues) |
| 115 | * Using pe_id for requester |
| 116 | * means that we are directly accessing a !SuperEntity, which is bad for permissions (can't differentiate by instance_type) |
| 117 | * so use this for just 1 instance_type at a time: variable single type NOT mixed type (mixed type can be seen as poor UX by users, as well as the permission issues) |
111 | | * have separate UI paths for the different options (Like Asset's 'Assign to Person'/'Assign to Org'). |
112 | | * use a custom widget to display the separate options (most costly to build) |
| 119 | * have separate UI paths for the different options (Like Asset's 'Assign to Person'/'Assign to Org') |
| 120 | * differently-filtered pe_id |
| 121 | * server-side page refreshes |
| 122 | * AJAX-load the different options |
| 123 | * use a custom widget to display the separate options |
| 124 | * e.g. have all 3 dropdowns in the form, but hide the ones not currently selected |
| 125 | * proxy fields in the form |
| 126 | * Simple to develop, although lower performance needing to load all the models each time even when not all needed |
| 127 | * AddResourceLink needs adjusting to support pe_id instead of id (& mixed-instance_type needs this adjustable with the options) |