Table of Contents

Search

  1. Preface
  2. Introduction to Informatica Customer 360 for Salesforce
  3. Configuring the Data Cleansing Settings
  4. Managing Batch Jobs
  5. Verifying Addresses, Email Addresses, and Phone Numbers
  6. Synchronizing Salesforce Records with Customer 360 for Salesforce
  7. Managing Duplicate Records
  8. Consolidating Records
  9. Converting External Records to Salesforce Records
  10. Managing Hierarchies
  11. Integrating Customer 360 for Salesforce with Multidomain MDM
  12. Managing Multi-Org
  13. Troubleshooting
  14. Appendix A: Custom Settings
  15. Appendix B: Glossary

Internal Settings for Batch Jobs

Internal Settings for Batch Jobs

You can configure internal settings and change the default behavior of the batch jobs.
You can configure the following internal settings for the batch jobs:
Custom Filter:<Job name>
You can configure custom filters for the batch jobs to filter the records that you want to process. Custom filters allow you to filter the records that you want to process. For example, you can configure a filter to identify records that belong to a particular company.
You can configure custom filters for all batch jobs except the Data Conversion batch job and the Data as a Service batch job.
To configure custom filters, use the
Custom Filter:<Job name>
internal setting and set a value to it.
Use the following format to set a value for the custom filter internal setting:
API_SettingsManager.updateInternalSetting('Custom Filter:<Job name>', '<Filter 1>' [<Operator> '<Filter 2>]');
The following table describes the parameters used in the format of the custom filter internal setting value:
Parameter
Description
Job name
Name of the batch job.
You can set one of the following values 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
Filter 1
Filter criteria to identify the records that you want the batch job to process.
For example,
DS_Last_Updated__c > 2014-12-314T05:42:14+0000
Filter 2
Optional. Additional filter criteria to identify the records that you want the batch job to process.
For example,
DS_company__c='INFA'
.
Operator
Required if you use more than one filter criteria. Logical operators
AND
.
For example,
(DS_Last_Updated__c > 2014-12-314T05:42:14+0000 AND DS_company__c='INFA')
.
The following sample code filters records for the Matching job :
API_SettingsManager.updateInternalSetting('Custom Filter:Matching','DS_company__c='INFA' AND 'DS_Record_Type_Name__c='Sales');
You cannot configure custom filters for the previously scheduled jobs.
Current Set Number
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');
The value is incremented whenever the batch jobs run in multiple concurrent processes.
enableDefaultJobPriorityForRunAutomatic
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);
enableQueueMonitorAutomaticRefresh
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);
Log Batch Statistics
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');
Synchronous Run Automatic
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);
Reschedule Failed Jobs
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');

0 COMMENTS

We’d like to hear from you!