Overview
This release introduces Time-Based Alerts, a powerful new capability that gives teams precise control over when alerts activate and notifications are delivered. In addition, we’ve enhanced referral APIs and resolved key issues affecting automation, data integrity, and cross-site data sharing.
New Feature: Time-Based Alerts
Schedule alerts to activate exactly when they matter.
Time-Based Alerts allow you to set an Effective Date for alerts directly from the Manage Alerts page. Alerts remain inactive until their scheduled date, ensuring notifications are timely, relevant, and aligned to your workflows.
This feature supports planning ahead for program milestones, compliance deadlines, and participant engagement — without generating unnecessary noise for staff.
Key benefits
Future scheduling of alerts
Configure alerts to activate on a specific date. Until that date arrives, alerts remain hidden and inactive.
Email delivery on your schedule
Emails tied to future-dated alerts are automatically sent once the Effective Date is reached — eliminating premature or mistimed notifications.
Enhanced visibility and control
From setup through delivery, alert behavior fully respects your scheduling, enabling more targeted and meaningful engagement with participants and staff.
Additional details
The View Alerts page now respects the Effective Date:
Alerts with a future Effective Date won’t appear until that date arrives.
Alerts with no Effective Date or a past date display as usual.
All existing alert configurations remain supported:
Alerts without an Effective Date behave exactly as they did before.
Clearing an Effective Date returns the alert to immediate activation.
Enhancement
Referral API | New ReferralState Field
Referral API responses now include a plain-text ReferralState field, making it easier to understand referral status at a glance and simplifying integrations.
Possible values include Pending, Accepted, Rejected, and Retracted, matching the ETO UI.
The field is included in referral objects returned by the following endpoints:
GetReferralsByCLID, GetReferralByID, CreateSubjectReferralDetails, UpdateSubjectReferralDetails, RejectReferral, and RetractReferral.
Fixes
Referral API | Auto-Accept 502 Error
We fixed an issue where the CreateSubjectReferralDetails endpoint failed when Auto-Accept Internal Referrals was enabled without a start date. The API now defaults to the current date when a start date is not provided.
Referrals | Missing Participant Demographics
We resolved an issue where participant demographics were not populating correctly on the destination site when referrals were created via API. ReleaseClientInfo now defaults to true when not explicitly included. If your configuration requires this value to be false, it must be specified in the request.