Connector Scheduler

For each out-of-the-box connector that you activate or for any custom integration you will build, you must define a data exchange schedule. This can be accomplished from the “Scheduled Jobs” setup option.

Create a Scheduler for an Integration Connector

For defining how often the data will be exchanged between your BSS and your back office system, you must do the following:

1. Navigate the BSS → Setup → Administration → System Options → Scheduled Jobs.
2. Select “Add new Record” for creating a new scheduler.
   
3. In the pop-up form define the following info:
   
   1. Name and Description of your scheduler.
   2. Instance. This is a drop-down field that includes all the instances you have activated in your BSS.  You must select for which instance is this scheduler
   3. Settings. In this section, you can define the recurrence of the data exchange process.  You can define if the synchronization of the data will be performed daily, weekly or monthly.
      1. Daily synchronization: You can define the interval from once per day to every minute
      2. Weekly synchronization: You can define which days the synchronization will run.
      3. Monthly synchronization: You can define which months the synchronization will run
         
      4. Advanced Settings. In this section, you can define when this schedule will stop. You can define that it will stop after a number of times or after a specific date. If you reactivate the scheduler at some point in the future, the system will sync all the data from the last date the scheduler ran.
         

Managing the Scheduler

You can edit an existing scheduler for changing its option, or you can delete it if you no longer want it.

Understanding the Scheduler’s Workflow

The Integration Instance Scheduler, also known as “Integration Framework Scheduler” gathers and syncs all the data from your instance in BSS to your back-office system.
Each time the scheduler is programmed to run based on its configuration settings, it will proceed completing the following flow of actions:

• First execution:
  1) The scheduler is initialized.
  2) It gathers all the instance data from the database.
  3) Saves those data to a sync queue.
  4) Syncs those data to your back-office system.
  
• Next execution(s):
  1) The scheduler is initialized.
  2) It gathers all the instance data that were created, updated, or failed after the last sync date.
  3) Saves those data to a sync queue.
  4) Syncs those data to your back-office system.

As a result, your back-office system will always be in sync with all the instance’s data, even the failed ones.