Compared with before, Ding Talk has released restrictions on the use of IP for self-built applications. Now using the Ding Talk plug-in does not require a client proxy server, and the server provided by ShareCRM is used uniformly. (If accounts who are already using it need to switch to the server of ShareCRM, please contact the customer service of ShareCRM and contact the R&D personnel to deal with it.)

Before implementing the docking, a few key points are explained:

1. Callback Address:

DingTalk restricts a company to register only one callback address. The function of the callback address for our docking application is to monitor changes in the organizational structure of the DingTalk company in real time. Therefore, before realizing the docking, the implementation students can ask the customer whether the DingTalk company has registered the relevant callback event.

If there is a failure caused by the callback address during the configuration process, it will not affect the initialization of the address book, but you need to configure the application authorization in the DingTalk management background. Refer to the application authorization in catalog 4.

2. When configuring, you need to pay attention to the addition of DingTalk authorization, and don't forget the basic permissions such as mobile phone number information and address book.

3. At present, one DingTalk supports multiple CRM scenarios. Customers need to pay attention to that one CRM corresponds to one DingTalk application, that is, multiple applications need to be created on the DingTalk side to correspond to the CRM, which can be determined by the scope of application permissions. Which employees are visible? In addition, it should be noted that the homepage address of the mobile terminal or the homepage address of the PC terminal of multiple applications needs to be supplemented with the corresponding appID: namely:

https://www.fxiaoke.com/dingtalk/index.jsp?corpId=DingTalk Enterprise corpId&appKey=Application appkey

4. At present, the CRM agency and reminder messages are sent to DingTalk in Grayscale. If necessary, please contact Funshare customer service to contact Funshare R&D Grayscale.

5. Opening method: Contact Fanxiang customer service or the corresponding account manager to place an order to purchase a DingTalk connector.

The entire configuration docking process can be divided into two parts, one is the configuration of the DingTalk development platform. The second is: the docking interface configuration on the customer side of ShareCRM.

1.1 It is recommended to create a new H5 micro-app, so that you can click on the app on the mobile terminal to open the ShareCRM H5 terminal interface.

1.2 After creating the application, click "Development Management" to see the following information that needs to be supplemented:

(1) Server exit IP: copy and paste the address below to the server exit IP in the above picture

58.250.204.197, 119.254.150.2, 120.133.55.5, 103.235.239.34, 103.235.230.65, 114.67.19.130, 114.67.19.195, 43.228.181.1, 114.114.9.2347.1

(2) Fill in the homepage address of the application & the homepage address of the PC side: (Note, if a DingTalk company corresponds to multiple CRMs, you need to add the corresponding appkey. For details, refer to point 4 of the preceding instructions above)

https://www.fxiaoke.com/dingtalk/index.jsp?corpId=Fill in the corpid of your company

(3) About corpid acquisition:

DingTalk managers log in to the background: https://open-dev.dingtalk.com/#/index, copy the corpId below

1.3 Click Permission Management to configure the authorized department and personnel (it is recommended that the authority be selected according to the diagram below, and you can select all employees or some departments or employees)

1.4 Publish the application

Fill in the callback domain name uniformly: https://www.fxiaoke.com/

3. Application authorization (only when the callback address is registered, you can follow this operation)

If the above callback address is registered, you can subscribe to the address book event on the DingTalk app page, the steps are as follows:

3.1 Log in to the DingTalk management background and enter the event subscription page

3.2 The configuration parameters are as follows:

Encrypted aes_key: twki1srsvwm2vaxecwyy2xxllc4r5t0zivt1qropp9s

Signature token: iMY3uFx9DPCc5S17i7Y

Request URL:

https://www.fxiaoke.com/dingtalk/business/appCallBack?appKey=The appkey of the self-built application above

Check the event reference below. Just remember to click the switch, no need to click save

1. Log in to the system

Login to ShareCRM: https://www.fxiaoke.com/pc-login/build/login.html

Log in to DingTalk: https://open-dev.dingtalk.com

2. System Initialization Configuration

2.1 In the "Home" channel of the DingTalk open platform, find the CorpId under the company name, copy and paste the information code to the "Management-System Docking Management-DingTalk Docking-Docking Settings-Application Initialization" in ShareCRM system Corp ID field in the Configuration channel.

2.2 In the "Application Development-Enterprise Internal Development-Small Program-Application Homepage" channel of the DingTalk open platform, copy and paste the information codes of AgentId, AppKey, and AppSecret to the "Management-System Interconnection Management- The Agent ID, App Key, and App Secret fields in DingTalk Docking - Docking Settings - Application Initialization Configuration" channel.

2.3 In the "Application Development-Mobile Access Application-Login-Scan Code Login" channel of the DingTalk open platform, copy and paste the appId and appSecret information codes to the "Management-System Docking Management-DingTalk" in the FunShare system Nail the App Key and App Secret fields in the "Docking-Docking Settings-Mobile Access Application Configuration" channel.

2.4 Find the Client URL in the "Management-System Connection Management-DingTalk Connection-Docking Settings" channel of FunShare. Fill in uniformly: https://www.fxiaoke.com/dingtalk/

3. Account synchronization and binding

3.1 Mode 1: Synchronize only employee accounts and manually bind CRM accounts

Applicable scenario: The enterprise wants to maintain the organizational structure of DingTalk and the CRM organizational structure independently of each other. When DingTalk adds new employees, it needs to manually generate CRM accounts for these employees and bind them.

- In the channel of "Management-System Management-DingTalk-DingTalk-Account Mapping" of FunShare, click the Sync DingTalk employee account button

- Check the DingTalk account that needs to be synchronized, and click Synchronize

- You can view historical synchronization records (time, operator, status, etc.) in the channel "Management-System Connection Management-DingTalk Connection-Synchronization Diary" of Funshare.

3.2 Mode 2: Synchronize organizational structure and automatically create CRM account

Applicable scenario: Enterprises want to keep the CRM organizational structure consistent with DingTalk, and only maintain the organizational structure on DingTalk. When DingTalk adds new employees/departments, the department and employees will be generated synchronously in CRM and automatically bound.

- Click to sync DingTalk employee account

- Enter the department and employee selection page, where the departments and employees authorized by DingTalk are displayed

When initializing the connection, you need to manually select the binding once.

Logical explanation: If Funshare does not have the employee, it will be created automatically. When the department or employee authorized by DingTalk changes, it will rely on the callback event to complete the synchronous change in Funshare. Note that the implementation students need to determine whether the client company has completed the registration of the callback address.

At this point, the docking configuration between Fenxiang Pinke and DingTalk is complete. Is it very simple?

1.1 PC Entrance

1.2 Terminal Entrance

2.1 PC

2.2 Terminal