In today’s Triggre Weekend Masterclass, Eddie explains why mandatory fields can never be empty and how this influences application logic. When a field is marked as mandatory, Triggre recognizes that it is impossible for that field to be empty. As a result, when creating decisions based on this field, the option to set a logical path for the “empty” condition is not available.
While you can create logic for non-mandatory fields being empty, Triggre disables this for mandatory fields since they are always required to have a value. This feature helps avoid confusion during logic design, ensuring developers consider the mandatory status of fields. If you ever face this situation, be sure to check the field settings!
