UI for License term configuration
(UXPROD-1521)
|
|
| Status: | Closed |
| Project: | UX Product |
| Components: | None |
| Affects versions: | None |
| Fix versions: | None | Parent: | UI for License term configuration |
| Type: | Sub-task | Priority: | TBD |
| Reporter: | Gill Osguthorpe | Assignee: | Unassigned |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original estimate: | Not Specified | ||
| Attachments: |
|
| Description |
|
There are two UI options which we could adopt. Owen is keen to take the path of least resistance. md331 and Aditya matukumalli, could you please take a look at both options and guesstimate the time to implement, or just say which you think will be the most straightforward. Option 1 - three panes In this approach, records are created in the same pane as the list of terms. It is used frequently by other apps but does not respond well in narrower browser widths and has not been used yet to display records with more than 4 fields. This example shows how the Cancel button is lost, and how little space is available for entering a description: For license terms, we will need to display the following fields for each term:
The question is can the current UI handle this number of fields in one row, and if not what needs to happen to make it possible? For example, collapsing the row group so that it spans more than one row in the UI, or displaying it as a card. Option 2 - 4 panes Data Import uses a four pane approach, with the Edit pane displayed full-width. This approach will solve the layout issues, but is it more time consuming to deliver? Mockups are below (have not done the Edit pane yet). |
| Comments |
| Comment by md331 (Inactive) [ 08/Aug/19 ] |
|
Option 1
Option 2
Option X
|
| Comment by Gill Osguthorpe [ 09/Aug/19 ] |
|
Thanks md331. Introducing the card layout gets my vote. |
| Comment by Owen Stephens [ 12/Aug/19 ] |
|
Thanks all. Will update
Note that "Licenses using this term" is not a requirement in the configuration |