Field behavior control
Field validation is not enough. In addition to “hide object when” in inspector we need the ability to enable or disable field edit with a calculation.
Edit protection can already be enforced at the data layer via privelege sets in security. There are also ways to enable calculations and object triggers to enforce this data protection.
OK, Chris, but this feauture also would ensure that the field gets a disabled/enabled state. These states would be editable in the styles section.
Duplicate of many ideas, including the ones listed here:
Hopefully this fact alone is getting FMI's attention
Retrieving data ...