Hot answers tagged

3

I think you can get close with just a couple of changes from where you are now. Have a different and informative CTA for the requirements Currently you have 'Save' (local) and 'Save all changes' (global). This seems potentially confusing. If you changed the CTA to something like the following, the user would be made aware that this change is local, not ...


1

I think modal could be an overkill, as it will take the focus away from the page - and moreover its not justified for something like an edit function in the context of the application. Take a look at the below suggested flow: 1) Initially, the user is visually shown which are the editable vs non editable categories. As seen, Reqs are shown to be editable, ...


1

"The earlier system just had all fields editable at all time, which avoided this problem - is that still the best way to go?" Yes. What is the difference between the fields of a requirement to the fields of its evaluation? - None. The evaluation fields are also "saved" locally and you do not have 'Save' and 'Discard' buttons for them, and that's because ...


1

What is the ultimate goal for the user? Evaluate the Law? Edit the Requirement? Edit and Evaluate? I suspect the ultimate goal is to just Evaluate, and if so this should be the primary Call to Action trigger. I also suspect that Editing the Requirement is an occasional supplementary activity so it's trigger needs to be very different to the primary ...



Only top voted, non community-wiki answers of a minimum length are eligible