Skip to main content
All CollectionsWhat's NewRelease Notes2022 Release Notes
Release Notes | Condition Logic Enhancements & Email Alerts
Release Notes | Condition Logic Enhancements & Email Alerts

Released 10/13/2022

Updated over a year ago

Release Summary

Rules & Alerts is an intelligent notification system that enables social good organizations to advance the way care is delivered.

Users can configure business logic to generate notifications when key events occur so that caseworkers can focus on the most critical tasks and use data to fight participant disengagement.

In this release users will enjoy an enhanced user experience and email delivery of alerts. Additionally, organizations on 360 can now build rules with multiform conditions.

Release Benefits

  • Cleaner and more advanced rule creation experience

  • Foundations set for complex logic

  • Delivery of time sensitive alerts to email inboxes

Timeline

  • Release is evening of October 12, 2022

  • Available to client morning of October 13, 2022

Considerations

  • Multiform conditions (“secondary form” in the UI) is 360 only

  • Multiform conditions are limited to the Doc Folder

  • Secondary form cannot be T1s, only other T2s in the Doc Folder – in progress

  • 10 conditions max on a rule, including secondary form conditions

  • Form rules only check the last created record of the secondary form

Release Notes

Please review below documentation to review and/or understand additions to Rules & Alerts.

Trigger Creation Improvements

Nested Form Selector

Graphical user interface, text, application, email

Description automatically generated

The delineation of Tier 1 and Tier 2 forms is now much clearer. Forms in any form selector dropdown now appear nested.

Also note the form selector has moved from Rule Details to Trigger. This makes it easier for users to reference the primary form when using multiform conditions.

Date Picker

Note: True time-based alerts are coming Q1 2023.

Using dates on record-based alerts here won’t yet be able to reason about this date. Any alerts created on dates require a record creation or update.

Graphical user interface, text, application

Description automatically generated

Numeric Validation

Conditions built on numerics, like scores or income, now have validation. No letters or special characters can be entered. This safeguards rule creation.

Users will not be able to type in letters or non-numeric characters when setting the condition.

State dropdown

If using State field type, U.S. state options now appear in the dropdown for selection.

Graphical user interface, text

Description automatically generated

Multiform Conditions

Organizations on Apricot 360 can now create rules combining conditions across two forms. This paves the way for more complex alerting. It is also a benefit to using Rules & Alerts vs. an email trigger.

  • Note: Secondary forms are only available within the Doc Folder. At this time conditions cannot be set on linked Doc Folders. Ex. Cannot use family T1 fields when rule is built on participant T1.

  • Note: Tier 1 forms are not available as secondary forms. Ex. Hogwarts Animal Enrolled AND Student is Gryffindor.

  • Note: Multiform conditions refer only to the last created record of the secondary form. At this time the rule cannot check first created, last modified or multiple records. Additionally, the rule cannot check against a record that does not exist. An empty condition meant to check if a record has or has not been created will not work.

Graphical user interface, text, application, email

Description automatically generated

To add multiform conditions, select Secondary Form.

Graphical user interface, text, application, email

Description automatically generated

Next, select the form you would like the rule to check.

Graphical user interface, text, application

Description automatically generated

Users can add multiple field conditions, just like on the primary form.

  • Note: An empty condition on the secondary form WILL NOT check that record’s existence. There must be a saved record for the alert to fire.

  • Note: All conditions in Secondary Form are connected by AND statements (not IF or OR).

Graphical user interface, text, application, email

Description automatically generated

Email Alerts

In response to feedback, we are happy that alerts can now delivered via email to the username address.

Alerts can be in-product only (seen in the notifications dropdown), email only or both.

Graphical user interface, text, application, email

Description automatically generated

Emails will appear as below.

Graphical user interface, text, application, chat or text message

Description automatically generated

Note: Alerts will be populated with the value saved into the field designated as the form's Record Name Field. In many cases, it is a good idea to use something like Participant Name for the Record Name; However, if using email alerts you should avoid using PII or PHI, and should choose a more anonymous field for the form's Record Name

Did this answer your question?