Better computational access to form components in JavaScript

Issue description

The current solution is difficult since it is hard and verbose to write simply functionality. In addition there are some very specific issues which need to be addressed so that coding becomes easier and more enjoyable.

Developer comments

The specific issues are: 1) Most JavaScript form code is triggered by validation by using onValidate. This function should have an event parameter passing the old value and the new value. 2) If should be possible to set a value only if the form input is empty and/or to require confirmation before changing a value: setIfNull.

The second point above becomes less important if the code clears up. Plus it is easy to avoid, e.g. [% if (form.weight.value === null) { form.weight.value = newWeight; }%]

Reporting date

2026-02-17

Reported by

Robert Cerny

Sub issues3

Automatic datatype conversion in service call from JavaScript(Enhancement)

Form grey because of exception caused by form.js(Bug)

Values not set when custom JavaScript code is run in form(Bug)

Related to

Computational access to form components in JavaScript(Enhancement)

Work sessions6

Start	2026-02-18T06:37:29
End	2026-02-18T10:27:33
Participant	Robert Cerny

Start	2026-02-18T13:00:00
End	2026-02-18T15:00:00
Participant	Robert Cerny

Start	2026-02-18T15:28:55
End	2026-02-18T18:10:08
Participant	Robert Cerny

Start	2026-02-20T07:41:47
End	2026-02-20T18:03:12
Participant	Robert Cerny

Start	2026-02-21T12:25:56
End	2026-02-21T16:13:44
Participant	Robert Cerny

Start	2026-02-22T10:00:00
End	2026-02-22T11:20:30
Participant	Robert Cerny