You can configure custom filters for the batch jobs to filter the records that you want to process. You can configure custom filters for all the batch jobs except the Data Conversion and Data as a Service batch jobs.

To configure custom filters, set the value of the

Custom Filter:<Job name>

to the value that you want to add.

Job name

is the batch job for which you want to filter the records.

You can set one of the following values for the

Job name

parameter based on the batch job for which you want to configure the custom filters:

Consolidation
DuplicateBeanCheck
DuplicateCheck
ExternalCleansing
HierarchyMigration
Matching
MergeAccount
MergeContact
MergeLead
Migrate
MigrateAccount
MigrateContact
MigrateLead

The following sample code filters records that the Matching job processes:

API_SettingsManager.updateInternalSetting('Custom Filter:Matching','DS_Last_Updated__c > 2014-12-314T05:42:14+0000');

If you have batch jobs that run in multiple concurrent processes, you can configure the

Current Set Number

internal setting to populate the Concurrent Set custom field of the Batch Queue object. The value of the Concurrent Set custom field identifies related batch queue records when batch jobs run in multiple concurrent processes.

To populate the Concurrent Set custom field of the Batch Queue object, set the value of the

Current Set Number

internal setting. Default is 0.

The following sample code populates the Concurrent Set custom field:

API_SettingsManager.updateInternalSetting('Current Set Number','10');

If a user does not define priorities or defines incorrect priorities for Run Automatic batch jobs in the performance settings, CC360 assigns default priorities for each batch jobs. You can switch to the default priorities instead of CC360 priorities.

CC360 assigns the following default priorities to the batch jobs:

Batch Job Name	Priority
Matching	1
Duplicate Contact Check	2
Duplicate Check	3
Consolidation	4
Conversion	5

To switch to default priorities, set the value of the

enableDefaultJobPriorityForRunAutomatic

internal setting to true. Default is false which indicates that the jobs run on user-defined priorities.

The following sample code switches to default priorities instead of user-defined priorities:

API_SettingsManager.enableDefaultJobPriorityForRunAutomatic(true);

You can disable the automatic refresh of the Running Jobs table and the Queue Entries table in the batch queue.

To disable automatic refresh, set the value of the

enableQueueMonitorAutomaticRefresh

internal setting to false. Default is true.

The following sample code disables the automatic refresh of the Running Jobs table and the Queue Entries table:

API_SettingsManager.enableQueueMonitorAutomaticRefresh(false);

CC360 does not log batch statistics.

To log batch statistics, set the value of the

Log Batch Statistics

internal setting to true.

The following sample code logs the batch statistics:

API_SettingsManager.updateInternalSetting('Log Batch Statistics','true');

CC360 can synchronously run the matching and the duplicate contact check jobs for a record whenever a user adds a record.

To synchronously run the matching and the duplicate contact check jobs, set the value of the

Synchronous Run Automatic

internal setting to 0. Default is 1.

The following sample code synchronously runs the matching and the duplicate contact check jobs:

API_SettingsManager.updateInternalSetting('Synchronous Run Automatic',0);

CC360 job scheduler reschedules only the successfully completed jobs.

To reschedule the failed jobs, set the value of the

Reschedule Failed Jobs

internal setting to true. Default is false.

The following sample code configures the job scheduler to reschedule the failed jobs:

API_SettingsManager.updateInternalSetting('Reschedule Failed Jobs','true');