{"id":90199,"date":"2026-01-14T19:19:24","date_gmt":"2026-01-15T03:19:24","guid":{"rendered":"https:\/\/rightwave.com\/rwi\/?page_id=90199"},"modified":"2026-01-14T19:58:10","modified_gmt":"2026-01-15T03:58:10","slug":"rdn-sfdc-integration","status":"publish","type":"page","link":"https:\/\/rightwave.com\/rwi\/rdn-help\/rdn-sfdc-integration","title":{"rendered":"RDN-SFDC Integration"},"content":{"rendered":"\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t\t\t\t
<\/div>\n\t\t\t\t\t\t\t
\n\t\t\t\t\t
\n\t\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t\t
\n\t\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t\t

RDN-SFDC Integration<\/p>\t\t\t\t<\/div>\n\t\t\t\t

\n\t\t\t\t\t

This guide provides step-by-step instructions for integrating Salesforce (SFDC) with the RDN platform using a metadata-driven, asynchronous integration package.<\/p>\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/section>\n\t\t\t\t\t<\/div>\n\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/section>\n\t\t\t\t

\n\t\t\t\t\t\t
\n\t\t\t\t\t
\n\t\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

1. Purpose<\/b><\/h4>

This guide provides step-by-step instructions for integrating Salesforce (SFDC) with the RDN platform using a metadata-driven, asynchronous integration package.<\/span><\/p>

It covers:<\/b><\/h4>
  • Installation & configuration steps<\/span><\/li>
  • Metadata setup and field mappings<\/span><\/li>
  • Operational workflows and troubleshooting<\/span><\/li>
  • Security, compliance, and performance considerations<\/span><\/li><\/ul>

    Audience:<\/b><\/h4>
    • Salesforce Administrators<\/span><\/li>
    • RDN Integration team<\/span><\/li>
    • Developers supporting Salesforce customizations<\/span><\/li><\/ul>

      2. Prerequisites<\/b><\/h4>

      Before starting the integration, ensure the following:<\/span><\/p>

      • Salesforce Access: System Administrator profile.<\/span><\/li>
      • Environment: Salesforce Sandbox for testing, Production for rollout.<\/span><\/li>
      • Required Package: RDN Managed Package (install link provided).<\/span><\/li>
      • API Credentials: Valid RDN Auth Token.<\/span><\/li>
      • Remote Site Settings: Must allow the RDN API base URL.<\/span><\/li>
      • Version Compatibility: Salesforce Lightning Experience recommended.<\/span><\/li>
      • Connected App: Ensure API Enabled.<\/span><\/li><\/ul>

        3. Architecture & Data Flow<\/b><\/h4>

        Architecture Components:<\/b><\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t

        \n\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t\"\"\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t
        \n\t\t\t\t\t\t\t\t\t

        Data Flow:<\/b><\/h4>
        1. User inserts\/updates a Lead\/Contact.<\/span><\/li>
        2. Trigger fires and enqueues a Queueable Job.<\/span><\/li>
        3. Job dynamically builds payload from metadata.<\/span><\/li>
        4. RDN APIs are called (Basic Utility, Categorization, Lookup, etc.).<\/span><\/li>
        5. Response mapped back to Salesforce fields.<\/span><\/li>
        6. Records updated asynchronously.<\/span><\/li><\/ol>

          4.\u00a0 Installation & Configuration<\/b><\/h4>

          Step<\/b> 1 \u2013 Install Package<\/b><\/h4>

          Navigate to the unmanaged package link:<\/span><\/p>

          \u00a0\/packaging\/installPackage.apexp?p0=xxxxxxxxxxxxxx<\/b><\/p>

          Installed Packaged Details<\/b><\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t

          \n\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t\"\"\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t
          \n\t\t\t\t\t\t\t\t\t

          MetaData Components included in package:<\/b><\/h4>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t
          \n\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t\"\"\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t
          \n\t\t\t\t\t\t\t
          \n\t\t\t
          <\/div>\n\t\t<\/div>\n\t\t\t\t\t\t<\/div>\n\t\t\t\t
          \n\t\t\t\t\t\t\t\t\t

          Post-installation Components:<\/b><\/h4>
          • Custom Metadata Types (CMDTs)<\/span><\/li>
          • Apex Classes (RDNTriggerHandler, RDNAPIUtils, Queueable Jobs)<\/span><\/li>
          • Example Triggers<\/span><\/li><\/ul>

            Step 2 \u2013 Metadata Configuration<\/b><\/h4>

            The integration is completely configurable through CMDTs.<\/span><\/p>

            Create and configure\u00a0 the following Custom Meta DataTypes:<\/b><\/p>

            1 RDN API Configuration<\/span><\/p>

            2 RDN API Input Field<\/span><\/p>

            3 RDN API Provider<\/span><\/p>

            4 RDN Field Update<\/span><\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t

            \n\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t\"\"\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t
            \n\t\t\t\t\t\t\t\t\t

            1.1 RDN API Configuration<\/b>
            <\/b>Purpose<\/b>: <\/span><\/h4>

            Defines which Salesforce object to monitor and how.<\/span><\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t

            \n\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t\"\"\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t
            \n\t\t\t\t\t\t\t\t\t

            1.2 Manage RDN API Configuration (Lead and Contact)<\/b><\/h4>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t
            \n\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t\"\"\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t
            \n\t\t\t\t\t\t\t\t\t

            1.3 Edit Label (Lead) <\/b><\/h4>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t
            \n\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t\"\"\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t
            \n\t\t\t\t\t\t\t\t\t

            1.4 Edit Label (Contact)<\/b><\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t

            \n\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t\"\"\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t
            \n\t\t\t\t\t\t\t\t\t
            Field Name<\/b><\/td>Description<\/b><\/td>Type<\/b><\/td><\/tr>
            Service name<\/span><\/td>Name of the RDN service<\/span><\/td>text<\/span><\/td><\/tr>
            API Type<\/span><\/td>Picklist: Basic, Categorization, Lookup, Custom<\/span><\/td>Dropdown<\/span><\/td><\/tr>
            Endpoint Path<\/span><\/td>instead of a full URL, like \/addScore<\/span><\/td>Text<\/span><\/td><\/tr>
            SFDC_Object_Name<\/span><\/td>Object Name<\/span><\/td>Text<\/span><\/td><\/tr>
            Is Active?<\/span><\/td>Is the service active<\/span><\/td>Checkbox<\/span><\/td><\/tr>
            RDN API Provider<\/span><\/td>Reference of RDN_API_Provider__mdt\u00a0<\/span><\/td>Lookup<\/span><\/td><\/tr>
            Run_in_Batch__c<\/b><\/td>RUN this configuration when c<\/b>alled from manual execution.RDNAPIUtils.runCallBatch(‘lead’,query);<\/b><\/td>Checkbox<\/b><\/td><\/tr><\/tbody><\/table>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t
            \n\t\t\t\t\t\t\t\t\t

            2.1 RDN API Input Field<\/b><\/h4>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t
            \n\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t\"\"\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t
            \n\t\t\t\t\t\t\t\t\t

            2.2 Manage API Input Field<\/b><\/h4>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t
            \n\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t\"\"\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t
            \n\t\t\t\t\t\t\t\t\t

            2.3 Edit Service 1 (Lead) (Not Applicable for memoryBlue)<\/b><\/h4>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t
            \n\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t\"\"\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t
            \n\t\t\t\t\t\t\t\t\t
            Field Name<\/b><\/td>Description<\/b><\/td><\/tr>
            API Config<\/span><\/td>Id of RDN_API_Configuration__mdt<\/span><\/td><\/tr>
            SF_Field_Name<\/span><\/td>API name of the Salesforce field<\/span><\/td><\/tr>
            Request_Key__c\u00a0<\/span><\/td>Key in JSON payload<\/span><\/td><\/tr><\/tbody><\/table>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t
            \n\t\t\t\t\t\t\t\t\t

            2.4\u00a0 Edit Service 2 (Contact)<\/b><\/h4>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t
            \n\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t\"\"\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t
            \n\t\t\t\t\t\t\t\t\t

            2.5\u00a0 RDN API Provider<\/b><\/h4>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t
            \n\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t\"\"\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t
            \n\t\t\t\t\t\t\t\t\t
            Field Name<\/b><\/td>Description<\/b><\/td><\/tr>
            Base URL<\/span><\/td>Domain<\/span><\/td><\/tr>
            Auth Token<\/span><\/td>Auth Token which has to be included in header<\/span><\/td><\/tr>
            Get notified<\/span><\/td>Use for send email in case of exception.<\/span><\/td><\/tr>
            Is Active<\/span><\/td>Flag to turn off RDN<\/span><\/td><\/tr><\/tbody><\/table>

            2.5\u00a0 Manage API Provider<\/b><\/h4>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t
            \n\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t\"\"\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t
            \n\t\t\t\t\t\t\t\t\t

            2.6 Edit<\/b><\/h4>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t
            \n\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t\"\"\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t
            \n\t\t\t\t\t\t\t\t\t

            2.7\u00a0 API Field Update<\/b><\/h4>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t
            \n\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t\"\"\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t
            \n\t\t\t\t\t\t\t\t\t
            Field Name<\/b><\/td>Description<\/b><\/td><\/tr>
            API_Config__c\u00a0<\/span><\/td>Id of RDN_API_Configuration__mdt<\/span><\/td><\/tr>
            SF_Field_Name__c\u00a0<\/span><\/td>API name of the Salesforce field<\/span><\/td><\/tr>
            Request_Key__c\u00a0<\/span><\/td>Key in JSON payload<\/span><\/del><\/td><\/tr><\/tbody><\/table>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t
            \n\t\t\t\t\t\t\t\t\t

            3.\u00a0 Manage RDN API Field Update<\/b><\/h4>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t
            \n\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t\"\"\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t
            \n\t\t\t\t\t\t\t\t\t

            3.\u00a0 Manage RDN API Field Update<\/b><\/h4>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t
            \n\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t\"\"\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t
            \n\t\t\t\t\t\t\t\t\t

            3.2\u00a0 Management Level Lead <\/b><\/h4>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t
            \n\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t\"\"\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t
            \n\t\t\t\t\t\t\t\t\t

            3.3 Job Role Contact<\/b><\/h4>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t
            \n\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t\"\"\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t
            \n\t\t\t\t\t\t\t\t\t

            3.4 Job Role Lead<\/b><\/h4>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t
            \n\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t\"\"\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t
            \n\t\t\t\t\t\t\t\t\t

            Step 3 \u2013 Update Salesforce Triggers<\/b><\/h4>

            Trigger Flow:<\/b><\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t

            \n\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t\"\"\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t
            \n\t\t\t\t\t\t\t\t\t

            Trigger Example:<\/b>
            <\/b><\/h4>

            Add to objects like Lead, Contact, etc.<\/span><\/p>

            trigger LeadTrigger on Lead (after insert, after update) {<\/span><\/p>

            \u00a0\u00a0\u00a0\u00a0if (Trigger.isAfter) {<\/span><\/p>

            \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0RDNTriggerHandler.handleTrigger(Trigger.new, Trigger.oldMap);<\/span><\/p>

            \u00a0\u00a0\u00a0\u00a0}<\/span><\/p>

            }<\/span><\/p>

            trigger ContactTrigger on Contact (after insert, after update) {<\/span><\/p>

            \u00a0\u00a0\u00a0\u00a0if (Trigger.isAfter) {<\/span><\/p>

            \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0RDNTriggerHandler.handleTrigger(Trigger.new, Trigger.oldMap);<\/span><\/p>

            \u00a0\u00a0\u00a0\u00a0}<\/span><\/p>

            }<\/span><\/p>

            Please note that user has to write below lines in trigger.<\/span><\/p>

            \u00a0\u00a0\u00a0\u00a0if (Trigger.isAfter) {<\/span><\/p>

            \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0RDNTriggerHandler.handleTrigger(Trigger.new, Trigger.oldMap);<\/span><\/p>

            \u00a0\u00a0\u00a0\u00a0}<\/span><\/p>

            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.<\/span><\/p>

            Step 4 \u2013 Allow Remote Site Access<\/b><\/h4>

            To use the solution in the SFDC instance, the user has to provide access to remote sites.<\/span><\/p>

            Steps to Add a Remote Site in Salesforce<\/b><\/b><\/h4>
            • Log in to Salesforce:<\/b><\/li><\/ul>

              Go to https:\/\/login.salesforce.com (or your org\u2019s login page) and log in with your credentials.<\/span><\/p>

              1. Navigate to Setup<\/b>:<\/span><\/li><\/ol>

                Click the gear icon (\u2699\ufe0f) at the top right.<\/span><\/p>

                  1. Select Setup.<\/span><\/li>
                  2. Search for “Remote Site Settings”:<\/span><\/li>
                  3. In the Quick Find box on the left sidebar, type Remote Site Settings.<\/span><\/li>
                  4. Click on Remote Site Settings under the Security section.<\/span><\/li>
                  5. Create a New Remote Site:<\/b>
                    <\/b>Click the “New Remote Site” button.<\/span><\/li><\/ol><\/li><\/ol>
                    • Fill Out the Remote Site Details:<\/b><\/li><\/ul>

                      Remote Site Name: Give it a unique name (no spaces, e.g., My_API_Site).<\/span><\/p>

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

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

                            Click Save.<\/span><\/p>

                            5. Error Handling<\/b><\/h4>

                            When an error is encountered,\u00a0 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:<\/span><\/p>

                            • API is inactive<\/span><\/li>
                            • Processing Unit (PU) limits are exceeded<\/span><\/li>
                            • Invalid or expired authentication token<\/span><\/li>
                            • Incorrect or missing metadata configuration<\/span><\/li>
                            • Unexpected failure in the process execution<\/span><\/li><\/ul>

                              Error code\u00a0<\/b><\/p><\/td>

                              Explanation<\/b><\/p><\/td>

                              Flow Terminated<\/b><\/p><\/td><\/tr>

                              Q001, QB01, DB01<\/span><\/p><\/td>

                              unhandled processing exception<\/span><\/p><\/td>

                              YES<\/span><\/p><\/td><\/tr>

                              Q002, QB02, DB02<\/span><\/p><\/td>

                              API endpoint not found (404)<\/span><\/p><\/td>

                              NO<\/span><\/p><\/td><\/tr>

                              Q003, QB03, DB03<\/span><\/p><\/td>

                              API error with specific HTTP status<\/span><\/p><\/td>

                              NO<\/span><\/p><\/td><\/tr>

                              Q004, QB04, DB04<\/span><\/p><\/td>

                              RDN response indicates failure<\/span><\/p><\/td>

                              NO<\/span><\/p><\/td><\/tr>

                              Q006, QB06, DB06<\/span><\/p><\/td>

                              Invalid input field error<\/span><\/p><\/td>

                              NO<\/span><\/p><\/td><\/tr>

                              Q007, QB07, DB07<\/span><\/p><\/td>

                              Inner exception during processing<\/span><\/p><\/td>

                              NO<\/span><\/p><\/td><\/tr>

                              Q008, QB08, DB08<\/span><\/p><\/td>

                              Retry record save error<\/span><\/p><\/td>

                              NO<\/span><\/p><\/td><\/tr>

                              Txx0<\/span><\/p><\/td>

                              Input field error in trigger when try to detect change.<\/span><\/p><\/td>

                              NO<\/span><\/p><\/td><\/tr><\/tbody><\/table>

                              6. Validation & Testing<\/b><\/h4>
                              • Test Data: Create sample Leads with Job Title, Country, Email.<\/span><\/li>
                              • Expected Results: Job Title categorized \u2192 Job Role & Management Level fields populated.<\/span><\/li>
                              • Verify: Check Salesforce record after API run.<\/span><\/li><\/ul>

                                7. Troubleshooting<\/b><\/h4>

                                Common Issues:<\/b><\/h4>
                                • Invalid Token: Verify Auth_Token__c in metadata.<\/span><\/li>
                                • Inactive Service: Check Is_Active__c flag in configuration.<\/span><\/li>
                                • API Limit Exceeded: Retry after reset window.<\/span><\/li>
                                • Wrong Mappings: Ensure SFDC fields match API payload keys.<\/span><\/li><\/ul>

                                  Logs & Debugging:<\/b><\/h4>
                                  • Check RDN logs.<\/span><\/li>
                                  • Use Salesforce Debug Logs (set Apex logging level = FINE).<\/span><\/li><\/ul>

                                    Rollback Steps:<\/b>
                                    <\/b><\/h4>
                                    • Deactivate CMDT records.<\/span><\/li>
                                    • Remove triggers temporarily.<\/span><\/li><\/ul>

                                      8. Security & Compliance<\/b><\/h3>
                                      • Authentication:<\/b> Secure Auth Token.<\/span><\/li>
                                      • Data Access:<\/b> Only mapped fields are shared with RDN APIs.<\/span><\/li>
                                      • PII Handling:<\/b> Sensitive fields (Email, Phone, Name) only processed via secure HTTPS.<\/span><\/li><\/ul>

                                        9. Limits & Performance\u00a0<\/b><\/h4>

                                        Salesforce Governor Limits:<\/span><\/p>

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

                                          10. Support & Escalation<\/b><\/h4>
                                          • Level 1:<\/b> Salesforce Admins check logs & metadata.<\/span><\/li>
                                          • Level 2:<\/b> RDN Team (RightWave Inc.)<\/span><\/li><\/ul>

                                            Escalation Contact:<\/b> RightWave Team<\/span><\/h4>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/section>\n\t\t\t\t<\/div>\n\t\t","protected":false},"excerpt":{"rendered":"

                                            RDN-SFDC Integration This guide provides step-by-step instructions for integrating Salesforce (SFDC) with the RDN platform using a metadata-driven, asynchronous integration package. 1. Purpose This guide provides step-by-step instructions for integrating Salesforce (SFDC) with the RDN platform using a metadata-driven, asynchronous integration package. It covers: Installation & configuration steps Metadata setup and field mappings Operational workflows…<\/p>\n","protected":false},"author":47,"featured_media":0,"parent":86839,"menu_order":1,"comment_status":"closed","ping_status":"closed","template":"elementor_header_footer","meta":{"footnotes":""},"class_list":["post-90199","page","type-page","status-publish","hentry"],"_links":{"self":[{"href":"https:\/\/rightwave.com\/rwi\/wp-json\/wp\/v2\/pages\/90199","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/rightwave.com\/rwi\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/rightwave.com\/rwi\/wp-json\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/rightwave.com\/rwi\/wp-json\/wp\/v2\/users\/47"}],"replies":[{"embeddable":true,"href":"https:\/\/rightwave.com\/rwi\/wp-json\/wp\/v2\/comments?post=90199"}],"version-history":[{"count":10,"href":"https:\/\/rightwave.com\/rwi\/wp-json\/wp\/v2\/pages\/90199\/revisions"}],"predecessor-version":[{"id":90227,"href":"https:\/\/rightwave.com\/rwi\/wp-json\/wp\/v2\/pages\/90199\/revisions\/90227"}],"up":[{"embeddable":true,"href":"https:\/\/rightwave.com\/rwi\/wp-json\/wp\/v2\/pages\/86839"}],"wp:attachment":[{"href":"https:\/\/rightwave.com\/rwi\/wp-json\/wp\/v2\/media?parent=90199"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}