Table of Contents

Search

  1. Preface
  2. Introduction to Informatica Cloud MDM - 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 CC360
  7. Managing Duplicate Records
  8. Consolidating Records
  9. Converting External Records to Salesforce Records
  10. Managing Hierarchies
  11. Integrating Cloud MDM - Customer 360 for Salesforce with Multidomain MDM
  12. Managing Multi-Org
  13. Troubleshooting
  14. Custom Settings
  15. Glossary

Internal Settings for DaaS

Internal Settings for DaaS

If you have DaaS enabled in your organization, you can configure internal settings and change the default behavior of DaaS and the DaaS jobs.
You can configure the following internal settings for DaaS and DaaS jobs:
DaaS Trigger Lookback in mins
When you create a record in the Scout pages and use DaaS to verify address, email address, and phone number, the verification details are stored as a transaction entry in the EventQueue table. Since the record is not yet saved in the database, the verification details are not associated with any Salesforce object.
CC360 uses the user ID and object name to associate Salesforce objects with the verification details in the EventQueue table created within the time period specified in the
DaaS Trigger Lookback in mins
internal setting.
If you save the record after a time frame that is greater than the
DaaS Trigger Lookback in mins
value, the record is saved with a not-verified status. The
DaaS Trigger Lookback in mins
internal setting ensures that the objects get associated with valid and updated verification details.
To specify the time period, set the
DaaS Trigger Lookback in mins
internal settings value in minutes. Default is 30 minutes.
The following sample code specifies the time frame which CC360 uses to associate the verification details with a Salesforce object:
API_SettingsManager.updateInternalSetting('DaaS Trigger Lookback in mins','5');
DisableDaasTrigger
You can disable DaaS for standard Salesforce objects and custom objects.
To disable DaaS, set the value of the
DisableDaasTrigger_<sObjectKeyPrefix>|<sObjectName>
internal setting to 1, where
sObjectName
indicates the name of the Salesforce object and
sObjectKeyPrefix
indicates the key prefix of the object. Default is 0 which indicates that the DaaS is enabled.
The following sample code disables DaaS for an account with key prefix 001:
API_SettingsManager.updateInternalSetting('DisableDaasTrigger_001',1);
The following sample code disables DaaS for accounts:
API_SettingsManager.updateInternalSetting('DisableDaasTrigger_Account',1);
LTNG Auto Verify Address Suggestions
When you verify addresses in Lightning Experience and select a suggested address, DaaS does not verify the selected address again. You can configure to verify a selected address again.
To verify a selected address, set the
LTNG Auto Verify Address Suggestions
internal setting value to
false
.
The following sample code verifies a selected address again:
API_SettingsManager.updateInternalSetting('LTNG Auto Verify Address Suggestions','false');
MaxSchedulesData as a Service
You can create multiple templates for multiple instances of the DaaS job. You can run each job at different schedules on different objects. If you do not have any governor limits in your organization, you can also set the maximum number of schedules that you can configure for the DaaS job. Default is 30 schedules.
To change the default maximum number of schedules that you can configure, configure the
MaxSchedulesData as a Service
internal setting.
The following sample code changes the maximum number of schedules for the DaaS job:
API_SettingsManager.updateInternalSetting('MaxSchedulesData as a Service', 50);
Sfdc Webservice Timeout in Milli Secs
You can configure the Salesforce web service timeout interval for the address, email address, and phone number verification services. Default is 120 seconds.
To change the default time interval, configure the
Sfdc Webservice Timeout in Milli Secs
internal setting.
The following sample code configures the Salesforce web service timeout interval:
API_SettingsManager.updateInternalSetting('Sfdc Webservice Timeout in Milli Secs','10000');

0 COMMENTS

We’d like to hear from you!