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:
- Log in to DemandTools
- Load the Scenario (and any files being used by the scenario)
- Click through each step
- Initiate processing
**Steps 2-4 (above) are done 20 times per show**
If the admin uses JobBuilder they need to:
- Create the batch, i.e. add all 20 scenarios in the order of preferred execution
- **New Users: Scheduling Best Practice is to use a registry file but it is not required**
- Save the batch; this creates a .djb file for future use
- Execute the batch in one of two ways (user preference):
- Double click the batch’s .djb file
OR - Open JobBuilder
- Load the batch
- Click the Execute Batch Button
- Double click the batch’s .djb file
The use of JobBuilder, with a one-time setup that is easily initiated (and modified at will), saves significant processing time.
Start using JobBuilder: