JobBuilder - 1.5 Release Notes

DemandTools JobBuilder 1.5 contains identical features and operates exactly as version 1.0 except for one upgrade for the Run DemandTools Command.

The Run DemandTools Command now has the capability to define in which instance of Salesforce the job will execute.

When version 1.5 is installed, users will see a configurable drop-down for Salesforce Instance. This new option, in conjunction with .reg files, will provide the ability to run multiple jobs in multiple organizations in one JobBuilder batch.

Salesforce Instance Drop-down:

• Default Setting: DemandTools as last logged in - this means the job will process in the Salesforce Organization where the last login to DemandTools was made
  • This setting is great for users that do not log in to multiple Salesforce instances via DemandTools

• Using a .reg file with the Salesforce Instance Drop-down:
  • The Salesforce Instance is created in JobBuilder and references the .reg file to know which Salesforce instance to log in to and which DemandTools settings to use.
    • This feature is a must for users:
      • Logging into multiple Salesforce instances
      • Who have changed their DemandTools File Paths but, DemandTools doesn't always retain them because the drives are not always immediately available upon login
      • Who use different settings from the DemandTools General Settings menu, e.g. batch size, in each instance or for specific scenarios
    • A .reg file contains the encrypted credentials used to access DemandTools as well as all settings from the General Settings and File Paths tab
      • Click here to learn more about .reg files and how to create them
    • The Salesforce Instance feature is also easy to configure and use
      • Click here to learn how to use the Salesforce Instance drop-down

You can view the full JobBuilder Training here.