Configuring Source Specific Settings for Live Chat
Updated
The Source Specific Settings screen in data connectors is where you configure the details about the data source you want to connect to. This screen allows you to define the source's type, parameters, and access details to ensure the data connector can interact with it correctly. The options that appear in the Source Specific Settings screen depends upon the type of entity (We will consider System entity Live Chat here) and the entity source selected in the previous screens.
Note: Before you start, go through the following links to get an insight on installing the connector, different entities supported, and configuring connector details.
Configuring Source Specific Settings Screen
The Source Specific Settings is a dynamic screen, the values of which depend on the Entity Source chosen at the previous step. Depending on the selected Entity Source in the previous screens, additional specifications need to be configured.
Scenario 1: If you selected S3 as the data source, refer Configuring an S3 Connection.
Scenario 2: If you selected GCS as the data source, refer Configuring a GCS Connection.
Scenario 3: If you selected SFTP as the data source, refer Configuring an SFTP Connection.
Scenario 4: If you selected Zendesk as the data source, refer Configuring a Zendesk Connection.
Scenario 5: If you have selected Azure Blob as the data source, refer Configuring Azure Blob Connection.
Note: For steps to access directories in SFTP, S3, Azure Blob, and GCS, refer Selecting Directories for SFTP/S3/GCS/Azure Blob .
The table covers information on different fields in the Source Specific Settings screen and their definition.
Parameters | Description |
Upload Sample File | Drag and drop attachments here. Supported file formats include ZIP and GZ, with a maximum size of 10.0 MB. For users to ingest any data in the platform the files are supposed to be in a Sprinklr predefined format. If you want to look at the template of the file that needs to be uploaded, a link to download the sample file is available at the same component. |
Source file Format | The source file format specifies the format of the file. There are currently two file formats:
|
Source File Prefix | If the source is an SFTP location, S3 bucket, or GCS, this value will help the system identify as to which file does it has to process. For example, If the connector is activated in a manner that it must create a live chat cases from an SFTP location, this prefix will help the system identify which zip files must be read from the SFTP location to create cases out of |
Metadata File Prefix | This is used to identify which file is the metadata file inside the zip file(the source file) |
Metadata File Extension | Select the extension of the metadata file(csv, xml or JSON) |
Metadata File - CSV Delimiter Type | If the extension chosen above is CSV, select the delimiter type. |
Messages File Prefix | This is used to identify which file is the message file inside the zip file(the source file) |
Messages File - CSV Delimiter Type | Choose the delimiter type for message level CSV file(CSV is the only supported type for message level file) |