When building Rules & Alerts in Apricot, not every field type or condition can trigger an alert. This reference helps administrators quickly confirm which fields and comparison conditions are unsupported.
If a field or condition does not appear on this list, it is supported and can be used in your Rules & Alerts configuration.
Tip: Linking fields in Rules & Alerts are treated the same as their base field type. For example, a Dynamic Number field is treated like a Numeric field.
Step 1: Review the list of unsupported fields
Use the table below when designing or troubleshooting rules.
If your field type or condition appears in this list, it is not supported for triggering alerts.
| Field Type(s) | Unsupported Condition(s) |
| Checkbox, Multi-select Dropdown, Dynamic Checkbox | Begins With, Ends With |
| Milestone / Goals | All |
| Append Only | All |
| Scheduler | All |
| Created By, Modified By | All |
| Record ID | All |
| Assigned Program | All |
| User Creation | All |
| Email Trigger | All |
| AFF Fields: Grant, Grant Invitation, Review Assignment | All |
| Record Lock | All |
| All Calculation Fields | All |
Step 2: Understand how linking fields behave
Linking fields follow the behavior of the base field type they represent.
-
Example: A Dynamic Number linking field is treated as a Numeric Field, meaning its compatibility is determined by the base type, not its dynamic nature.
Step 3: Follow best practices for Record Name Fields
Alerts display the value saved into the form’s Record Name Field. When choosing which field to use:
-
Use a clear identifier such as Participant Name for easy reference.
-
Avoid using PII or PHI (personally identifiable or health information) in email alerts.
Instead, choose a more anonymous field, such as a participant ID or case code.
Note: Record Name Field values will appear directly in alerts—ensure this field aligns with your organization’s privacy standards.
What else do you need help with?
Learn more about Rules & Alerts in Apricot:
FAQs and Additional Resources
How do I identify unsupported fields in Rules & Alerts in Apricot? | Why are some fields unsupported in Apricot rules? | How do I find unsupported conditions when building a rule? | Where do I see a list of unsupported fields for rules? | What happens if I use an unsupported field in a rule? | How do I fix unsupported conditions in Apricot rules? | Which field types aren’t supported in Apricot Rules & Alerts?