Contact Us

If you still have questions or prefer to get help directly from an agent, please submit a request.
We’ll get back to you as soon as possible.

Please fill out the contact form below and we will reply as soon as possible.

  • Contact Us
  • Log in
  • Home
  • ClientTrack
  • ClientTrack Admin Guide

Configurations That Conditionally Sync

Configuration Syncs

Written by April Lockett

Updated at September 28th, 2023

Contact Us

If you still have questions or prefer to get help directly from an agent, please submit a request.
We’ll get back to you as soon as possible.

Please fill out the contact form below and we will reply as soon as possible.

  • ClientTrack
    ClientTrack Admin Guide HMIS Refugee Resettlement Co-Responder Reports Configuration Guides Design Rights Training Resources
+ More

Three configurations in ClientTrack Sync conditionally depending on the environment they were created in:

1.  The Codes Table

The Codes table (not to be confused with Evaluation Codes) will Sync, including each Codes' OrgGroupID.

If you create a Code in the Source environment marked as "All Organizations", it saves in the OrgGroupID table with the value of "-1" and will Sync as expected.

If Users only have specific Organizations selected to have access to a specific Code, after the Syn, the Code will not retain those Organization Access configurations due to the OrgGroupIDs being associated with different values in different environments.

If a User needs to have a Code be accessed by specific Organizations, create it in the Destination environment only or change the configurations post-Sync. Records in the Codes table that had been created in the Destination environment will not be removed by a Sync.

2.  Eligibility Rule Sets

3.  Queries designed in ClientTrack Query Designer

If the query logic is no longer valid due to changes in your database schema the sync process will communicate a warning to the Engineer conducting the sync. The Engineer will communicate any queries that are no longer valid at the close of the configuration sync. The query will still be visible within ClientTrack but will not query against the database until the query logic has been updated.

A similar process is happening with the tables associated with Query Designer and the Eligibility Rule-Sets. When a User creates a Query in the Production (PROD) environment, those Queries will all start with a 2000000000 number and because it is not in initial Sync ID number range, will be left alone during a Sync.

1000000000 ID Queries made in Training (TRAIN) are not editable in Production (PROD) environments.

 

When a Production (PROD) environment is copied to create/replace a Training (TRAIN) environment, the 2000000000 ID records will be deleted and the environment will be reset to have new records created with a 1000000000 ID. Users with 2000000000 ID Queries that exist only in the Production (PROD) environment only at that point, will need to recreate or export/import the Queries into the newly created Training (TRAIN) environment, if necessary.

condition configs sync conditions

Was this article helpful?

Yes
No
Give feedback about this article

Related Articles

  • Configuration Syncs Overview
  • Tool Access Permissions
  • Merging Duplicate Clients
  • Managing Service Code Groups
ecco_hzt_RGB - amber_white_white, tagline
2150 W. Parkway Blvd, Suite A-101
Salt Lake City, UT 84119
Facebook-f Twitter Linkedin Instagram Youtube
© 2023 All Rights Reserved

Features

  • Reporting & Analytics
  • Case Management
  • Design Tools
  • Custom Workflows

Solutions

  • Homeless Management
  • Victim Services Providers
  • Refugee Resettlement
  • Food and Nutrition
  • Care Coordination
  • Whole Person Care

System

  • System Status and Maintenance

About Us

  • Eccovia's Story
  • Careers
  • Our Leadership

Social

  • Blog
  • Contact Us
  • News
  • Schedule Demo

Subscribe To Our Newsletter


Knowledge Base Software powered by Helpjuice

Expand