Loading
Feature degradation | Gmail Email delivery failureRead More
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
            Modify an Agent Action Integration Procedure

            You are here:

            1. Salesforce Help
            2. Docs
            3. Financial Services Cloud Admin Guide

            Modify an Agent Action Integration Procedure

            You can customize the prebuilt BSA agent action IPs to add your own business logic and data validation.

            Required Editions

            Available in: Lightning Experience
            Available in: Professional, Enterprise, and Unlimited Editions
            User Permissions Needed
            To modify Integration Procedures: Omnistudio Admin

            For example, if you want your service reps to collect MICR (Magnetic Ink Character Recognition) numbers from a customer for a stop check payment request, you can add logic to make the MICR number mandatory and validate if the user input to MICR number is nine digits. Similarly, you can add conditional logic to check if the Check Number exists and validate if the user input to Check Number is six digits.

            1. Create an Integration Procedure from an existing StopCheckPayment_CreateCase IP.
              1. From the Integration Procedure list view page, select and open the StopCheckPayment_CreateCase IP that you want to customise for your agent.
              2. Create a new version to add your custom validation logic. For example, StopCheckPayment_CreateCase - Version 1 in this case.
            2. Create conditional blocks and response actions to handle different validation scenarios and test to verify the customizations.
              1. CheckNumberMissing: A conditional block and response action to handle cases where the check number is missing.
              2. MICRMissing: A conditional block and response action to handle cases where the MICR is missing.
              3. MICRIsNotNineDigits: A conditional block and response action to validate if the MICR is not nine digits.
              4. CheckNumberIsNotSixDigits: A conditional block and response action to validate if the check number is not six digits.
            3. Click Execute.

              Verify that the JSON results are composed correctly according to the requirements.

            4. Click Configure Agentforce.
            5. Define the input and output data for the Integration Procedure in JSON format, and then click Verify Data.
              The data structure is updated automatically.
              1. Input Data: accountid (String), accountName (String), financialAccountNum (String), financialAccountType (String), checkDate (Date), payee (String), amount (Integer), checkType (String), startingCheckNumber (String), endingCheckNumber (String), checkNumber (String), MICR (String).
              2. Output Data: apiResponse (Object), caseId (String), caseNumber (String), svcCatalogRequestId (String), error (String), MICRValidationResult (String), CheckNumberValidationResult (String).
            6. Click Save.
            7. Activate the Integration Procedure.
              You can test for new validations in the Agentforce Conversation Preview.

            You’re now ready to use the enhanced version of Check Payment Cancellation subagent in your Agentforce conversations.

             
            Loading
            Salesforce Help | Article