Loading
Upcoming Mandatory Changes to Public Key Infrastructure (PKI)Read More
Salesforce Enforces New Security Requirements in Summer 2026Read More
Collections and Recovery
Table of Contents
Filter by (0)Add
Select Filters

          No results
          No results
          Here are some search tips

          Check the spelling of your keywords.
          Use more general search terms.
          Select fewer filters to broaden your search.

            Search all of Salesforce Help
            Search all of Salesforce Help
            Create and Configure Integration Definitions and Named Credentials

            You are here:

            1. Salesforce Help
            2. Docs
            3. Collections and Recovery

            Create and Configure Integration Definitions and Named Credentials

            To connect Salesforce with an external system, create integration definitions. APIs work with the integration definitions to perform operations in both Salesforce and the external system. Link the prebuilt APEX class to the integration definition.

            Required Editions

            Available in: Lightning Experience
            Available in: View product and edition availability.
            User Permissions Needed
            To create Apex Defined integration definitions: Customize Application
            1. Create an integration definition with these details, save the changes, and activate the integration definition.
              Type Apex Defined
              Name PostComplianceDetails
              Apex Class fsc_collection_apex.RequestComplianceIntegrationProvider
              Plain Client Id Attribute Copy the consumer key from the local external client application that you created earlier.
              If you plan to change the integration definition name, make sure that you update the changed name in the remote action that's called by the integration procedure, Collections_CheckOutboundCallComplianceForBorrowerContacts.
            2. Create an external credential with these details, and save the changes. Make sure that you create a Principal.
              Authentication Protocol OAuth 2.0
              Name PostComplianceDetail
              Authentication Flow Type Client Credentials with Client Secret Flow
              Identity Provider URL Copy the Callback URL from the external auth identity provider that you created earlier and paste it here.
            3. Create a named credential with these details, and save the changes.
              Field Description
              Label postComplianceNC
              Name postComplianceNC
              URL

              Provide the API end point of the compliance application. Append the compliance query string and a specific path in the callout definition’s reference to the named credential as shown in this example.

              https://orgfeature.cumuluscapital.com/services/data/v64.0/connect/compliance/procedure/CollectionsAndRecovery/evaluate
              Enabled for Callouts Turn on this setting
              External Credential Select the external credential that you created earlier
            4. To link the new external credential principal to permission sets or user profiles so that users can make callouts by using the named credential, create a permission set and add the external credential principal.
            5. To enable any user performing an authenticated callout, in the new permission set, provide View All Fields and Modify All Records object permissions to the User External Credentials object.
            6. Assign the new permission set to the user performing an authenticated callout.
             
            Loading
            Salesforce Help | Article