Schedule Seeding in Salesforce Overview

Benefits of the Schedule Seeding Feature

Use of this feature contributes to your work efficiency, because it enables you to:

• Automate the execution of multiple seeding jobs. Use the same template to schedule seedings each to a different destination
• Ensure that necessary destinations are fully seeded with required data, in advance of upcoming sprints and development projects

What the Schedule Seeding Feature Provides

• The Scheduled tab, which is located under the Seeding tab, is where you perform the scheduling of seeding jobs. Additionally, the Scheduled tab displays a listing of all scheduled seeding jobs, both completed and future jobs
• Scheduling of seeding jobs on either a one-time basis, a recurring daily basis, or a recurring weekly basis
• Scheduled, recurring seeding jobs that fail five consecutive times to complete are automatically deactivated
• If either a source service, or a destination service that is being used in a scheduled seeding job becomes unavailable for use, the Scheduled tab alerts you about the service being unavailable for the scheduled seeding job, in the following manner:
  • The warning icon displays to the left of the service's name
  • The service's name appears in orange text
  • The tooltip Service is unavailable displays when you hover over the service's name

  Scheduled seeding jobs having unavailable services do not execute. Should the service(s) return to being available, affected seeding jobs execute as scheduled. Here's what you can do when scheduled seeding jobs have unavailable services:

  • Source service unavailable - navigate to the Template Builder and edit the template by replacing its source service
  • Destination service unavailable - you need to create a new scheduled seeding job that uses a different destination

Scheduled seeding jobs only use the published version of a seeding template (and never a seeding template that is in Edit mode).

The Scheduled Tab

In addition to performing the scheduling of seeding jobs in the Scheduled tab, the tab displays a table that lists all scheduled seeding jobs, both completed and future jobs. Completed scheduled seeding jobs - meaning, seeding jobs whose final, scheduled execution has occurred and their defined end date may or may not have been reached - appear grayed-out. Per table entry, the following information is provided:

• Provider: the data provider that the scheduled seeding job is defined to process, meaning either Salesforce, or ServiceNow
• Id: a numeric identifier assigned to the scheduled seeding job. By default, table entries are sorted by Id from newest (at top) to oldest (at bottom)
• Type: an icon that identifies the template's type, either the Nodes template icon or the Levels template icon
• Template: name of the (published) seeding template for use by the scheduled seeding job (or, as used by the completed, scheduled seeding job). Click the name to display, in a new browser tab, this template in the Template Builder
• Source:
  • Name of the service being used as the seeding source for the scheduled seeding job (or, as used by the completed, scheduled seeding job). When the seeding job generates synthetic data as part of the seeding job, the line entry displays Generate synthetic data.
  • ID of the service being used as the seeding source for the scheduled seeding job (or, as used by the completed, scheduled seeding job). When the seeding job generates synthetic data as part of the seeding job, the line entry is empty.
• Backup:
  • If the Live service data was selected for the scheduled seeding job, then the Backup column entry displays two dash characters (--) indicating that column info is not applicable
  • If the Latest Backup of service data was selected for the scheduled seeding job, then the Backup column entry displays only the word Latest
  • If a recent backup of service data [by <date> <time>] was selected for the scheduled seeding job, then the Backup column entry displays following information:
    • <date><time> of the backup
    • ID of the backup
• Destination: name of the Destination service for use by the scheduled seeding job (or, as used by the completed scheduled seeding job)
• Start Date: the seeding job’s scheduled start date and start time and scheduled recurrence (if applicable)
• End Date: either the recurring seeding job’s scheduled end date and end time or two dash characters (--) to indicate that column info is not applicable
• Next Run: the recurring seeding job’s upcoming, scheduled execution date or two dash characters (--) to indicate that column info is not applicable

All times provided in the table appear in your (the viewer's) local time.