I have a customer that is doing extensive configuration on their portal to allow for the capturing of data. They are on Cherwell V9.2.1.
The issue that they are experiencing is that disable expressions on numeric fields do not disable the fields even when the conditions are met. As a work around they are hiding the fields and displaying a label but this is tedious as it results in having to add the field and a label to the form and then have 2 sets of visibility rules for each control on the form.
Has anyone else had this issue, and if so, how can I resolve this?
I haven't disabled fields via expression myself, but would setting a read-only expression meet the criteria instead? Field is non-editable by user and only one-steps can update it.
I did attempt this and for other fields types it works, but not for number fields.
We tested this in 9.40a and the issue still exists, so our next step is to test this in 9.6.1.
As a work-around, I put a visibility rule on the field on the form to make it invisible, and then added a label to show the value of the field with the opposite visibility rule attached. This is a workable work-around for the customer, but this does result in do double work per field.