1.2 Manage RDN API Configuration (Lead and Contact)

Trigger Example:

Add to objects like Lead, Contact, etc.

trigger LeadTrigger on Lead (after insert, after update) {

    if (Trigger.isAfter) {

        RDNTriggerHandler.handleTrigger(Trigger.new, Trigger.oldMap);

    }

}

trigger ContactTrigger on Contact (after insert, after update) {

    if (Trigger.isAfter) {

        RDNTriggerHandler.handleTrigger(Trigger.new, Trigger.oldMap);

    }

}

Please note that user has to write below lines in trigger.

    if (Trigger.isAfter) {

        RDNTriggerHandler.handleTrigger(Trigger.new, Trigger.oldMap);

    }

The old map and the new list are compared to identify any changes in the fields. An HTTP call will be triggered only if a change is detected.

Step 4 – Allow Remote Site Access

To use the solution in the SFDC instance, the user has to provide access to remote sites.

Steps to Add a Remote Site in Salesforce

• Log in to Salesforce:

Go to https://login.salesforce.com (or your org’s login page) and log in with your credentials.

1. Navigate to Setup:

Click the gear icon (⚙️) at the top right.

1. 1. Select Setup.
   2. Search for “Remote Site Settings”:
   3. In the Quick Find box on the left sidebar, type Remote Site Settings.
   4. Click on Remote Site Settings under the Security section.
   5. Create a New Remote Site:
      Click the “New Remote Site” button.

• Fill Out the Remote Site Details:

Remote Site Name: Give it a unique name (no spaces, e.g., My_API_Site).

Remote Site URL: Enter the base URL of the external service (e.g., https://api.example.com).

1. 1. Do not include trailing slashes or paths like /v1/endpoint. Just the base domain.
   2. Description (optional): Add a meaningful description.
   3. Disable Protocol Security: Leave unchecked unless you’re working with an old HTTP endpoint (not recommended).
   4. Active: Keep this checkbox checked to allow callouts to this URL.

• Save the Remote Site:

Click Save.

5. Error Handling

When an error is encountered,  an alert email is sent to the RightWave (RW) team and the RDN Support team through the RDN API. Notifications are triggered under the following conditions:

• API is inactive
• Processing Unit (PU) limits are exceeded
• Invalid or expired authentication token
• Incorrect or missing metadata configuration
• Unexpected failure in the process execution

6. Validation & Testing

• Test Data: Create sample Leads with Job Title, Country, Email.
• Expected Results: Job Title categorized → Job Role & Management Level fields populated.
• Verify: Check Salesforce record after API run.

7. Troubleshooting

Common Issues:

• Invalid Token: Verify Auth_Token__c in metadata.
• Inactive Service: Check Is_Active__c flag in configuration.
• API Limit Exceeded: Retry after reset window.
• Wrong Mappings: Ensure SFDC fields match API payload keys.

Logs & Debugging:

• Check RDN logs.
• Use Salesforce Debug Logs (set Apex logging level = FINE).

Rollback Steps:

• Deactivate CMDT records.
• Remove triggers temporarily.

8. Security & Compliance

• Authentication: Secure Auth Token.
• Data Access: Only mapped fields are shared with RDN APIs.
• PII Handling: Sensitive fields (Email, Phone, Name) only processed via secure HTTPS.

9. Limits & Performance 

Salesforce Governor Limits:

• Max 100 callouts per transaction
• Queueable job chaining for >98 records
• Batch Size: Default 98, configurable in metadata.
• Retry Behavior: Failed jobs retried based on the SFDC retry mechanism

10. Support & Escalation

• Level 1: Salesforce Admins check logs & metadata.
• Level 2: RDN Team (RightWave Inc.)

Escalation Contact: RightWave Team