Data Management (DMS) integrates with DingTalk Standard Edition, DingTalk Exclusive Edition, Feishu, and Lark notification channels. You can view notifications on mobile devices and clients, and approve tickets on your mobile device.
Prerequisites
You have an organization set up in DingTalk or Feishu.
This organization must be an internal organization of your enterprise, not a public organization of Alibaba Cloud, such as Alibaba Cloud technical support.
Usage notes
-
You can approve tickets only on mobile devices.
-
If you are an Alibaba Group internal user, contact DMS technical support (DingTalk group ID: 87370028482).
-
The US site does not support message notifications.
Preparations
-
Configure an application to receive messages.
DingTalk Standard and Exclusive
-
Create an application.
-
Log on to and join a DingTalk organization.
-
Log on to the DingTalk Open Platform.
-
Select your enterprise's organization. For example, select "XXX Test Organization".
-
-
Go to the DingTalk console to create a DingTalk application.
-
In the upper-right corner of the page, click My Background.
-
Click the Application Development tab. In the left-side navigation pane, choose .
-
Click Create Application.
-
Enter an Application Name and Application Description, and then click Save.
-
-
Configure a DingTalk chatbot to receive messages.
-
Click the name of the application you created to go to the application editing page.
-
In the left-side navigation pane, choose , and add a chatbot on the page that appears.
-
Configure the chatbot information, such as Chatbot Overview, Chatbot Description, and Message Receiving Mode, and then click Publish.
NoteFor Message Receiving Mode, select HTTP Mode.
-
-
Configure the web application.
-
After you add the web application, click Web Application in the Application Capabilities menu.
-
Set the application homepage URL and click Save.
The URL must match your DMS deployment region. For example, if your deployment region is Singapore, set the homepage URL to
https://dms-ap-southeast-1.alibabacloud.com.NoteTo view your deployment region, see Switch the DMS deployment region.

-
China (Hangzhou):
https://dms-cn-hangzhou.alibabacloud.com. -
Japan (Tokyo):
https://dms-ap-northeast-1.alibabacloud.com. -
Singapore:
https://dms-ap-southeast-1.alibabacloud.com. -
Malaysia (Kuala Lumpur):
https://dms-ap-southeast-3.alibabacloud.com. -
Indonesia (Jakarta):
https://dms-ap-southeast-5.alibabacloud.com. -
Saudi Arabia (Riyadh):
https://dms-me-central-1.alibabacloud.com. -
China (Hong Kong):
https://dms-cn-hongkong.alibabacloud.com. -
South Korea (Seoul):
https://dms-ap-northeast-2.alibabacloud.com.
-
-
-
Configure permissions.
In the left-side navigation pane, choose and apply for the following permissions:
-
Basic permissions to call SNS API operations
-
Read permissions for member information
-
Permission to get basic member information by mobile number
-
Basic permissions to call enterprise API operations
-
Basic permission to get user access credentials for DingTalk Open API
-
Permission to manage basic information of DingTalk groups
-
Permission for enterprise internal chatbots to send messages
-
Write permission for interactive card instances
-
-
Create and publish a new version.
You must publish a version of the enterprise internal application so that other users in the enterprise can use it.
In the left-side navigation pane, choose Version Management & Publishing, click Create New Version, enter the required configuration information, and then click Save.
-
-
Create a card.
-
Create a new template.
-
Go to the Card Platform and click Create Template.
-
Enter the Template Name, select the Card Type and Card Template Scenario, and then click Create.
Set Card Template Scenario to Regular Card and select the application you created as the associated application.
-
-
Import the card template.
Choose to import and save the notification card template. For a sample template file, see DingTalkTemplate.json.
-
Publish the notification card template.
-
Feishu and Lark
-
Log on to the Feishu or Lark Open Platform and go to the developer console.
-
Go to the Feishu Open Platform or Lark Open Platform.
-
Click Login.
The account you use to log on must belong to the target enterprise organization, such as "XXX Test Organization".
-
After you log on, go to the Developer Console.
-
-
Click Create Enterprise Internal Application, configure the Name and Application Description, and then click Create. For more information, see Self-managed enterprise application development process.
-
Add a Feishu chatbot.
-
(Optional) Click the application name to go to the application editing page.
NoteYou can skip this step for newly created applications.
-
In the left-side navigation pane, choose .
-
On the Add by Capability tab, click Add on the Chatbot card.
-
On the Chatbot page, enter a name for the chatbot and click Save.
-
-
Add a web application.
-
In the left-side navigation pane, choose .
-
On the Add by Capability tab, click Add on the Web Application card.
-
On the Web Application page, set the Mobile Homepage URL and click Save.
The homepage URL must match your DMS deployment region. For example, if your deployment region is Singapore, set the homepage URL to
https://dms-ap-southeast-1.alibabacloud.com.NoteTo view your deployment region, see Switch the DMS deployment region.

-
China (Hangzhou):
https://dms-cn-hangzhou.alibabacloud.com. -
Japan (Tokyo):
https://dms-ap-northeast-1.alibabacloud.com. -
Singapore:
https://dms-ap-southeast-1.alibabacloud.com. -
Malaysia (Kuala Lumpur):
https://dms-ap-southeast-3.alibabacloud.com. -
Indonesia (Jakarta):
https://dms-ap-southeast-5.alibabacloud.com. -
Saudi Arabia (Riyadh):
https://dms-me-central-1.alibabacloud.com.
-
-
-
Add a redirect URL and an H5 trusted domain.
-
In the left-side navigation pane, choose .
-
On the Redirect URL tab, configure the Redirect URL and H5 Trusted Domain.
The redirect URL and H5 trusted domain must match your DMS deployment region. For example, if your deployment region is Singapore, set the redirect URL to
https://dms-ap-southeast-1.alibabacloud.com/console/mobile/index/and the H5 trusted domain tohttps://dms-ap-southeast-1.alibabacloud.com. -
Click Add for each entry.
-
-
Configure application permissions.
-
In the left-side navigation pane, choose .
-
On the Permission Management tab, click Enable Permissions.
-
On the Application Identity Permission tenant_access_token tab, apply for the following permissions. For more information about how to configure permissions and for a list of permissions, see Request Permissions and Permission list.
-
Get user ID
-
Get user ID by mobile number or email
-
Upload images and attachments to cloud documents
NoteThis permission is not supported by Lark.
-
Get and send one-on-one and group messages
-
Send messages as an application
-
Send messages to multiple users in batches
-
Get and upload image or file resources
-
-
-
Publish an application version.
You must publish a version of the enterprise internal application so that other users in the enterprise can use it.
-
In the left-side navigation pane, choose .
-
Click Create Version.
-
Enter the Application Version Number, select the Default Mobile Capability, and then click Save.
For Available Scope, select All Members.
-
-
-
Obtain the key information from DingTalk, DingTalk Exclusive Edition, or Feishu. You need this information to configure the notification channel in DMS.
DingTalk Standard
-
Get the AppId, AgentId, AppKey, and AppSecret of the application
On the Credential and Basic Information page of the DingTalk Open Platform, get the AppId, AgentId, AppKey, and AppSecret.
-
Get the RobotCode
On the page of the DingTalk developer platform, get the RobotCode.
-
Get the card template ID
On the page of the Card Platform, get the card template ID.
-
Get the CorpId (optional)
Go to the DingTalk Developer Console and click your profile picture to get the CorpId.
NoteAfter you configure the CorpId parameter in the DMS notification channel, you can receive messages and approve tickets without switching your DingTalk organization to the one associated with the enterprise internal application.
DingTalk Exclusive
-
Get the AppKey and AppSecret of the application
On the Basic Information page of the DingTalk Open Platform, get the AppKey and AppSecret.
-
Get the RobotCode
On the Chatbot page of the DingTalk Open Platform, view the credential information to get the RobotCode.
-
Get the card template ID
On the page of the Card Platform, get the card template ID.
-
Get the CorpId (optional)
Go to the DingTalk Developer Console and click your profile picture to get the CorpId.
NoteAfter you configure the CorpId parameter in the DMS notification channel, you can receive messages and approve tickets without switching your DingTalk organization to the one associated with the enterprise internal application.
Feishu and Lark
On the page of the Feishu Open Platform or Lark Open Platform, get the AppId and AppSecret.
-
Step 1: Enable and configure notification channels in DMS
The channel management feature in DMS lets you enable or disable tenant-level notification channels and manage configurations for applications such as Feishu and DingTalk Exclusive Edition.
After you enable a channel, DMS uses it to send notifications based on your configured settings.
Only administrators and DBAs can configure notification channels.
Log in to DMS 5.0.
-
In the upper-left corner of the console, click the
icon and choose .NoteIf you are using the DMS console in normal mode, choose from the top navigation bar.
-
In the upper-left corner of the page, click Channel Management.
-
Select the target notification channel.
-
Configure the required information for Feishu, Lark, DingTalk, or DingTalk Exclusive Edition.
The following steps use the Feishu channel as an example; the process for other channels is similar.
-
In the Feishu channel section, click Edit.
-
Enter the AppId and AppSecret, and then click Save.
-
Step 2: Set notification recipients
The following example shows how to configure notifications for a data export ticket that is pending approval:
-
An administrator adds the users who will receive notifications to DMS. For more information, see User management.
-
An administrator or DBA goes to the Notification Management page in the DMS console.
On the Notification Management page, select the DMS module whose notification settings you want to update.
-
From the Module / Business type drop-down list, select .
-
Find the ticket with the Pending approval business status and click Modify in the Actions column.
-
In the Additional Notification User section, select the target user and click Confirm.
-
Enable message notifications.
DMS then sends notifications for subsequent data export tickets pending approval directly to the user's DingTalk, DingTalk Exclusive Edition, or Feishu.
Related topics
DMS lets you process tickets quickly on mobile devices, greatly improving development efficiency. For more information, see Approve tickets on mobile devices.
FAQ
-
Q: I have configured a notification channel for Feishu, DingTalk, DingTalk Exclusive Edition, or Lark in my personal information, but I am not receiving DMS notifications. Why?
A: Check whether you have enabled the notification channel for Feishu, DingTalk, DingTalk Exclusive Edition, or Lark at the tenant level. Your settings take effect only after the channel is enabled, which allows DMS to send you notifications through it. To enable the channel, see Step 1: Enable and configure notification channels in DMS.
-
Q: I have configured the notification channel and specified users to receive messages, but I am still not receiving notifications from DingTalk or Feishu. Why?
A: Follow these steps to resolve the issue:
-
Check whether an administrator or DBA has enabled the corresponding channel in DMS by navigating to . For more information, see Step 1: Enable and configure notification channels in DMS.
-
Click your DMS user profile picture and ensure the switch for the notification method is on.
In the drop-down menu, click Account Information. On the user information panel, verify that the target notification channel is configured in the Notice field.
-
-
Q: I have not changed my notification settings, but I suddenly stopped receiving notifications from DingTalk or Feishu. What could be the reason?
A: This may happen if the number of API calls for your enterprise internal application exceeds the limit. Check the API call volume in the developer console of DingTalk or Feishu. For information on how to adjust the API call limit, see the official documentation for DingTalk and Feishu.