Have you ever completed a TouchPoint outside of your Workflow and wished the step could just be marked as complete? Now you can with Workflow Cross-Check!
Overview
This release includes the first release for Workflow Cross-Check, specific to TouchPoints, and high-priority defect fixes for ETO HMIS, Collections, and Manage Programs.
Introducing Workflow Cross-Check
Users can now refresh Workflows directly from the Participant Dashboard. With just one click of a Refresh button, the system will scan for completed Workflow steps that include TouchPoints across the current site. When required Workflow prerequisites are completed, any TouchPoint finished outside the Workflow for that Participant will be automatically detected, updated, and marked as Done—ensuring all required information is captured seamlessly.
Important: When a step is required prior to a step with a TouchPoint, that step must be completed in advance of the Refresh button working.
To read more about Workflow Cross-Check, click here.
We expect to expand these capabilities to other Workflow requirements and add Site Manager controls. Stay tuned for upcoming releases!
Fixes:
ETO-168 | ETO HMIS: Fix for HUD Assessment Conditional Logic for Pages
Previously, when some users selected "Self" as Head of Household for a Participant under 18 in a HUD Assessment, Page #2 "Living Situation" and Page #5 "Income and Benefits" appeared but none of the questions populated into the pages. Now, after selecting a Participant under 18 as Head of Household, all pages and questions populate as expected.
ETO-289 | Manage Programs: Reason for Dismissal does not Populate Fix
Some users have saved an auto-dismiss Reason for Dismissal that is scoped to only be available in a single program on the Manage Programs page. Previously, when attempting to edit that program while located in a different program, the auto-dismiss Reason for Dismissal appeared blank. Now, when an auto-dismiss Reason for Dismissal of any scope is saved in Manage Programs, it will populate with the previously saved value no matter which program you're in.
ETO-300 | ETO HMIS: Fix for Sexual Orientation data element on incorrect page of HUD Assessment
Previously, the "Sexual Orientation" element (R3) and the "R3.1-A_SexualOrientationOther" element were both on Page 3 of the HUD Assessment, which only appears if the Project is RHY or SSVF funding-related. Now, both elements appear on Page #1 of the HUD Assessment.
ETO-359 | Fix for Save and Record Similar TouchPoint Produces Robot Error for Collections
Previously, when saving a Collection TouchPoint response after selecting Save and Record Similar, some users experienced a robot error for Multi-Participant TouchPoints. Now, saving for Collections will work as expected with no robot error.