Managing Outbound System Configuration

Adding Outbound System Configuration

From the side menu select Toolbox, select System Setup, select Outbound, and then select Outbound Configuration.
Click New and complete the following:
1. Context: Select a value from the list.
  1. Select Global when you want to define Chain level outbound system configurations that all properties in the chain can use.
  2. Select Property when you want to define Property level outbound system configurations that a property can use.
2. Outbound Type: Select the Outbound type for the type of system you want to create an outbound configuration.
  
  Note:
  See Outbound System Types and Respective Configurations for details.
3. Outbound Code: Enter the Unique Outbound code you want to create, for example, SGAP1, CRMC1, CRMP1, and so on.
  
  Note:
  The Outbound Code is unique in the given OPERA Cloud multi-tenant instance.
4. Outbound Description: Enter the summary description of the outbound system details being configured.
5. Protocol: Gets defaulted with the supported protocol REST or XML for the selected Outbound Type for user information.
6. Enable External System: Select this option if you want to create an External System Code and External Database Code, same as Outbound Code.
7. Enable Conversions: This option is enabled when the above option is selected. Select this option to define Data Value Mappings for the Outbound Code created.
8. Default Property: This is visible when Context is Global. Select a default Property from the list to use it for DVM Conversions.
9. External Property: This field is visible when above option is selected to define Property conversion code.
10. Authorization Type: Select a value from the list:
  1. BASIC - when external system provides only basic authentication details like service account user name and service account password key details.
  2. OAUTH - when external system provides open authorization details like OAuth URL, Service Account & Key, and Clientid and Secrete details.
  3. TOKEN - when the integrated system provides only Token based authorization. Token Key length is supported up to 256 characters.
  4. NONE - when there is no authorization required; applicable only for CRM_LEGACY outbound type configuration.
11. Grant Type: Select a value from the list:
  1. Password - when external system provides you Service Account & Key and Client Id & Key details.
  2. Client Credentials - when the external system provides you only the Client Id & Key details.
12. Scope: Enter the Scope URL if provided by the External System.
13. Application Key: Enter the Application Key provided by the External System. Key length is supported up to 256 characters.
14. Bypass Proxy: Select this check box when you configure the endpoint URL provided by Oracle Cloud within the same region. Do not enable if the URL is from a cross region or non-Oracle Cloud.
15. Service Details:
16. Service Name: Defaulted value RESTAPIBaseURL.
17. Service Path: Enter the external system's REST APIs base URL. Path should not include any relative path, query parameters or path parameters.
  1. For example, you need to set Base URL only, which is https://mycrmsystem.com/crm/v1/.
  2. In this case, for Profile Lookup, the target URL is generated as https://mycrmsystem.com/crm/v1/externalSystems/{systemCode}/chains/{chainCode}/externalProfiles.
Click Save.

Editing Outbound System Configuration

From the side menu, select Toolbox, select System Setup, and then select Outbound System Configuration.
Enter search criteria and click Search.
Select the Outbound System in search results, click the vertical ellipsis, and select Edit.
Click Save.

Deleting Outbound System Configuration

From the side menu, select Toolbox, select System Setup, and then select Outbound System Configuration.
Enter search criteria and click Search.
Select the Outbound System in search results, click the vertical ellipsis, and select Delete.
Click Delete again to confirm.