Form Field: Set as Disable - usage of the "Set as Disabled" yes/no
Problem/Motivation
Hello - I tried using the task Form Field: Set as Disabled. I was able to successfully set a form fields to disabled (working as expected). However, I thought I can use the same task to enable a form field, since the task has a drop down selection for "Set as disabled" with the options yes/no. To disable a field, I set the selection to yes. To enable a field, I though I can just select the option to "no". However, this is not working (the fields is not getting enabled as expected). Perhaps this is a bug, or perhaps I'm not understanding the correct usage of this yes/no dropdown? (Please see attached image). Thank you!
Steps to reproduce
1. Create an ECA model with a "After Build Form" event using a form that has a field set to disabled.
2. Create a flow (no condition needed)
3. Create a task: Form Field: Set as Disabled. Enter the name of the field. Select the "Set as disabled" option to "no".
4. Reload the form with the ECA rule enabled.
5. Observe that the field is not enabled (still remains in disabled state)