Required attributes based on other attributes
In projects, you can require an attribute that is based on another single-select drop-down attribute. For example, you can configure a form to require the postal code attribute if the user selects "United States" from the drop-down for the Country attribute.
Attributes that are always required are marked with a double red asterisk (**). Attributes that are required because of a rule are not marked. Instead, the user is prompted to enter a value for the required attribute if the user tries to save without entering a value. For example, if a user selects "United States" for the country, the user receives an error if the user tries to save the form without entering a postal code.
*
Editing rules behavior
After you create rules to require attributes that are based on other attributes, the following criteria for editing rules apply.
*
*
If you delete any value from a single-select database attribute, Marketing Operations checks to see whether rules are defined on that value. If a rule is defined on the value and you delete the value, the rule is flagged as invalid. You can then modify the rule.
*
*
*
*
Importing and Exporting behavior
After you create rules to require attributes that are based on other attributes, the following criteria for importing and exporting forms with rules apply.
*
*