Expanding snapshots workflow

After an initial snapshot is executed, the schedule items and tasks during the snapshot window are synchronized for each contact. You can continue to synchronize schedule items and tasks outside the initial snapshot range by using expanding snapshots.

Define expanding snapshot settings on the Batch Sync Setup tab in the Global Exchange Synchronization Options dialog.

The expanding snapshots workflow is as follows.

  1. Configure synchronization for a new prospect.
  2. Submit and execute an initial snapshot based on X Days in Past and Y Days in Future.
  3. Initiate the expanding snapshots workflow which submits a request for:
    • A past snapshot before the initial snapshot window with size = Past Multiplier x X
    • A future snapshot after the initial snapshot window with size = Future Multiplier x Y
  4. Increment Past Iterations and Future Iterations.
  5. Execute the submitted snapshot request during the processing window.
  6. Submit a request for another iteration with:
    • A past snapshot before the previous past snapshot window with size = Past Multiplier x Size of Previous Past Snapshot.
    • A future snapshot after the previous future snapshot window with size = Future Multiplier x Size of Previous Future Snapshot.
  7. Increment Past Iterations and Future Iterations.
  8. Repeat steps 5 to 7 until both Past Iterations and Future Iterations are reached.

For tracking purposes, this feature leverages existing Process Queues functionality. Process queues can be accessed using the Process Queue page in NexJ Admin Console. The queue name for expanding snapshots is ExchangeExpandingSnapshots. The queue can be configured for different concurrency values, priority, and timeout values. The processing window defined previously can also be configured from this page.

When the first iteration of expanding snapshots is executed, it creates a process in the process queue and is visible in the Queue section with either Waiting or Running status. Once the process finishes, it moves to the History section with a Completed status and spawns another process that is responsible for executing the next iteration of expanding snapshots. Each process represents a single iteration and is responsible for up to four snapshots in total: inbound future and past snapshots, as well as outbound future and past snapshots.