Feel free to take a stab at creating a mock-up. To be honest, I barely have the bandwidth for the implementation.
That might make validation and updating for future features simpler, yet I think it would be a good idea to first do some UI scibbles and discuss about the workflow, before implementing it.
Mit freundlichem Gruß
Alexander Rühl
Lead Domain Expert Java
valantic Software & Technology Innovations GmbH
alexander.ruehl@xxxxxxxxxxxxxxxx |
+49 6196 64066 0 | +49 171 4818859
Kölner Str. 3 | 65760 Eschborn
www.valantic.com
Geschäftsführer Dr. Markus Eisel, Stefan Billeb
Sitz der Gesellschaft: Eschborn - Amtsgericht Frankfurt am Main HRB 129301
Umsatzsteuer-ID Nr. DE256147936
Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte Informationen. Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtümlich erhalten haben,
informieren Sie bitte sofort den Absender und vernichten Sie dieses E-Mail. Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser E-Mail sind nicht gestattet.
This e-mail and any attachments contain confidential information addressed to a specific recipient(s) which is private and protected by law. If you are not an addressee,
any disclosure, copying, distribution or use is strictly prohibited, and you are requested to advise us immediately of the information you have received.
EXTERNAL SENDER: Be cautious with links and attachments!
Hi folks,
I just fixed the GitHub Actions workflows, so the nightly builds should be back to normal again. It looks like some UI validation bugs were introduced as well as part of the UI changes, which I will fix ASAP.
However, I am also thinking about introducing the concept of a workflow into the UI. I think changing from radio buttons to drop downs makes that a more sensible thing to pursue now.
What I am thinking is to enable/disable the valid options only for the next field in the workflow on each selection in sequence and clear/disable all the subsequent fields. The submit button will be enabled only when all non-optional fields have been filled
out.
In addition to introducing a conscious workflow, this should significantly simplify the validation logic as you only really need to deal with validating the state of one field per update as opposed to trying to keep all fields valid at all times. As you know,
I had been trying to simplify the validation logic for some time, and I think this will really do the trick without compromising usability.
Please share thoughts? Otherwise, I’ll begin to roll out these changes as time permits. I’ll also update the runtimes and versions to the latest. I’ll make sure at least some key folks like Jeyvison review and test the PR since these are quite significant changes.
Cheers,
Reza
