The current design of the "My Requests" page lists each request name on the left, with the detail view of the selected request on the right (majority) of the page. When introducing the cohort builder though, this will take up more screen estate and make the already cramped looking screen potentially worse.
List/Detail View
Instead, the page should be redesigned into a more typical list/detail view - similar to how account pages would appear on other websites.
The "My accounts" page will lead to the "list" view, displaying in a table:
Each request name
Status
Ancillary details? e.g. dates? (Not essential)
Typical CRUD controls e.g. "View", "Edit", Delete" etc
Selecting a single view will then redirect to a "detail" view of that request, showing the same information as before:
List of data points chosen
Controls to manage those data points
Description
Submit actions
etc
Routing
This will mean a change to the routing as well:
/my-requests - directs to the list view of all requests
/my-requests/{uuid} - directs to the detail view of a request, defined by it's {uuid}
Out of scope
Other than rearranging the pages, the existing functionality should remain. No new functionality should be added at this stage yet.
Background
The current design of the "My Requests" page lists each request name on the left, with the detail view of the selected request on the right (majority) of the page. When introducing the cohort builder though, this will take up more screen estate and make the already cramped looking screen potentially worse.
List/Detail View
Instead, the page should be redesigned into a more typical list/detail view - similar to how account pages would appear on other websites.
Routing
This will mean a change to the routing as well:
/my-requests
- directs to the list view of all requests/my-requests/{uuid}
- directs to the detail view of a request, defined by it's{uuid}
Out of scope
Other than rearranging the pages, the existing functionality should remain. No new functionality should be added at this stage yet.