Mobile App Management

Prerequisites

You have enabled the fault management package. For details about billing, see Billing Items.

Precautions

Currently, WeCom, Lark, and DingTalk are supported.

Enabling WeCom Notifications

1. Log in to COC.
2. In the navigation pane, choose Basic Configurations > Mobile App Management.
3. In the WeCom area, click Enable Now.
   Figure 1 Enabling WeCom notifications
   

4. In the displayed drawer, set WeCom enabling parameters. For details about how to configure the parameters, see the following table.

   Table 1 Parameters for enabling WeCom

   Parameter	Description
   Enterprise ID	Unique identifier of an enterprise in WeCom. An enterprise ID cannot be changed after being saved. To obtain the enterprise ID, go to the enterprise management page and obtain the enterprise ID from the enterprise information.
   Authentication Password	Dedicated key of an app developed by WeCom or a basic app, which is used together with the app agent ID. To obtain the key, log in to the WeCom management backend and click App Management on the top menu bar. In the navigation pane, choose Apps. Under Self-built, select the app you created.
   Telephone Book Key	An independent key dedicated to the address book synchronization or management API. It is a type of basic app key. To obtain the key, log in to the WeCom management backend and click App Management on the top menu bar. In the navigation pane, choose Apps. Under Self-built, select the app you created.
   Service ID	A service ID is a unique identifier of the app for a WeCom third-party independent software vendor (ISV), which is also called a suite ID. This parameter is optional. To obtain the value, log in to the WeCom management backend and choose App Management and obtain the agent ID.

5. Click OK to enable WeCom notifications.

Enabling DingTalk Notifications

Before enabling DingTalk notifications, complete the pre-configurations on the DingTalk open platform.

1. Create an app.
   1. Add an app capability and select the web page application (Only the H5 app supports the group template function).
   2. On the permissions management page, add the corresponding API permissions. Search for permission and apply for the following permissions:
      • DingTalk group message management permissions (qyapi_chat_manage)
      • DingTalk group message read permissions (qyapi_chat_read)
      • Permissions (qyapi_get_member_by_mobile) of calling the API for obtaining the group member information based on phone numbers and names.
   3. Release an app version: Go to the version management and release page and create and release a version.
2. Create a robot: Go to the development capability page, in the scenario group list, select a robot.
3. Create a group template.
   1. On the development capability page, in the scenario group list, create a group template.
   2. You must select the created robot in the template.
   3. After all group template information is configured, you need to release the template for use.

To enable DingTalk notifications, perform the following steps:

1. Log in to COC.
2. In the navigation pane, choose Basic Configurations > Mobile App Management.
3. In the DingTalk area, click Enable Now.
   Figure 2 Enabling DingTalk notifications
   

4. In the displayed drawer, set DingTalk enabling parameters. For details about how to configure the parameters, see the following table.

   Table 2 Parameters for enabling DingTalk

   Parameter	Description
   Client ID	Unique identifier of an internal app or a third-party app of an enterprise on the DingTalk open platform. A client ID cannot be changed after being saved. To obtain the value, log in to the DingTalk open platform, go to the application development module, and find the DingTalk app. In the credential and basic information area, obtain the client ID.
   Client Secret	Key corresponding to the client ID, which is equivalent to the password of the app. To obtain the value, log in to the DingTalk open platform, go to the app development module, and find the DingTalk app. In the credential and basic information area, obtain the client secret.
   Group Template ID	Unique ID of a scenario group template, which is used to describe the corresponding group configurations (configurations for plug-ins, robots, and entries). To obtain the value, log in to the DingTalk open platform, go to the open capabilities module, access the scenario group page, and find the group template. Then, obtain the group template ID.
   Robot ID	Globally unique identifier of a DingTalk bot, also called the robot code. To obtain the value, log in to the DingTalk open platform, go to the open capabilities module, access the scenario group page, and find the robot option. Then, obtain the group robot ID.
   Service ID	Unique service ID generated after a data service is created on the DingTalk data asset platform. This parameter is optional. To obtain the value, log in to the DingTalk open platform, go to the app development module, and find the DingTalk app. In the credential and basic information area, obtain the agent ID.

5. Click OK to enable DingTalk notifications.

Enabling Lark Notifications

Before enabling Lark notifications, complete the pre-configurations on the Lark developer backend.

1. Create an enterprise app.
2. Adding an app: Add a robot.
3. Grant the following API permissions:
   • Obtain a user's ID (contact:user:id:readonly) using the corresponding mobile number or email address.
   • Obtain and update group information (im:chat).
   • Obtain and send one-on-one and group chat messages (im:message).
   • Update the group messages (im:chat:operate_as_owner) of the group created by the app.
4. Version management and release: Create and release an app version, and enable it to be available to all employees.

To enable Lark notifications, perform the following steps:

1. Log in to COC.
2. In the navigation pane, choose Basic Configurations > Mobile App Management.
3. In the Lark area, click Enable Now.
   Figure 3 Enabling a mobile app
   

4. In the displayed drawer, set Lark enabling parameters. For details about how to configure the parameters, see the following table.

   Table 3 Parameters for enabling Lark

   Parameter	Description
   App ID	Unique ID of an app on the Lark open platform. The value is globally unique and is automatically generated when an app is created. An app ID cannot be changed after being saved. To obtain the value, log in to the Lark developer backend, go to the enterprise-built app module, and find the Lark app. In the credential and basic information area, obtain the app ID.
   App Secret	Key corresponding to the app ID, which is equivalent to the password of the app. To obtain the value, log in to the Lark developer backend, go to the enterprise-built app module, and find the Lark app. In the credential and basic information area, obtain the app secret.
   Service ID	Service provider or HelpDesk ID. This parameter is optional. The value must be the same as the app ID. To obtain the value, log in to the Lark developer backend, go to the enterprise-built app module, and find the Lark app. In the credential and basic information area, obtain the app ID.

5. Click OK to enable Lark notifications.

Viewing Mobile Apps

1. Log in to COC.
2. In the navigation pane, choose Basic Configurations > Mobile App Management.
3. On the displayed page, check whether the mobile app is enabled.
   • If a mobile app is enabled, the bound information is displayed.
     Figure 4 Viewing enabled mobile apps
     
   • If a mobile app is not enabled, you can see Enable Now.
     Figure 5 Viewing disabled mobile apps
     

Changing a Mobile App Key

1. Log in to COC.
2. In the navigation pane, choose Basic Configurations > Mobile App Management.
3. Locate the target mobile app and click Modify Key.
4. On the displayed page, modify the key as required.

   Table 4 Parameters for modifying information about a WeCom account

   Parameter	Description
   Authentication Password	Dedicated key of an app developed by WeCom or a basic app, which is used together with the app agent ID. To obtain the key, log in to the WeCom management backend and click App Management on the top menu bar. In the navigation pane, choose Apps. Under Self-built, select the app you created.
   Telephone Book Key	An independent key dedicated to the address book synchronization or management API. It is a type of basic app key. To obtain the key, log in to the WeCom management backend and click App Management on the top menu bar. In the navigation pane, choose Apps. Under Self-built, select the app you created.
   Service ID	A service ID is a unique identifier of the app for a WeCom third-party independent software vendor (ISV), which is also called a suite ID. To obtain the value, log in to the WeCom management backend and choose App Management and obtain the agent ID.

   Table 5 Parameters for modifying information about a DingTalk account

   Parameter	Description
   Client Secret	Key corresponding to the client ID, which is equivalent to the password of the app. To obtain the value, log in to the DingTalk open platform, go to the app development module, and find the DingTalk app. In the credential and basic information area, obtain the client secret.
   Group Template ID	Unique ID of a scenario group template, which is used to describe the corresponding group configurations (configurations for plug-ins, robots, and entries). To obtain the value, log in to the DingTalk open platform, go to the open capabilities module, access the scenario group page, and find the group template. Then, obtain the group template ID.
   Robot ID	Globally unique identifier of a DingTalk bot, also called the robot code. To obtain the value, log in to the DingTalk open platform, go to the open capabilities module, access the scenario group page, and find the robot option. Then, obtain the group robot ID.
   Service ID	Unique service ID generated after a data service is created on the DingTalk data asset platform. To obtain the value, log in to the DingTalk open platform, go to the app development module, and find the DingTalk app. In the credential and basic information area, obtain the agent ID.

   Table 6 Parameters for modifying information about a Lark account

   Parameter	Description
   App Secret	Key corresponding to the app ID, which is equivalent to the password of the app. To obtain the value, log in to the Lark developer backend, go to the enterprise-built app module, and find the Lark app. In the credential and basic information area, obtain the app secret.
   Service ID	Service provider or HelpDesk ID. The value must be the same as the app ID. To obtain the value, log in to the Lark developer backend, go to the enterprise-built app module, and find the Lark app. In the credential and basic information area, obtain the app ID.

5. Click OK.

Deleting a Mobile App

A deleted mobile app cannot be used anymore. Exercise caution when performing this operation.

1. Log in to COC.
2. In the navigation pane, choose Basic Configurations > Mobile App Management.
3. Locate the mobile app you want to delete and click Delete.
4. Click OK.

Helpful Links

After a mobile app is created, it can be invoked during Handling an Incident Ticket Through a War Room.