Social Commerce configuration

Procedure

1. First, obtain the following four parameters from your Demandware system and add them to your Social Commerce configuration. Once validated, these parameters establish a mapping between Demandware and Social Commerce.

2. Second, when creating a product synchronization task, choose either a one-time or recurring synchronization type. You must also provide the following five key parameters to establish the basic mapping and retrieve the correct product information.

3. Third, map the required product fields in Social Commerce to the corresponding fields in Demandware. Click Save. If the task is saved successfully, its status defaults to Disabled. You must manually enable the task from the task list. This two-step process acts as a final confirmation before data synchronization affects your existing product list.

Notes

1. You must configure the relationship between SiteID and PriceBook in Demandware. When you select a site in Commerce, the system automatically uses its corresponding currency unit to retrieve product prices.

2. By default, the product's online status in Demandware is mapped to the listed/delisted status in Social Commerce. If the 'Online' value is not configured in Demandware and is empty during synchronization, the system cannot synchronize the product to Social Commerce.

3. If a product is delisted, the system cannot retrieve its price. In this case, the price is set to 0 by default during data synchronization. If a product is listed during the initial synchronization and is synchronized successfully, but you later delist the product or SKU in Demandware, the next synchronization task will update the product's status to delisted and set its price to 0, as the price cannot be retrieved.

4. Before you enable a synchronization task, ensure that you have correctly configured the relationship between image directories and languages, or place all images in the Default directory. If images are stored in different language-specific directories, the system may fail to retrieve the image URLs. Additionally, if you add images or other content to the product description in Demandware, the system can currently only retrieve the URL's path without the domain name, which means the images will not display correctly.

5. Social Commerce requires products to have specification information. Therefore, ensure that the product's SPU in Demandware has a category, and that both the SPU and SKU are in the same directory. The Attribute and Variant Values fields must contain values. Otherwise, the product will fail to synchronize.

6. This feature supports two types of synchronization: one-time and recurring. For a one-time synchronization, you only need to set a start time. For a recurring synchronization, you must set a start time and a task polling interval in whole minutes. For example, a configuration of 30min/Cycle means a new task will start 30 minutes after the previous one completes, and this cycle will repeat until the specified end time.

API

Background

This feature helps developers with system integration. On this page, developers can find and understand the parameters and procedures for accessing the Open API and view relevant system information.

Features

• View and obtain all development parameters required for the tenant and access the API documentation at any time.

• Download all open-source sample code.

• View API call statistics.

Procedure:

1. Download the Storefront parameters as an Excel file, which includes channel name, x-channel, storefront name, and x-storefront-id.

2. Users manage their own Business Open API key pairs. Click your profile avatar, go to your personal center, and navigate to Open API Key Pair Management to create and manage your key pair.

Custom fields

Background

Salesforce Social Commerce lets you define custom fields for the Product(SPU), Order, Customer, and AfterSales tables to store relevant customer information. You can define up to 30 fields for each table. Currently, only the String data type is supported.

View custom fields

Go to Settings > Social Commerce Configuration > Custom Fields to view the list of custom fields. This list shows all the fields you have created for the Product(SPU), Order, Customer, and AfterSales tables in your organization. Click a field name to view its configuration details.

Create a field

Creating a custom field affects all customer and order data. A field cannot be deleted after creation. Please proceed with caution.

Procedure:

1. In the upper-right corner, click Create Field to add a new custom field.

2. After clicking Create Field, enter a Field Name. Note: This name is used to reference the field in API read and write operations. It must be unique and cannot be changed after creation.

3. Enter a field label, then confirm the field's default value and description. Adjust permissions for different Open APIs to ensure your developers can implement the correct read and write workflows for this field.

4. You can also configure the display status of this field on different pages.

5. Use the "Send via Webhook" setting to control whether the system automatically sends this custom field's data to a specified address when a webhook triggers an event.

Note that new fields only affect subsequent customer and order data; they do not apply to existing data.

Edit a field

As with field creation, you cannot change the Field Name, but you can modify other configuration options. Note that changing the default value does not affect historical data; it only applies to new customer and order data created afterward.

Use a custom field

Developers must access custom fields through the Open API and should refer to the API documentation for the relevant interface specifications.

Product reviews

Background

You can use review settings to enable or disable the "Create Review" feature. This feature is disabled by default when an organization is created. A tenant administrator can enable it in the review settings. Once enabled, you can use the Open API to create product reviews for completed orders. You can also specify the order statuses that allow reviews. The default status is "Completed", but you can select multiple other statuses. Changing the review settings does not affect historical review data. Note: Before you enable this feature, ensure that you have created at least one store.

Procedure

1. Go to Settings > Social Commerce Configuration > Product Review Settings to open the settings page.

2. Click Edit to enable or disable the review feature.

3. Select the desired order statuses.

4. Click Save to apply your changes.

Domain whitelist

Background

You can configure security settings for your system, including a domain whitelist. The second-level domain of any external link saved in the system must be on this whitelist. This setting primarily affects external links for product videos.

Note:

1. Only second-level HTTPS domains are supported (for example, https://xxx.salesforce.com). Top-level domains (for example, https://salesforce.com) and third-level or higher domains (for example, https://xxx.xxx.salesforce.com) are not supported.

2. The system supports only exact-match, valid domains. It does not allow wildcards or wildcard DNS resolution.

Procedure

1. Go to Settings > Social Commerce Configuration > Domain Whitelist to access the domain whitelist.

2. Click Add Domain, and enter the desired second-level domain in the dialog box.

3. Click Confirm to add the domain to the whitelist.

Background

• Tableau Server is a highly scalable, enterprise-grade business analytics platform. Its data visualization capabilities help you refine operations and adjust business strategies using intuitive analysis charts.

• Currently, the system provides a connection between SSC, SSM, and Tableau Server to help you analyze your business data in Tableau.

• To access this feature, click the Settings icon in the upper-right corner and find Tableau Server.

Tableau connection

Procedure:

1. The organization administrator must purchase a Creator account from the official Tableau website to obtain a valid license.

2. Download Tableau Desktop and deploy your server. To ensure successful data pushes, you must use Tableau Server version 2021.2.1 or later.

3. Log in to Tableau Server and create a site.

4. Enter the Site ID, URL, folder name, and personal access token from your Tableau Server account into the Tableau Server Integration configuration page.

5. After you complete the configuration, you can verify the connection by logging in to Tableau Server the next day to check for the pushed data source.

Tableau configuration

Procedure:

1. Click Edit to open the Tableau Server integration configuration page.

2. Enter and save the configuration information (Site ID, URL, folder name, personal access token, and its token secret).

3. After editing, click Save. The system runs an automated connection test in the background. If the test succeeds, the system saves the data. If it fails, the system returns an error status to the frontend.

Data source details:

• The data source pushed to Tableau Server consists of "Order" and "Customer" related data.

• The system updates the data source daily at 00:00:00.

• Each update is an incremental push delivered as a complete data package.

• The system records the timestamp of the last successful push. If several consecutive pushes fail, the reason for the failure is displayed. The next update will push all data accumulated since the last successful push. For example, if a push succeeds on March 9 but fails on March 10 and 11, the next successful push will include data from March 10 and 11.

• You can use the "Enable Data Push" toggle to start or stop data pushes. When enabled, the system pushes data according to the defined rules. If you disable it, a confirmation dialog appears: "Are you sure you want to stop pushing data to Tableau Server? If you do, the system will no longer push data on a schedule." Clicking Confirm will turn off the toggle and stop scheduled data pushes in the backend.

Background

• The audit feature provides log audit capabilities for security, compliance, and traceability.

• There are two types of logs: operation log and login log.

• The operation log categorizes events into Commerce events and public events.

Logs

• The operation log records the following data fields: Operator Account, Operation Time, Operation Type, Operation Name, URL Interface, Operation Object, Parameters (for POST and GET), HTTP Method, Return Value, Client Information (optional), source IP, Source Port, Destination IP, and Destination Port.

• Modules recorded in the operation log include: Channel, Product, Gift, Order, After-sales, Notification, webhook, Tableau, custom field, Promotion, download center, and Open API key pair.

• The login log records the following data fields: Account, Login Time, Login System, Login Device, and Login Result.

Log export

To improve query performance and user experience, the login log and operation log export functions use asynchronous export. You must retrieve exported data from the download center. You must wait at least five minutes between consecutive exports.

You can only export the data currently displayed in the list.

To export the logs currently loaded in the list, first apply the desired filters and search criteria. For example, to export the logs for the last month, set the time range to one month and click Query. The list will load the records for that period. You can then click Export to export the filtered data.

Procedure:

1. Set the desired filters and search criteria in the log list.

2. Click Query. The log list updates to show the filtered data.

3. Click the Export button in the upper-right corner of the log list.

4. In the export dialog box, click Export.

5. In the success dialog box, click Download Center.

6. In the download center, find the corresponding export task and click Download.

7. The log export is complete.