yuuvis® RAD Q&A

0 votes
by (2.9k points)
retagged by

When we have a read-only input field, lets say "msg". then we cant use scope.model.msg.error = {msg: myError}; If the field is writeable, everything works fine.

We need to use the workaround with the formscript and error function because its not possible to evaluate the start conditions of a process.

I know it does not make sense to have an error method on a read-only field, but at the moment we are forced to use this workaround. It should just tell the user an information "are you sure to start the process".

Any other suggestions to set an error on a formscript?

2 Answers

+1 vote
by (14.8k points)
selected by
Best answer

This current behavior is correct.
The correct solution would be to set the complete form as incorrect including a message as it is for a field -> CR -> Story-Ticket COOL-8114, will come within the next iterations.

by (1.2k points)
Hello Martin,
is there any information if it will be possible to set an error to readonly fields?
by (14.8k points)
This ticket is still in the backlog for version 5 and will not be delivered before april 2019.
0 votes
by (2.9k points)

We would change the read-only msg field to an optional notice field, where the user can enter some additional information. On this field we can set an error. This field wouldnt be necessary. It would nice to have an method at the startform to throw an error.