Difference between revisions of "PT Sync Getting Started"

Revision as of 15:40, 21 August 2011

Overview

All implementations of the PT Sync application are unique for all sites.

These steps below will walk through implementing the Sync Test custom element. You can use this custom element to test the installation or customize the steps to utilized your sites custom elements.

Sync Custom Elements

1. Setup the custom element to be identical on both the source and destination sites.
   1. An easy method to maintain this is to export and import the custom element from the source to destination site.
   2. Note: If syncing a local custom element, make sure the custom element is changed to global on the destination site.
   3. Optional: Import the "Sync Test" custom element into the source and destination sites.
2. The custom elemepnt to be synchronized must have a unique ID field (i.e. UUID) and a parent unique ID field. The parent unique ID field maintains the relationship between the parent and child custom element records. When building the sync mapping record, select the fields for the unique ID and the parent unique ID within the custom element.

CCAPI Configuration

1. Each custom element to be synchronized must have be setup through in the CCAPI on the destination site.
2. The following steps for the CCAPI Configuration will setup the CCAPI for the Sync Test custom element.

Sync Mapping

1. Navigate to the Sync Mappings page created on the source site.
2. Create a new sync mapping record to synchronize the custom element records to the destination site.
3. The following are definitions for the fields in the sync mapping:
   1. Source Custom Element - Select from a list of the custom elements within the source site. Select the custom element to synchronize.
      1. Optional: Select the "Sync Test Element" custom element.
   2. Destination Custom Element - This field validates the "Source Custom Element" selected to find the matching custom element on the destination site. The custom elements must have the same names on the both sites.
   3. Unique ID Field - Select the field in the "Source Custom Element" that is the unique ID for the custom element.
      1. Optional: Select the "uuid" custom element.
   4. Parent Unique ID Field - Select the field in the "Source Custom Element" that stores the parent unique ID. This is to maintain the relationship between parent and child records.
      1. Optional: Select the "parentUUID" custom element.
4. Save the Sync Mapping record and reset the ADF.

CommonSpot Hooks

1. CommonSpot version 6.2 and greater contain the "Post Save Form Hook". If you are running CommonSpot version 6.1, then install the HF 8b. This hotfix is in the PT Sync application (/ADF/apps/pt_sync/site_files/commonspot/CS_6.1.0_HF08b.zip).
2. Copy the Post Save Form Hook cfm file (/ADF/apps/pt_sync/site_files/post-save-form-hook.cfm) and paste in the root of the Source site.

Optional Sync Test Element Setup

Optional steps to setup datasheets on the source and destination sites for the Sync Test Element.

1. On the source site, create page "Sync Test Manager" in the /webadmin/sync/ subsite.
2. Add a custom script element to the page.
3. Edit the custom script and define the explicit path as the following:
   1. /ADF/apps/pt_sync/customcf/sync_mapping_test.cfm