IMPLEMENTED: Component properties as conditions

Being able to use component properties as conditions within a component would be useful. For example, don’t include an element if a property is empty or do something different if a property value matches a certain string.

I don’t see that functionality, nor a feature request. Apologies if I missed it.

1 Like

It is implemented and oartially works.

This essential feature is not documented, so several more threads with the question will occur.

I don’t recall seeing an option in the list of conditions.

It’s there for text for example

Select Dynamic data, then the purple + sign and pick one of the component fields.

1 Like

Mileage may vary. The text properties are available in the condition builder but it’s not working when building conditions based on the values of those text boxes for us

1 Like

Not working for me either. Super limited as well as no checkboxes or dropdowns.

When anything is entered into the instance it still doesn’t show the element.

This still isn’t working. Is there a date when it will be fixed (ETA)?

Hoping this gets fixed soon.

At the moment, no condition comparisons operate as expected.

1 Like

Still not working.

If we can select the dynamic fields in the conditions, it should be letting us test against the values as well. Otherwise what’s the point of having the dynamic field available to select?

Hey guys,

Please be informed that this has already been implemented in 2.0-alpha