This feature allows scheduling of one or more bulk shares to occur repeatedly over time, run once, sometime in the future, or On Demand. When a Bulk Share has been defined to execute the way you want, you may use this feature to schedule it to run repeatedly to update an external database or your sub-production environments. This is only necessary if you are not using the Dynamic Share feature for real time sharing, but choose to update all records every time the scheduled bulk share runs.
To schedule a bulk share, go to the Replicator > Scheduled Bulk Share option under the Perspectium app.
By selecting the above module, you will be presented with a list of currently defined scheduled bulk shares. If this is your first time, there will not be any existing entries. Go ahead and click the button at the top of the list, you will now be presented with a form to define the scheduled bulk share.
|Name||The name for the scheduled bulk share. Normally you would select something intuitive like “Daily user record sync”.|
|Active||State for the current schedule. When Active is “checked” or “true”, the schedule is in effect and will run based on its configuration.|
|Allow Concurrent Jobs|| Carbon
Having this enabled will allow multiple instances of the same Bulk Share to run at the same time. More details below.
|Run||The schedule for how this group of bulk shares should run. The scheduling controls are similar to any scheduled jobs in ServiceNow, you can reference that documentation here.|
|Time||The time related to “Run” regarding when the job should run.|
|Conditional||When this field is “checked” or “true”, the condition script input box is opened for you to specify a scripted condition of when this job should run. This is a ServiceNow feature and more documentation can be found here.|
|Condition||Specify your conditions for executing this job. This is a ServiceNow feature and more documentation can be found here.|
|Related bulk share records||Once the scheduled bulk share entry is created, you can click the button to select from a list of bulk shares you want to run under this schedule.|
As mentioned above you can set the run period of a job as you would with a standard ServiceNow job. Your options for the run period are:
With varying levels of granularity in each one. You can for example create a Scheduled Bulk Share running periodically every 2 hours, and then create a Bulk Share filtered on “Updated - on - last 2 hours”.
The default implementation is that these individual Bulk Shares are individual jobs where you can have multiple iterations running at the same time. The Bulk Shares should still complete in their entirety, however, the logging of the records processed on the record can look off. Additionally if you have your Bulk Shares set too aggressively for their run period you can have many multiple jobs in your Scheduler.
Starting with the Carbon release of the Update Set you have the option to stop the Scheduled Bulk Share from scheduling a Bulk Share if it has not finished. It will check this per Bulk Share if you have multiple Bulk Shares in the given Schedule.