Periodic configuration of prospects

When the Enable periodic invocation of batch sync setup option is enabled, a staging mechanism using the NJExchangeProspect table can be used to periodically configure synchronization for a large number of users. An integration component external to synchronization must populate the NJExchangeProspect table, where each prospect record has the NexJ ID of the Exchange server, the NexJ ID of the user's Entity record, and an Activate flag to indicate whether the prospect's synchronization should be activated or deactivated. Deactivation disables the synchronization links of the prospect but does not remove them.

The recurring batch job will process the prospect records and configure synchronization for each user on the specified server. Optionally, it can also initiate a filtered snapshot, known as the initial snapshot. The records for successfully configured users will be removed from the NJExchangeProspect table. Prospect records that could not be processed successfully will be retried on the next execution of the batch job, up to the maximum number of retries specified in the Batch Sync Setup screen. Records that reach the maximum number of processing attempts will be removed from the NJExchangeProspect table. For prospects that are already configured for synchronization, the batch job will attempt to re-enable synchronization if it is currently disabled. No snapshots will be initiated for such prospects.