Release Notes Summary:
We are updating our release process to align with the Clarity Human Services Release Process. The changes outlined here will be released to looker training instances on 4/3/23 and production and migration instances on 4/17/23. There may be changes to this article until the release date.
General Updates
- Chronically Homeless Fields updated to improve performance.
- Performance Improvements and persistence added to Last Service By Enrollment Field
Client Model
- Added User Creating, User Updating, and Last Updated Date fields in the Coordinated Entry Events view
- Added new “Is Last Event” fields in Coordinated Entry Events View
- Updated "Is Last Assessment By Processor" field
Coordinated Entry Model
- Added User Creating, User Updating, and Last Updated Date fields in the Coordinated Entry Events view
- Added new “Is Last Event” fields in Coordinated Entry Events View
- Updated "Is Last Assessment By Processor" field
Data Quality Model:
- Added new “Is Last Event” fields in Coordinated Entry Events View
HMIS Performance Model:
- The Outbound Recidivism Homeless System Re-entry view now uses only the household move-in date rather than each household member’s individual move-in date.
- Added User Creating, User Updating, and Last Updated Date fields in the Coordinated Entry Events view
- Added new “Is Last Event” fields in Coordinated Entry Events View
- Updated "Is Last Assessment By Processor" field
Outreach Model:
- The Encampment teams view has been created in the outreach model with new fields.
- Added the “Encampment Stay Date Filter” to the Outreach Model.
Services Model:
- Updated "Is Last Assessment By Processor" field
Detailed Notes:
General Updates:
The fields in the “Chronically Homeless” group of the “Entry Screen” View have been updated to improve performance -
- PIT/Current Date -Individual, (chronically_homeless_at_entry.is_chronic_homeless_pit)
- Project Start - Household, (chronically_homeless_households.is_chronic_homeless_household)
- Project Start - Individual, (chronically_homeless_at_entry.is_chronic_homeless)
The following field has been refactored in all models to improve performance.
Services -> "Is Latest service based on enrollment" (client_last_service_by_enrollment.last_service_by_enrollment)
Action Required: None
Client Model:
- Added the following new fields in the Coordinated Entry Events View.
New Fields:
- Coordinated Entry Events -> ”User Creating” (client_events.user_creating)
- Coordinated Entry Events -> ”User Updating” (client_events.user_updating)
- Coordinated Entry Events -> ”Last Updated Time” (client_events.last_updated_time)
- Coordinated Entry Events -> ”Last Updated Date” (client_events.last_updated_date)
- Coordinated Entry Events -> ”Last Updated Week” (client_events.last_updated_week)
- Coordinated Entry Events -> ”Last Updated Month” (client_events.last_updated_month)
- Coordinated Entry Events -> ”Last Updated Quarter” (client_events.last_updated_quarter)
- Coordinated Entry Events -> ”Last Updated Year” (client_events.last_updated_year) - Three new yes/no fields have been added to the Coordinated Entry Events view under the “Is Last Event” group. The Filter Dependent field shows the most recent Coordinated Entry Event, which applies all filters used in the query before calculating the latest event per client. The Reporting Period field shows events linked to an enrollment that is active within the reporting period for the explore. The System Wide field shows all events regardless of filter settings.
New Fields:
- Coordinated Entry Events -> "Is Last Event - Per Client (Filter Dependent)" (client_last_ce_event_filter_dependent_client_model.is_latest_event)
- Coordinated Entry Events -> "Is Last Event - Per Client (Reporting Period)" (client_last_ce_event_by_reporting_period.is_latest_event)
- Coordinated Entry Events -> "Is Last Event - Per Client (System Wide)" (client_last_ce_event_system_wide.is_latest_event) - Refactored the “Last Service by Enrollment” field to improve performance. In the client model, the field "client_last_service_by_enrollment.last_service_by_enrollment" now has the field name "client_last_service_by_enrollment_client_model.is_last_service_by_enrollment".
- Removed the hidden fields "client_last_service_by_enrollment.client_service_id" and "client_last_service_by_enrollment.client_program_id".
- Updated "Is Last Assessment By Processor" (client_last_assessment_by_processor.is_latest_assessment_by_processor) field to eliminate potential errors that can occur when using assessments that have multiple assessment processors assigned.
- Action Required: Any looks using the field "client_last_service_by_enrollment.last_service_by_enrollment" in filters and custom fields will need to be updated. The Technical Support team can help with identifying looks that need to be updated.
Coordinated Entry Model:
Added the following new fields in the Coordinated Entry Events View.
New Fields:
- Coordinated Entry Events -> ”User Creating” (client_events.user_creating)
- Coordinated Entry Events -> ”User Updating” (client_events.user_updating)
- Coordinated Entry Events -> ”Last Updated Time” (client_events.last_updated_time)
- Coordinated Entry Events -> ”Last Updated Date” (client_events.last_updated_date)
- Coordinated Entry Events -> ”Last Updated Week” (client_events.last_updated_week)
- Coordinated Entry Events -> ”Last Updated Month” (client_events.last_updated_month)
- Coordinated Entry Events -> ”Last Updated Quarter” (client_events.last_updated_quarter)
- Coordinated Entry Events -> ”Last Updated Year” (client_events.last_updated_year)
Three new yes/no fields have been added to the Coordinated Entry Events view under the “Is Last Event” group. The Filter Dependent field shows the most recent Coordinated Entry Event, which applies all filters used in the query before calculating the latest event per client. The Reporting Period field shows events linked to an enrollment that is active within the reporting period for the explore. The System Wide field shows all events regardless of filter settings.
New Fields:
- Coordinated Entry Events -> "Is Last Event - Per Client (Filter Dependent)" (client_last_ce_event_filter_dependent_ce_model.is_latest_event)
- Coordinated Entry Events -> "Is Last Event - Per Client (Reporting Period)" (client_last_ce_event_by_reporting_period.is_latest_event)
- Coordinated Entry Events -> "Is Last Event - Per Client (System Wide)" (client_last_ce_event_system_wide.is_latest_event)
Updated "Is Last Assessment By Processor" field to eliminate potential errors that can occur when using assessments that have multiple assessment processors assigned.
Action Required: None
Data Quality Model:
Three new yes/no fields have been added to the Coordinated Entry Events view under the “Is Last Event” group. The Filter Dependent field shows the most recent Coordinated Entry Event, which applies all filters used in the query before calculating the latest event per client. The Reporting Period field shows events linked to an enrollment that is active within the reporting period for the explore. The System Wide field shows all events regardless of filter settings.
New Fields:
- Coordinated Entry Events -> "Is Last Event - Per Client (Filter Dependent)" (client_last_ce_event_filter_dependent_dq_model.is_latest_event)
- Coordinated Entry Events -> "Is Last Event - Per Client (Reporting Period)" (client_last_ce_event_by_reporting_period.is_latest_event)
- Coordinated Entry Events -> "Is Last Event - Per Client (System Wide)" (client_last_ce_event_system_wide.is_latest_event)
Action Required: None
HMIS Performance Model:
The Outbound Recidivism Homeless System Reentry view in the HMIS Performance model has been updated to use only the household move-in date associated with the head of household when calculating homeless system reentry, rather than using the move-in date associated with each individual client's entry screen data.
Added the following new fields in the Coordinated Entry Events View:
- Coordinated Entry Events -> ”User Creating” (client_events.user_creating)
- Coordinated Entry Events -> ”User Updating” (client_events.user_updating)
- Coordinated Entry Events -> ”Last Updated Time” (client_events.last_updated_time)
- Coordinated Entry Events -> ”Last Updated Date” (client_events.last_updated_date)
- Coordinated Entry Events -> ”Last Updated Week” (client_events.last_updated_week)
- Coordinated Entry Events -> ”Last Updated Month” (client_events.last_updated_month)
- Coordinated Entry Events -> ”Last Updated Quarter” (client_events.last_updated_quarter)
- Coordinated Entry Events -> ”Last Updated Year” (client_events.last_updated_year)
Three new yes/no fields have been added to the Coordinated Entry Events view under the “Is Last Event” group. The Filter Dependent field shows the most recent Coordinated Entry Event, which applies all filters used in the query before calculating the latest event per client. The Reporting Period field shows events linked to an enrollment that is active within the reporting period for the explore. The System Wide field shows all events regardless of filter settings.
New Fields:
- Coordinated Entry Events -> "Is Last Event - Per Client (Filter Dependent)" (client_last_ce_event_filter_dependent_hmis_model.is_latest_event)
- Coordinated Entry Events -> "Is Last Event - Per Client (Reporting Period)" (client_last_ce_event_by_reporting_period.is_latest_event)
- Coordinated Entry Events -> "Is Last Event - Per Client (System Wide)" (client_last_ce_event_system_wide.is_latest_event)
Updated "Is Last Assessment By Processor" field to eliminate potential errors that can occur when using assessments that have multiple assessment processors assigned.
Refactored the “Last Service by Enrollment” field to improve performance.
Action Required: None
Outreach Model:
The Encampment teams view has been created in the outreach model with new fields for the team and team members.
New Fields:
- Encampment Teams -> “ID” (outreach_teams.id)
- Encampment Teams -> “Last Updated Time” (outreach_teams.last_updated_time)
- Encampment Teams -> “Last Updated Date” (outreach_teams.last_updated_time)
- Encampment Teams -> “Last Updated Week” (outreach_teams.last_updated_week)
- Encampment Teams -> “Last Updated Month” (outreach_teams.last_updated_month)
- Encampment Teams -> “Last Updated Quarter” (outreach_teams.last_updated_quarter)
- Encampment Teams -> “Last Updated Year” (outreach_teams.last_updated_year)
- Encampment Teams -> “Name” (outreach_teams.name)
- Encampment Teams -> ”User Creating” (outreach_teams.ref_user)
- Encampment Teams -> “User Updating” (outreach_teams.ref_user_updating)
- Encampment Teams -> “Team Members: Team Member Name”
- Encampment Teams ->”Team Members: Team Members Added Time” (outreach_team_users.added_time)
- Encampment Teams ->”Team Members: Team Members Added Date” (outreach_team_users.added_date)
- Encampment Teams ->”Team Members: Team Members Added Week” (outreach_team_users.added_week)
- Encampment Teams ->”Team Members: Team Members Added Month” (outreach_team_users.added_month)
- Encampment Teams ->”Team Members: Team Members Added Quarter” (outreach_team_users.added_quarter)
- Encampment Teams ->”Team Members: Team Members Added Year” (outreach_team_users.added_year)
- Encampment Teams -> “Team Members: Team Member User Adding”
- Encampment Teams -> “Number of Team Members”
- Encampment Teams -> “Number of Teams”
We have added a new date filter to the Outreach Model called 'Encampment Stay Date Filter', and the corresponding date objects, 'Encampment Stay Filter Start Date' and 'Encampment Stay Filter End Date'. This filter pulls client encampment stay records where the 'Client Start Date' is less than the specified 'Encampment Stay Filter End Date' or the current date in the event no filter end date is specified, and the 'Client End Date' is greater than or equal to the 'Encampment Stay Filter Start Date' or the 'Client End Date' is null.
New Fields:
- Encampment Stays -> "Encampment Stay Date Filter" (encampment_occurrences.date_filter)
- Encampment Stays -> ”Encampment Stay Filter Start Date” (encampment_occurrences.encampment_stay_filter_start_date)
- Encampment Stays -> “Encampment Stay Filter End Date” (encampment_occurrences.encampment_stay_filter_end_date)
Action Required: None
Services Model:
Updated "Is Last Assessment By Processor" field to eliminate potential errors that can occur when using assessments that have multiple assessment processors assigned.
Action Required: None
Updated: 3/30/2023