Data Management (DMS) integrates with DingTalk, DingTalk Enterprise, Feishu, and Lark as notification channels. Once configured, DMS sends ticket notifications directly to users on mobile devices and clients, and approvers can approve tickets from their mobile devices.
Prerequisites
Before you begin, ensure that you have:
A DingTalk or Feishu enterprise organization (internal enterprise organization, not a public Alibaba Cloud organization such as Alibaba Cloud Service Support)
Administrator or database administrator (DBA) access to the DMS console
Usage notes
Ticket approval is supported only on mobile devices.
The US site does not support message notifications.
If you are an Alibaba Group internal user, contact DMS technical support via DingTalk group number 87370028482.
How it works
Setting up notification channels involves three stages:
Create and configure an application on the DingTalk or Feishu Open Platform to receive DMS messages.
Retrieve credentials from the platform and configure a notification channel in DMS.
Assign users to receive notifications for specific ticket types.
Stage 1: Set up an application on the messaging platform
Follow the setup guide for your platform.
DingTalk
For full platform setup details, see the DingTalk Open Platform documentation.
Step 1: Create an application
Log on to the DingTalk Open Platform and select your enterprise organization.Lark Open PlatformFeishu Open PlatformDingTalk Open PlatformDingTalk Open PlatformCard PlatformCard PlatformLark Open PlatformFeishu Open PlatformDingTalk Open Platform
Click My Console in the upper-right corner.
Go to Application Development > Internal Enterprise Application > DingTalk Application and click Card PlatformCreate Application.
Enter an Application Name and Application Description, then click Save.
Step 2: Add a robot
Click the application name to open the editing page.
In the left-side navigation pane, go to Application Capabilities > Add Application Capability and add a robot.
Fill in Robot Introduction and Robot Description, and set Message Reception Mode to HTTP mode.
Click Publish.
Step 3: Configure a web application
In the Application Capabilities menu, click Web Application.
On the Web App page, enter the URL for the Mobile Homepage and click Save.
The homepage URL depends on the current DMS data processing region. For example, if the data processing region is Singapore, the application homepage URL is
https://dms-ap-southeast-1.alibabacloud.com.NoteTo view the data processing region, see Switch DMS deployment regions.
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.SAU (Riyadh - Partner Region):
https://dms-me-central-1.alibabacloud.com.
Set the homepage URL for the application and click Save.
The homepage URL depends on the current DMS data processing region. For example, if the data processing region is Singapore, the application homepage URL is
https://dms-ap-southeast-1.alibabacloud.com.NoteTo view the data processing region, see Switch DMS deployment regions.
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.SAU (Riyadh - Partner Region):
https://dms-me-central-1.alibabacloud.com.China (Hong Kong):
<a href="https://dms-cn-hongkong.alibabacloud.com" id="0c5ce72573cfn" uuid="ba897e6a-66d7-4d24-b1cd-c1cc256337fc">https://dms-cn-hongkong.alibabacloud.com</a>.South Korea (Seoul):
<a href="https://dms-ap-northeast-2.alibabacloud.com" id="95873e62e290c" uuid="3ed56fc3-194d-4618-b7eb-70ae2871deeb">https://dms-ap-northeast-2.alibabacloud.com</a>.
Set the homepage URL based on your DMS data processing region, then click Save. To find your data processing region, see Switch DMS deployment regions.
Region Homepage URL China (Hangzhou) https://dms-cn-hangzhou.alibabacloud.comJapan (Tokyo) https://dms-ap-northeast-1.alibabacloud.comSingapore https://dms-ap-southeast-1.alibabacloud.comMalaysia (Kuala Lumpur) https://dms-ap-southeast-3.alibabacloud.comIndonesia (Jakarta) https://dms-ap-southeast-5.alibabacloud.comSAU (Riyadh - Partner Region) https://dms-me-central-1.alibabacloud.comChina (Hong Kong) https://dms-cn-hongkong.alibabacloud.comSouth Korea (Seoul) https://dms-ap-northeast-2.alibabacloud.com
Step 4: Request permissions
In the left-side navigation pane, go to Development Configuration > Permission Management and request the following permissions:
Basic permissions required to call Simple Notification Service (SNS) APIs
Read permission for member information
Permission to retrieve basic member information based on mobile phone numbers
Basic permission to call enterprise APIs
Basic permission to retrieve user access credentials for DingTalk open interfaces
Permission to manage basic information of DingTalk groups
Permission for internal enterprise robots to send messages
Write permission for interactive card instances
Step 5: Create and publish a version
In the left-side navigation pane, go to Version Management and Publishing, click Create New Version, enter the configuration details, and click Save.
You must publish a version before other users in the enterprise can use the application.
Step 6: Create a card template
DMS uses a card template to format notification messages. Create the template on the DingTalk Card Platform:
Go to the Card Platform and click Create Template.
Enter a Template Name, select a Card Type and set Card Template Scenario to Normal Card, and select your application under Associated Application. Click Create.
Go to More > Import Template, import the DingTalkTemplate.json sample template, and save.
Publish the card template.
DingTalk Enterprise
For full platform setup details, see the DingTalk Enterprise Open Platform documentation.
Step 1: Create an application
Follow the same steps as DingTalk to create an internal enterprise application, add a robot (set Message Reception Mode to HTTP mode), and configure a web application with the homepage URL for your DMS data processing region (see the region URL table in the DingTalk section above).
Step 2: Request permissions
Request the same eight permissions listed in the DingTalk section above.
Step 3: Create and publish a version
Follow the same steps as DingTalk to publish a version.
Step 4: Create a card template
On the Card Platform, go to Development Tools > Card Builder to create and publish the card template. Use the DingTalkTemplate.json sample template.
Feishu/Lark (International)
For full platform setup details, see Development process for custom enterprise applications.
Step 1: Create an application
Log on to the Feishu Open Platform or Lark Open Platform using an account that belongs to your enterprise organization.
Go to the Developer Console and click Create Custom Enterprise Application.DingTalk developer consoleDingTalk developer console
Enter a Name and Application Description, then click Create.
Step 2: Add a robot
In the left-side navigation pane, go to App Features > Add App Feature.
On the Add By Feature tab, click Add in the Robot card.
Enter a robot name and click Save.
Step 3: Add a web application
In the left-side navigation pane, go to App Features > Add App Feature.
On the Add By Feature tab, click Add in the Web App card.
On the Web App page, enter the URL for Mobile Homepage based on your DMS data processing region, then click Save. To find your data processing region, see Switch DMS deployment regions.
Region Homepage URL China (Hangzhou) https://dms-cn-hangzhou.alibabacloud.comJapan (Tokyo) https://dms-ap-northeast-1.alibabacloud.comSingapore https://dms-ap-southeast-1.alibabacloud.comMalaysia (Kuala Lumpur) https://dms-ap-southeast-3.alibabacloud.comIndonesia (Jakarta) https://dms-ap-southeast-5.alibabacloud.comSAU (Riyadh - Partner Region) https://dms-me-central-1.alibabacloud.com
Step 4: Configure redirect URL and trusted H5 domain
In the left-side navigation pane, go to Development Configuration > Security Settings.
On the Redirect URLs tab, you can configure the Redirect URL and Trusted H5 Domain Name.
The redirection URL and trusted H5 domain name depend on the DMS data processing region. For example, if the DMS data processing region is Singapore, the redirection URL is
https://dms-ap-southeast-1.alibabacloud.com/console/mobile/index/and the trusted H5 domain name ishttps://dms-ap-southeast-1.alibabacloud.com.On the Redirect URLs tab, add your Redirect URL and Trusted H5 Domain Name based on your DMS data processing region. For example, if your region is Singapore:
Redirect URL:
https://dms-ap-southeast-1.alibabacloud.com/console/mobile/index/Trusted H5 domain name:
https://dms-ap-southeast-1.alibabacloud.com
Click Add for each entry.
Step 5: Request permissions
In the left-side navigation pane, go to Development Configuration > Permission Management.
Click Enable Permissions.
On the App Identity Permission (tenant_access_token) tab, request the following permissions. For details, see Request Permissions and Permission Description.
Retrieve user ID
Retrieve user ID by mobile number or email
Upload images and attachments to cloud documents (Lark does not support this permission)
Retrieve and send private and group messages
Send messages as the application
Send messages to multiple users in batches
Retrieve and upload image or file resources
Step 6: Publish a version
In the left-side navigation pane, go to App Release > Version Management & Publishing and click Create Version.
Enter the App Version, select the Default Mobile Capability, set Availability to All Members, and click Save.
Stage 2: Retrieve credentials and configure a notification channel in DMS
After setting up the application, retrieve the credentials from the platform and add them to DMS.
Retrieve credentials
DingTalk
DingTalk
| Credential | Where to find it |
|---|---|
| AppId, AgentId, AppKey, AppSecret | Credentials and Basic Information page on the DingTalk Open Platform |
| RobotCode | Application Capabilities > Robot page |
| Card template ID | Template Management > Template List page on the Card Platform |
| CorpId (optional) | DingTalk developer console — click your profile picture |
Configuring CorpId lets you receive messages and approve tickets without switching your DingTalk organization to the one where the custom enterprise application is located.
DingTalk Enterprise
DingTalk Enterprise
| Credential | Where to find it |
|---|---|
| AppKey, AppSecret | Basic Information page on the DingTalk Open Platform |
| RobotCode | Robot page — credential information section |
| Card template ID | Development Tools > Card Builder page on the Card Platform |
| CorpId (optional) | DingTalk developer console — click your profile picture |
Configuring CorpId lets you receive messages and approve tickets without switching your DingTalk organization to the one where the custom enterprise application is located.
Feishu/Lark
Feishu/Lark
| Credential | Where to find it |
|---|---|
| AppId, AppSecret | Basic Information > Credentials and Basic Information page on the Feishu Open Platform or Lark Open Platform |
Configure the notification channel in DMS
Only administrators or DBAs can configure notification channels.
Log on to the DMS console V5.0.
Click the
icon in the upper-left corner and choose All Features > Operations Management > Notification Management.In normal mode, choose Operations Management > Notification Management from the top menu bar.
Click Channel Management in the upper-left corner of the page.
Select your notification channel.
In the channel section, click Edit, enter the required credentials (for example, AppId and AppSecret for Feishu), then click Save.
The notification settings take effect only after you enable the channel.
Stage 3: Set users to receive notifications
This example shows how to configure notifications for data export tickets pending approval.
The administrator adds users to DMS. For details, see User Management.
The administrator or DBA opens the Notification Management page.
In the Module/Business Type filter, select Ticket > Data Exporting.
Find the ticket with the Pending Approval status and click Modify.
In the Additional Notification Users section, select the users and click OK.
Enable message notifications.
DMS now sends notifications for subsequent data export tickets pending approval directly to the specified users through DingTalk, DingTalk Enterprise, Feishu, or Lark.
FAQ
I configured Feishu, DingTalk, or Lark in my personal notification settings, but I'm not receiving notifications. Why?
The channel must be enabled at the tenant level before personal settings take effect. Go to Notification Management > Channel Management and verify that the relevant channel is enabled. For details, see Stage 2: Configure the notification channel in DMS.
I configured the notification channel and assigned users, but no messages are coming through. How do I troubleshoot this?
Check the following:
In DMS, go to Notification Management > Channel Management and verify that the channel is enabled.
Click your DMS profile picture and confirm that the notification channel is enabled in your notification method settings.
My notification settings haven't changed, but I suddenly stopped receiving messages. What happened?
Your custom enterprise application may have reached its API call limit. Check the API call volume in the DingTalk or Feishu developer console. For information on adjusting call limits, see the DingTalk billing documentation and Feishu API call limit documentation.
What's next
Process tickets on mobile devices to improve development efficiency. For details, see Approve tickets on a mobile device.