DataWind supports integration with email, WeChat, DingTalk, Lark, and Webex interfaces for a variety of office scenarios, such as message push notifications, alert subscriptions, and connecting to Lark data sources. This article introduces how to perform office platform integration.

The product provides office platform integration capabilities, allowing enterprise domain administrators to configure application integration and email service settings for scenarios such as message push notifications, alert subscriptions, and connecting to Lark data sources.
Common application scenarios
Provides application configuration capabilities for office platforms, enabling users to configure settings independently based on application scenarios and the capabilities supported by the office platform. After configuring the office platform, the following features can be enabled:

• Message push notifications for chart monitoring and alerts
• Message push notifications for dashboard subscriptions
• Message push notifications for dataset synchronization SLA alerts
• Message push notifications for project authorization-related notifications
• Enable Lark Docs as a data source to create datasets
• Lark mobile app

1. On the "System Configuration" page, the enterprise domain administrator can click the "Office Platform" tab on the left and fill in the corresponding enterprise IM configuration items.
   
2. Click Office Platform and fill in the corresponding enterprise IM configuration items. For details on each enterprise IM configuration item, see Feature introduction.

Email service #

Common application scenarios

• Allows individual users to use the enterprise email for password recovery and reset.
• When a new account is created, account information and password are automatically sent via email notification.
• Subscribe to product messages and send them to designated users of the enterprise email.

Basic configuration
On the office platform page, click "Add New Platform", select "Enterprise Email", and complete the following configuration:

• Platform logo: You can use the default logo, or click the default logo to upload a custom local logo
• Platform name: You can use the default platform name or modify it
• Email server: Enter the SMTP protocol email server address
• Port number: Enter the port number
• Encryption protocol: Supports no encryption. Also supports selecting the mail server's TLS or SSL encryption protocol.
• Allowlist management: Enter email suffixes with @. Multiple groups are supported, separated by commas.
• Status: Enabled by default. To disable, configure here.

Message sending
After configuration, the product's subscription information can be sent to specified users via email.

• Sender email: Enter the sender address for sending. Subscription product information will be sent from this sender.
• Username: Enter the username for logging in to the sender email account.
• Authorization code/password: Enter the authorization code or password for logging in to the sender email account.
• Sender alias: This field is optional.
• Available products: The selected products can use this sending channel.
• Test recipient email: Enter a test email address.
• Verification code: Enter the verification code received by the test recipient to ensure that this sending channel is available.

WeCom #

On the office platform page, click "Connect new platform" and select "WeCom", then complete the following configuration:

• Platform logo: You can use the default WeCom logo, or click the default logo to upload a custom local logo.
• Platform name: You can use the default platform name or modify it.

Required

• Corp ID: The unique identifier for the company.
• Corp Secret: The application authorization code, used to obtain the access_token credential for calling the WeCom API for this application.
• Agent ID: The unique identifier for the application.
• Status: Enabled by default. To disable, configure here.

The Agent ID (application ID) and Secret (key) can be obtained as shown in the following figure.

The Company ID (enterprise ID) can be obtained as shown in the following figure.

Lark #

On the office platform page, click "Connect new platform" and select "Lark", then complete the following configuration:

• Platform logo: You can use the default Lark logo, or click the default logo to upload a custom local logo.
• Platform name: You can use the default platform name or modify it.

Required

• App ID: The unique identifier for the application.
• App Secret: The application authorization code, used to obtain the token credential for calling the Lark API for this application.
• Status: Enabled by default. You can disable it here if needed.

DingTalk #

On the office platform page, click "Connect new platform", select "DingTalk", and complete the following configuration:

• Platform logo: You can use the default DingTalk logo. Clicking the default logo also allows you to upload a custom local logo.
• Platform name: The default platform name can be used. You can also modify it.

Required

• Agent ID: The unique identifier of the application. When creating an application, the system automatically generates an Agent ID, which can be used for scenarios such as sending enterprise session messages.
• App Key: When creating an application, the system automatically assigns a pair of AppKey and AppSecret. This AppKey is the unique identifier during application development.
• App Secret: When creating an application, the system automatically assigns a pair of AppKey and AppSecret. Use AppKey and AppSecret to obtain access_token.
• Status: Enabled by default. You can disable it here if needed.

Webex #

Required

• Access Token
• Status: Enabled by default. You can disable it here if needed.

• Access Token: The access token of the BOT