The ClientTrack Sync process includes special provisions for user mappings that aims to reconcile differences in user IDs when synchronizing queries and other configuration items that reference users.

As an example, if a user creates a new query in an implementation / training environment and marks the query as Runnable or Editable by only themselves, the ClientTrack Sync process will identify whether the same user exists in the production database based upon the user’s user name.

If the user does exist in the production database, the query will be appropriately associated with that user. If the user does not exist in the production database, the query will be assigned to a generic, system-generated user called “Missing Training User.”

A ClientTrack Sync also syncs checkout histories related to configuration items such as forms, workflows, and dashboards. User reconciliation during ClientTrack Sync applies to users associated with queries, form checkout histories, dashboard checkout histories, workflow checkout histories, and users associated with eligibility rulesets.