How to Use Dingtalk Connectors in Yida Scenarios

Related Tags：1.Events DingTalk
2. Dedicated DingTalk Solution

Table of contents
1. The relationship between Yida and the connection platform
2. Use the connector in Yida
3. Use integrated connectors in Yida
4. Q&A

1. The relationship between Yida and the connection platform

The value of interoperability between Yida and the connection platform
Yida is an enterprise low-code application platform, which can help enterprises complete the development of proprietary applications through low-code methods, and help enterprises solve business data problems at low cost. The usage scenarios of Yida are generally information management, such as: project management, travel management, customer management, order management, etc.

Before interoperating with the connection platform:

Customer requirements: After filling out the form in Yida, you can directly connect to Dingding to publish the agency task;
Problems encountered: Yida and Dingding platforms are relatively independent, and data exchange is difficult; code development is required to connect Yida and Dingding;
After connecting with the connection platform:

Through low-code configuration, you can either use the DingTalk connector in Yida, or configure the connection flow operation Yida API in the connector.
image.png
Yida and connection platforms are typical examples of mutual integration and mutual openness. As shown in the figure below, suitable form data source scenarios and process orchestration scenarios should be used to integrate various capabilities of the connectors connecting the platform to realize data exchange.
image.png
Build an integrated connection platform
image.png

Connection flow: In the connection platform, the process of realizing data conversion and synchronization is defined as connection flow, which can be produced in the form of low-code, or can be generated in a system integration way like Yida.
In the process of using the connection platform connector, behind each invocation relationship is a connection flow. When using the DingTalk capability, Yida will exchange data with DingTalk through the connection stream to complete its own business.
Fitting connectors in the connection platform
image.png

Connector: A connector is a collection of trigger events and execution actions. With the help of the rich connectors in the connector market, the interconnection between heterogeneous systems in an enterprise can be realized.
Yida registers its own development capabilities as connectors, uses the connection platform to connect streams, and combines other connectors to achieve connectivity with Yida in a low-code way.

2. Use the connector in Yida

Fit: Integration & Automation
Operation path: Yida - Integration & Automation - New Integration & Automation

Trigger type selection:

Form event trigger: the specified form or process event trigger;
Timing trigger: The trigger process is cyclically triggered according to the set time period;
Application event triggering: One-party and three-party application events provided by the connection platform connector are used as triggering conditions for process execution.
Typical Scenario 1: Using the To-Do Connector in the Connectivity Platform in Yida
The user fills in the form in Yida, and automatically creates a DingTalk to-do message for the designated member in DingTalk, and the executor clicks on the to-do to view the form details. Launch a powerful message reminder, so that everything is settled and everything has an echo.

Steps
Create an app

new form

To design the form:

New Integration & Automation

Select the trigger type as: form event trigger;

Process Design:

Create form event trigger;
Add connectors and configure actions;
image.png
Save and publish integrations & automation;
Publish the form to the public platform and view the form effect
Create a to-do form in Yida, fill it out and click submit

Receive to-do information in DingTalk client

At this point, the communication between Yida Form and Dingding To-do is completed.

Typical scenario 2: Use the message notification connector in the connection platform in Yida
When a user completes a task on Yida, or finds that a certain indicator has been reached through data analysis, and needs to send a group message to notify group members, the Yida connector can be used to send a message to the DingTalk group.

Steps
Create an App: Group Chat

new form

To design the form:

Create integrations & automations that use the newly created form as a trigger

Process Design:

Create form event trigger;
Add connectors and configure actions;
image.png
Add new data and configure new data;
image.png
After the configuration is complete, save and publish the integration & automation;
Fill out the form to see the effect
Create a group chat form "Create a group chat and send a group message" and submit it. You can see the newly created group chat in the DingTalk client, and the creation is successful.
Create a form to send a message to the newly created group chat

Create integrations & automations that use the newly created form as a trigger

Process Design:

Create form event triggers, add connectors, select connector actions, and configure actions;

Save and publish integrations & automations.
Fill in the form and submit it, and receive the message in the Yida form in the DingTalk client message group "Create a group chat and send a group message", and the message is sent successfully.
Typical scenario 3: Use the address book connector in the connection platform to trigger the execution of the Yida integration flow in Yida
When the employees of the enterprise change, trigger the execution of suitable business processes to complete automated operations such as onboarding or resignation.

Steps
Use a built travel schedule
Create integrations & automations, select application events to trigger

Process Design:

Application event trigger configuration: trigger application: select address book; trigger action: internal user change;
image.png
Delete connectors and add new data;
image.png
Save and publish after the configuration is complete.
View Results
If you change the information of an employee in the DingTalk address book, you will receive a changed message on the data management page in the Yida business trip data form.
image.png

3. Use integrated connectors in Yida
basic concepts

Integrated connector
An integrated connector is a type of connector with an integrated gateway, an integrated execution action or a trigger. It is connected to the external system through the integrated gateway, and the execution action and trigger can be linked with the external system.

Integrated Gateway
The integration gateway is a gateway provided by the connection platform and exchanged with the external data platform in a specific data format. It can require the external platform to convert the complex data format and register the connector in the unique format of the connection platform to simplify the input and output parameters of the connector. .
image.png

Using the integrated connector in Yida Premium
Choose an integrated connector
image.png
Execute actions linked to approval forms
image.png

Configuration instructions

The first step, select the connector action: you can search by entering the name or click to select to find the desired connector to perform the action;
The second step, select the process form: first, you need to select the approval application in DingTalk, (as in the OA approval in the above figure), this application needs to be created by the user in DingTalk; then you need to select the appropriate form (as in the above figure) overtime approval test);
The third step is to configure the action: that is, to bind the Yida form to the DingTalk application by clicking.
Typical scenario: use the advanced functions of the OA approval connector in Yida
Traditional connectors have fixed input and output parameters. However, for platforms such as OA approval, the form is built by the user, and the operation of the form will vary according to the content of the build.
After the advanced function is enabled, it will support the connection with the advanced function of the OA approval connector.
In Yida, you can select a form built under a platform such as OA approval to connect.
Scenario 1: OA approval form data is synchronized to Yida
Steps
Select a form in Dingding OA approval - item collection
image.png
According to the content of the DingTalk form, create a corresponding form in Yida Premium Edition

Create Integration & Automation

Process Design

Application event trigger:

connector:approval;
Trigger action: instance passed (advanced version);
Application name: OA approval;
Process form: item collection;
Delete connectors and add new data;

After the configuration is complete, save and publish.
View Results
Submit an item requisition form in DingTalk OA approval, and you will receive a new message on the data management page in the Item Requisition Record Form, which is the item requisition form submitted in DingTalk.



Scenario 2: It is advisable to synchronize form data to DingTalk OA for approval
Steps
Create a form in Yida
image.png
Create integration & automation and configure connection flow, save and publish when done
image.png
image.png
View the result: After Yida fills in the form and submits it, a new Yida form will be added to the DingTalk OA approval data.
image.png
4. Q&A
Q: Do we have to use DingTalk Professional Edition to use the connector?
A: First of all, this is not required, because the connector itself is open to everyone on the connection platform. But people who use connectors may be in a variety of products, such as approval and Yida. The professional version needs to be opened in the approval, because the function of the integrated connector in the approval can only be used after the professional version is opened. It's the same in Na Yida, but in Yida, he has a number limit. Then it will have a higher or higher degree of integrated connectors that can be used with the enhanced version.

Q: Can Yida update this form after obtaining the connector data?
A: It is possible to update this form, but this operation may require, for example, to associate the data of the form; if the connector returns, you can use this data to update the corresponding form.

Q: How to integrate the connector for an approval process initiated by calling the approval interface of OA
A: It may be different from what everyone thinks, because if you use connectors in approval, most of them are when the form is created or in the process. If it is initiated through the interface, it is estimated that it can only be in the process.

Q: If I am a professional user, will there be any connector discounts?
A: For the professional version user, in the first approval, he has opened up the connector of our connection platform, that is, the connector of the connection platform can be used in the approval. You can also define a new connector in the connection platform yourself, and then use it in the approval. Many customers can obtain the data of their own system or the data of the third-party system through the connector when creating a new form.

Q: How can Dingding's OA get a piece of data from Yida?
A: At present, the data of a form is relatively simple with the connector function provided by Yitao. The data format it returns is also not explicitly parsed. It may still be difficult for now. We are also advancing this matter. If we have a related progress in the follow-up, we will also push some updated news to you through the service window of Dingding or the official website of the open platform and the official website of the connector.

Q: Can I develop some connectors on the connection platform and use them in Yida?
A: Because Yida itself is an independent product, our connection platform is also an independent product, and there is cooperation between the two products. And then for his own product body it screened some connectors provided by our connection platform
For example, if there are some connectors developed by that service provider or some developers on the shelves, maybe after they are on the shelves, we can communicate with the Yida side to see if this connector can be used by Yida. This connector can be released on the other side.

Q: Is it possible to connect with Yida by connecting some predetermined data in the DingTalk smart conference room now?
A: First of all, the official connection lines are very rich and many of them are converted from the interfaces we have opened. Therefore, the specific function may be provided by the business plan of the corresponding connector. If there is a smart conference room
It would be fine if there was an interface to get such predetermined data. But for example, you need some interface input parameters to obtain the reservation data of the smart conference room. In this case, you may have to build a form yourself to use it with the connection.

Q: Can DingTalk currently obtain a piece of data from Yida?
A: Yes. But it can only be initiated by Yida. That is, in Yida integrated automation, we can call some of our official execution actions, that is, the connector to transmit his data. But at present, the connector provided by Yida itself is relatively simple in function and cannot fully parse its data structure. Therefore, for example, we want to obtain some data expressed by Yida in the approval, which is still not possible at present. So we are also recommending this thing to continuously improve the richness of connectors.

Q: Can the data of Yida be put in DingTalk OA approval?
A: This doesn't seem to work, because the two are independent products, and there is no way to put the appropriate form in the past. But there is a demonstration in the video just now, you can convert a form that should be taken into an approval process, which is possible. In fact, a piece of data at the bottom of it can be opened up, but there is currently no way to access it. After the deep integration of the exclusive version, some data formats have been approved and opened by Yida. Yida, for example, in his process, such a function can be completed by initiating approval in this way. It's like implementing simple such fit and approval activities. Of course, Yida itself can also receive the event that the approval form is completed.
It is also possible to drop this data.

Q: Can I make a suitable data application into a connector and then make a call to Dingding?
A: Yes, this is completely possible. At present, we are officially recommending these capabilities, that is, we do it ourselves.
If there are developers who can implement this function themselves, they can also be put on the shelves as connectors, and it is also possible to put them on the shelves.

Q: We have integrated a connector to connect the platform in Yida, so can we just use it for some other three-party systems?
A: Yida and the connection platform are in a cooperative relationship. Yida integrates the connectors under our connection platform and conducts screening. For such a model, we plan to open the connectors under our platform to the third party in the future. There is also, for example, the enterprise itself to carry out the integration. In this case, the enterprise or the third party can call the connector provided by our connection platform.

Q: Can an approval process that has been initiated still go to the connector?
A: Certainly not in the process. Because of the version of the approval form we did at the time, its process was fixed. It's the one that was already saved at that time. But for example, if you want to add a connector later, the newly initiated process can go through the connector.

Q: Yida made a bench with an ID card picture on it. How to update the ID card information in this list (9 minutes and 17 seconds)
A: There is a scene of a customer who says that he has an ID card picture in the form. For example, can he destroy it after he has been identified. Destroy come back and update that connection is In this way, you call the interface to identify, and after identifying the ID card, you will also identify the ID card information. If he returns synchronously, then the current form itself can update the identity information in that form, which is no problem. There is another kind of approval, for example, in the approval process, some approval processes can add some interface-type interactions identified by our ID card. If there is a return, the form of the current process can also be updated. Maybe for example, if you are xx, for example, I will identify the ID card, and after a while, the interface will be destroyed, saying that the ID card is recognized and then update this may have to develop it by yourself. Because in this process, if the data is actually obtained synchronously, there is no way to update the form.

Q: Can we bind the delete permission of a basic form
A: This is actually possible, but it needs to be specific. For example, which data I delete may need to provide the ID of the data, then the connector itself will not remember the data, and you may need to try your own actions.

Q: Can I use DingTalk OA approval by making Yidai application a connector for DingTalk OA approval?
A: This is possible. It is necessary to combine some open interfaces. Then, if you make a connector and register it on DingTalk, you must also provide a public network htv address. For the development of the related connector, everyone who has documentation on the development platform can take a look. Take that Yida as an API, do some simple data conversion, and then convert it into the format of the connection platform. Then register on the connection platform to make a connector. The principle is relatively simple.

Q: Trigger connector when empty key loses focus
A: In fact, we are also communicating with the approval side. We also want to add some connection points of some connectors to trigger in some events. Don't worry about this. We all have arrangements for iterative optimization. We will have some iterations and some optimizations for these. If we make a related update in the future, we will also notify you through a service window of the developer, and then look at the background. At that time, we will also hold some new training camps and live broadcast events to give you some explanations.

Q: How to make Yipai a connector
A: As far as the interface domain name is concerned, because the interface you want to provide to the connector has to be developed by yourself.
This Yida will not be provided. This is to ask you to package the Yida interface.