Add a "Show" action under the Rules tab
The current Rules tab features only four (4) possible actions: Hide, Disable, Display Only, and Required. Some customers have workflows that require the "Show" action, but were unable to do so because this option is not available. It's also because the Rule actions, just like other features like table views, are built on NEGATIVE logic, which is sometimes hard to grasp.
The current workaround, which I find tedious and error-prone, is to use the Hide action to implement the NEGATIVE/opposite logic of the required "Show" criterion. For instance, if you want to SHOW a text field named FirstName if another field is set to "Not a Member", you have to implement it using the Hide action with the condition FirstName is NOT "Not a Member".
Ryan Gatchalian
shared this idea
-
Russell Parker commented
You are correct about it taking a bit to wrap ones head around, however there is likely a reason for it. I am guessing this is because properties default to "False" since 0 is nice and unambiguous. Since the generally desired behavior is to have the field be Visible the property gets implemented as "Hidden" since "Hidden=0" causes the field to be Displayed/Shown.
I used to do Technical Support for an Enterprise ITAM application and the was a Field Property called "Irrelevant". By default is was False and Irrelevant=False is... well... Relevant. Had to explain that double negative many times. What it comes down to is programmatically testing again False is cleaner and more bullet proof than testing against true. In just about every language/system I have worked with False=0, but I have seen True be defined in a variety of ways. Everything from True=1, True=-1, to the most entertaining version which is True=Not(False). Anyway... just some thoughts about why the Negative/Opposite logic is not just capricious or crazy. :)