JobBuilder - it's not just for scheduling!

Often, Salesforce admins have a series of DemandTools scenarios that need to run in succession. The catalyst to run the jobs doesn’t occur on a regimented schedule. Since the process can’t be scheduled most conclude that JobBuilder won’t be useful when in fact, it will simplify and speed up the process.

Example:

A Salesforce system admin runs 20 DemandTools scenarios (a mix of MassImpact, MassEffect and Find IDs scenarios) in a specific order once the Marketing Department verifies their data processes are complete after each tradeshow.

If the admin runs the scenarios manually they need to:

1. Log in to DemandTools
2. Load the Scenario (and any files being used by the scenario)
3. Click through each step
4. Initiate processing

**Steps 2-4 (above) are done 20 times per show**

If the admin uses JobBuilder they need to:

1. Create the batch, i.e. add all 20 scenarios in the order of preferred execution
   1. **New Users: Scheduling Best Practice is to use a registry file but it is not required**
2. Save the batch; this creates a .djb file for future use
3. Execute the batch in one of two ways (user preference):
   1. Double click the batch’s .djb file 
      OR
   2. Open JobBuilder
      1. Load the batch
      2. Click the Execute Batch Button

The use of JobBuilder, with a one-time setup that is easily initiated (and modified at will), saves significant processing time.

Start using JobBuilder:

• JobBuilder recorded webinar
• JobBuilder Help documents