Enabled State on Inputs

1

The ability to configure enabled state of a button based on an expression has been a seismic improvement for architecting app logic. It makes error handling so much easier and at times even has prevented me from adding steps.

This same pattern could be applied to inputs for similar benefits. Preventing users from accessing input fields could be done in an extremely similar way-- I believe just setting the html element to a status of disabled.

For a simple example, this would allow for Add Record and Edit Record pages to be very easily consolidated into one step, where certain fields are usable if the record is null, and certain fields are disabled when you are editing. This way certain fields could be locked from editing.

There are probably many other examples. This would also have the benefit of ignoring the disabled input field while tabbing through an application.

2 Likes
2

Hi Daniel,

For some data presentation we show data from the loaded table record as an input widget (e.g. a boolean showing sampling or cleaning required as the table record). This avoid duplicating the data into a variable after loading. But we don’t want the operator to click it, so we place a transparent box over the widgets. Obviously this isn’t really a bulletproof solution as the users can tab their way to the widget and use space to change the value as shown in video below. Null/blank values are also not depicted so well for input boolean widget.
I fully support your idea.

thx
asger

3

I had a similar idea to you today and my friend ChatGPT made these for me :smiley:

customWidget-Single Select drop down- enabled_disable.json (2.4 KB)
customWidget-Single Select radio list- enabled_disable.json (2.6 KB)