# 96. Mandatory fields in decisions

**URL:** <https://community.triggre.com/t/96-mandatory-fields-in-decisions/838>\
**Category:** Weekend masterclass\
**Tags:** designer, decisions, flow-parts\
**Created:** [December 13, 2024, 8:06am UTC](https://community.triggre.com/t/96-mandatory-fields-in-decisions/838 "2024-12-13T08:06:05Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Marta](https://yyz1.discourse-cdn.com/flex035/user_avatar/community.triggre.com/marta/32/87_2.png) [@Marta](https://community.triggre.com/u/Marta)\
**Post date:** [December 13, 2024, 8:06am UTC](https://community.triggre.com/t/96-mandatory-fields-in-decisions/838/1 "2024-12-13T08:06:05Z")

</div>

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!

[![](https://canada1.discourse-cdn.com/flex035/uploads/triggre/original/1X/d839a1f51e9885cd1f090bc13ca0302928473d1e.jpeg "Mandatory fields in decisions | Triggre Weekend Masterclass") ](https://www.youtube.com/watch?v=uM2z78iuIMU)