Validation of a constant in Dropdown

RE: Validation of a constant in Dropdown

saarcenal — Tue, 18 Jan 2022 01:40:15 GMT

This worked for me. Thanks! I was fixated in using 1 constant only

RE: Validation of a constant in Dropdown

Stefan Helzle — Fri, 14 Jan 2022 10:41:08 GMT

Got it.

Our approach to status value is, that we have an individual constant for each value. Then we can reference each value clearly and also use it for comparisons.

To get a list of all values, we then create an expression which returns a list of all the constants.

In a task form, you could then just list the values you need for that form.

And if you use a reusable component, you could create a local holding the values matching the current status. A decision table can do that as well.

RE: Validation of a constant in Dropdown

saarcenal — Fri, 14 Jan 2022 10:32:15 GMT

I think I worded it wrongly. What I'm trying to say is the dropdown should differ depending on the status.

Example, if status is currently closed, then I should only see closed and cancelled.

Or if the status is open, then I should only see revising and reviewing on the dropdown.

RE: Validation of a constant in Dropdown

Stefan Helzle — Fri, 14 Jan 2022 10:22:56 GMT

Wouldn't it be easier to use a textField in readonly to display that value? This is what I am doing. DropDown for modification and a textField for display. Of course, you can also use a richTextField etc.