both the “set ReadOnly” and “set Disabled” actions of the textInputObject are not working at all in the engine or on the webApp, tried on various projects calling the actions with and without conditions, nothing happens. The current workaround is to have two versions of the object (one readOnly the other notReadOnly, and create/destroy them accordingly.
(not a problem with the project as this bug is happening in every project)
You’re not alone. Someone else recently had the same issue. The actions don’t work for me either. The object settings do but that’s not helpful if you can’t enable it with actions. Nice workaround. Hopefully, they’ll start fixing some of the recent bugs.
I wonder if the Javascript works. That could be another temporary workaround.
thanks for confiming that i´m no alone. I would have tried javascript just for testing purposes but I don’t know any.
This was fixed in the last update.