Skip to main content
Release Notes | June 28 | ETO 20.74.0

This release includes high-priority defect fixes and new functionality within the ETO API. Available 6/28/24.

Updated over 5 months ago

Feature Updates:

We are excited to announce that ETO APIs can now better support Internal Referrals data, providing new functionality and greater flexibility.

(Note: The ETO API updates have not been rolled out to Australian customers at this time.)

What is the ETO API?

The ETO API is a powerful extension point within the ETO application, allowing users to create custom software integrations via API. It facilitates data retrieval, data submission, and data modification within ETO at a more granular level in comparison with Batch Uploads or Reporting. If you would like to add API capabilities to your enterprise, please contact your Account Manager.

New Functionality: Expansion of Referrals API Calls

The latest update introduces endpoints for accessing Internal Referral data previously unavailable through the ETO API. Users can now programmatically submit, retrieve, and manipulate referral form data, enhancing flexibility akin to TouchPoint data management in the ETO API.

Now you can:

  • Create, update, and delete individual Internal Referrals by Referral ID

  • Create, update, and delete referral form responses by Response ID

  • Retrieve individual referrals and referral form responses by Referral ID and Response ID

    • Extending beyond the legacy referral functionality to Internal Referrals

    • Including Family Referrals

  • Retrieve multiple-participant referrals and referral form responses by Participant ID (CLID)

    • Including across programs/sites

    • Including Family Referrals

  • Retrieve the following available data:

    • Referral Date

    • Referral form Response Identifiers

    • Source and Destination Program Identifiers

    • Current Referral Status

    • Services Provided

    • Entity Identifier

    • Release Client Info flag

    • Household Unique Identifier

Fixes:

ETO-346 | Feature Update: Site Filter for Response Cross Reference Now Available

We’ve expanded the available options for the Response Cross Reference Element. Now, users can add a filter by Site. To learn how to apply this functionality, please visit the help article here.

ETO-272 | Dismiss Participant: Fix for Searching by Family Only Returning Members with Exact Name

Previously, when a user selected the Family Name filter on the Dismiss Participants page, only exact matches for that family name would appear based on the search term, excluding any family members with different last names. Now, the search results in Dismiss Participant will show all members for a selected Family, even if their last name is different.

ETO-330 | Caseloads: Fix For Assignment Email Inconsistencies

Previously, Caseload Assignment confirmation emails only appeared for the first participant selected. Now, when a Caseload is assigned, there will be an email confirmation for each participant.

ETO-185 | TouchPoints: Fix for Address Element Not Allowing New Canadian Postal Code

Previously, the Address TouchPoint Element displayed an “Invalid Post Code" message when the new Canadian Postal Code "T5C 0N8" was entered. Now, "T5C 0N8" is accepted in the Address Element as a valid postal code.


Did this answer your question?