Configurations Copied During a Sync
Configuration Syncs
For all of the following items, all configuration objects are removed from the Destination environment and replaced with the configurations that are maintained in the Source environment.
Forms including associated Data Elements, Buttons, Help Text, and Rules/Actions.
Workgroups (new and existing) updated in non-production environments will sync associated Workspaces, Menu Groups, Menu Options, Calendar options, Entity configurations, and Form/Workflow assignments. Workgroups are synced based on their name rather than the ID and must use the same name in non-production and production environments.
Dashboards. However, personalized User Dashboards (changes made by individual users) not Sync.
Drop Down Lists including Definitions, Baseline Lists, and List Items.
Workflows including associated Steps, Conditions, and Actions.
Case Note Templates. However, the assignment of a template to specific categories for a specific Organization do not Sync.
Data Explorer Domains including the setup of a Domain, its relationship with other Domains, and the assignment of that Domain to specific Workgroups.
Reports designed in ClientTrack Report Designer, and Report Files create externally with Microsoft Report Builder and uploaded into the Source environment.
Extended ClientTrack Database Objects including:
- Table structures and/or columns prefaced with “CT_” or “CUSTOM_”
- Store procedures prefaced with “C_” or “dnn_” or “aspnet_”
- Database functions prefaced with “C_”
- Database views that start with “CUSTOM_” or “qview_”, with “qview_” only being used for views created from a query (i.e. qview_1000000123)
XML and CSV Import and Export Definitions
Scheduled Asynchronous Task configurations
ClientTrack Portal configurations including the setup of a particular Blog or Forum (blog entries and forum posts are not transferred in a Sync).
Additional System Access options from User Management (Individual User's Permissions that Additional System Access will not Sync).
Due to ClientTrack's server processes, RDL Files may take up to two hours before appearing for Users after a Sync. Users should always stick to "c_" format in their Procedure names and use the following naming conventions:
|