SYNC Add-in > Setup > Creating templates and scopes

There are three types of provisioning:

•Template

•Remote

•Local

Template

A template defines tables that will be included in a scope and the filter type that will be applied (i.e. none, division or project). Designing these requires an in-depth knowledge of the database structure and inter-dependencies of objects to avoid potential conflicts.

Sync_Provision_Template_Add

Considerations include:

•How will the system be filtered?

•How many templates will there be?

•Which tables will be included in each template?

•Have we added all the tables required?

•Have we assigned tables to the template with the equivalent filters?

•Have we duplicated the same table in multiple templates?

•Are the tables in the correct order to avoid referential constraint conflicts?

•Are the data types correct?

Designing a template takes the most time, as there are many ways that the synchronization system can be configured depending on the tables and filters that are included.

Templates only need to be defined once and are reused whenever a scope is defined.

Remote

A remote scope is defined by selecting a template and setting the filter values that will be passed to the template.

Sync_ScopeManager_Remote_Provision_Add

Local

A local scope is provisioning by selecting an existing remote scope, with all settings relating to the remote scope created locally.

Sync_ScopeManager_Local_Provision_Add

Note

Initial template, remote scope and local scope provisioning adds tracking tables, triggers, types and stored procedures to each database to maintain a history of changes to any given record in a table.

How To: Provision a template

Select the Template type, and click the Provision button:

Sync_ScopeManager_Template_Provision

Set the template definition:

Sync_Provision_Template

Name must be unique (often the filter type is used).

Description provides additional information about the template .

Filter defines which columns will be used to filter data in the template, associated to the existence of the key column in tables.

Permissions can be set to control the ability to execute scopes:

•User - any user can run the scope.

•Division - only division or system administrators can run the scope.

•System - only system administrators can run the scope.

Mode defines the rules applied when a conflict occurs:

•Safe - the conflict is notified, but nothing happens.

•LocalOverridesServer - data from the local database overrides data in the remote database.

•ServerOverridesLocal - data from the remote database overrides data in the local database.

•Unsafe - the conflict is resolved in a first-in-wins basis determined by the direction.

Direction defines the direction of sync:

•Upload - changes are uploaded from the local database. No changes are downloaded from the remote database to the local database.

•Download - changes are downloaded to the local database. No changes from the local database are uploaded to the remote database.

•UploadAndDownload - changes are uploaded from the local database, then changes are downloaded from the remote database.

•DownloadAndUpload - changes are downloaded from the remote database, then changes are uploaded from the local database.

A tables list can be imported from a text (*.txt) file with each table name on a separate line. Alternatively, tables can be added to the table list (right-hand side) by double clicking on the table name shown in the table tree (left-hand side), or by selecting the table name in the table tree and clicking the button.