2021.09.14 update-Integration & Automation-connector
1. Overall function introduction
The logic orchestration function has been upgraded as a whole, and DingTalk connectors have been connected at the same time, DingTalk official applications, DingTalk Ecological Applications, and lightweight access YIDA of enterprise-owned systems, YIDA applications are naturally interconnected.
- Data interconnection between YIDA forms is easily realized. Through the configuration and orchestration of data operation nodes, business personnel no longer need to write advanced functions and codes.
- YIDA access DingTalk one-party connectors, including work notifications, group notifications, to-do tasks, contacts, schedules, calendars, attendance, intelligent personnel, NISSIN-month closing (manufacturing), etc., to achieve task processing, complex scenarios of message sending.
- Support enterprises to develop custom connectors,DingTalk YIDA resource integration, data transmission, and business connection with dingecological applications and other third-party applications.
版本权益
Function | Experience Edition | Standard edition | Vip version |
Integration & Automation | 1 (per application) | 5 (per application) | Unlimited |
Custom connector | 1 (upper limit within the organization) | 5 (upper limit within the organization) | Unlimited |
Process node use connector | 1 (per application) | 1 (per application) | Unlimited |
Note:
Connector nodes can be used in the approval process, with unlimited VIP version;
Each application of Experience edition and standard edition only allows one flow chart to use connectors in the process node. After the first flow chart has configured connectors, the second flow chart also configures connectors in the process node, click process-an error will be reported when publishing the process.
2. Business function demonstration
3. Integration & Automation entry
3.1 Create form event triggering process
- The specified form or process event is triggered.
3.2 Create application event triggering process
- The specified DingTalk one-party, ecological, and three-party application events are triggered, for example, when a new member is added to the address book
3.3 Process Management
- Manage created process events, quickly start, stop, copy, and view running logs, and edit and modify them.
3.4 process start and stop
- Enable or close the event process freely. The enabled process is in the effective state and the closed process is not in the effective state.
3.5 process replication
- After creating an event trigger process, you can quickly copy an event process with the same rule through the Copy button.
3.6 process operation records
- Run logs can check whether the current event process is successfully triggered, and can be quickly filtered through execution status and date.
4. Process Orchestration designer
4.1 designer panel area features
It mainly involves the following functions. For more information, click the corresponding function to view details:
4.2 trigger node configuration
- Currently, form events or application events are supported. Scheduled triggers and webhook triggers focus on product optimization.
Form event triggering
- Trigger events can trigger subsequent node rules by creating the current form, editing it, deleting it, and commenting it successfully.
- Data filtering is divided into all data and filtered by conditions. Filtering by conditions is based on the fields of the current form.
Application event triggering
- You can select an official application or create a new connector to trigger it.
4.3 action node configuration
- The approval flow nodes are more abundant, including connectors, adding data, updating data, obtaining a single piece of data, obtaining multiple pieces of data, deleting data, initiating approval, message notification, and Groovy nodes.
4.4 branch
- Conditional Branch(Implement different business rules under different conditions),Parallel branch(Multiple rules are executed simultaneously if multiple conditions are met)
5. Node introduction
5.1 connector
5.1.1 one-party connector (trigger)
- Currently, only DingTalk are provided when the event is triggered.Contacts 」The trigger action of the application. Other connector applications are not online to trigger the action.
5.1.2 one-party connector (execution)
Currently, the following are available.10DingTalk application connectors:
(1) to-do tasks
- After triggering, you can create a DingTalk to-do task.
(2) schedule
- Trigger New Schedule
(3) message
- Send a message to the enterprise group. This node function needs to be used together with the scene Group node.
(4) scene Group
- Trigger the creation of a new scene Group
(5) video conference
- Create a video conference
(6) Attendance
- Trigger notification approval
(7) address book
- Triggers DingTalk contacts to update, create, and delete user information
(8) intelligent personnel
- Supports adding employee information after triggering an event.
(9) NISSIN
- It is suitable for the industrial business scenario of piece-rate reporting in manufacturing industry.
(10) DingTalk Sports
- Get DingTalk sports department and personal sports data
5.1.3 custom connector
Use YIDA connector factory to customize connection to self-built systems or third-party application systems
Path:YIDA Workbench> Settings> connector factory
For more information, seeCreate a connector
5.2 Data nodes
It mainly realizes different execution effects on data. Currently, there are the following nodes:
5.2.1 add data
When a form event is triggered or an application event is triggered, one or more pieces of data can be added to the target Table. Currently, the new method isAdd to form, inAdd a subtable2 Types
After you select Add method and target table, a new or multiple data and field settings will pop up. By default, select Add one data. You need to add multiple data. You need to manually switch
5.2.2 update data
After a form event is triggered or an application event is triggered, the data of one or more target tables can be updated. If no data is obtained, you can skip this node or add a new data.
Note:
- To update a data node, you need to configure the get data node. Otherwise, no option appears.
- Only common forms can be selected for obtaining data node flow chart, but flow chart is not supported. It is already in the plan and will pay attention to subsequent product optimization.
5.2.3 obtain a single piece of data
- Obtain a single piece of data in the target table, and then process the data (update, delete)
Method:Obtain from a form, obtain from a data node, and obtain from an associated form
5.2.4 obtain multiple pieces of data
- Obtain multiple pieces of data in the target table in batches, and then process the data (update, delete)
5.2.5 delete data
- When you need to delete data from a form in a business scenario, you must first obtain the data from the data node and then configure the delete data node to achieve the effect.
5.3 branch nodes
- Branch nodes can implement different conditions to execute the following different rule configurations, meet multiple conditions at the same time to execute rule configurations at the same time
5.3.1 Conditional Branch
- Conditional branches have priority. Only the branch with the highest priority is executed.
5.3.2 parallel branches
- There is no priority between parallel branches. Branches that meet the conditions will be executed.
5.3.3 configuration method
(1) conditional rules
- It mainly uses components in the form and system default fields as conditional branches.
- The following components support conditional branching:The ID of the organization to which the form event trigger belongs, single-line text, multi-line text, single choice, check, drop-down single choice, drop-down check, value, date, attachment, member, Department
(2) formula
- To edit the field of the current form as a conditional branch, useLogical functionThe public function in can judgeWhether the condition is true,An example is as follows:
5.4 Artificial nodes
- Main pointsInitiate approval,Message notificationThese two types of execution rules
5.4.1 initiate approval
- After the form event is triggered, you can initiate a data entry for the target flow table. You can only select flow chart. Ordinary forms do not support it.
- The initiated flow chart field data values can be set to fixed values, fields, and formulas.
- The initiator can specify a member or a member component in the form (the initiator is the person who selects the member component when submitting)
5.4.2 message notification
- After the event is triggered, a message is sent to the corresponding person. You can specify members, roles, and variables to notify member components in the form. You cannot send message notifications to group chat.
5.5 developer nodes
5.5.1 Groovy operation instructions
(1)Groovy entry
(2)Groovy configuration panel
(3) parameter initialization
The input object name can be set freely. Assignment can be divided into two types:
Value: static data, you can directly set
Field: Select the variable object generated in the node before Groovy
※ Note that the initialization values here are of string type, that is, param1 = "100". If you want to convert them to int in subsequent processing, you must convert them yourself.
(4) code block writing
The code block is a Groovy script, which can be understood as a java method with only basic jdk.
※ Note: The return value must use outputs. Parameter meaning: outputs.add(# Variable Description#,# variable name#,# Variable value#)
(5) testing
Note: you must click test to check whether the code is normal and generate a variable description for subsequent nodes.
Because variables cannot be used for testing, you need to set a static test value for the variable value before testing. For example, set a test value of 20 for param2 first, and then click test, the output object parameter list is generated. If the output object is running normally, the code is correct.
(6) save
Modify the value of the variable back to the variable before saving, and then click save
6. Connector factory
It is used to connect user-defined interfaces and can support some authentication functions. More authentication support will be added gradually in the future.
6.1 entrance
(1) the connector factory entrance is in platform management, click
(2) Click Connector factory to enter the custom connector configuration interface.
6.2 New connector
6.2.1 create
Click Create connector. The create connector configuration page appears on the right. Enter a custom connector name and click OK;
6.2.2 basic configuration information
Configure basic information. Click 「Next Step"Enter the next stage, or click 「Save」 Return to the current editing State next time
Host:The host address of the request does not need to contain the http:// or https:// protocol header, and does not need the end of the // protocol;
Base URL:You can configure the basic prefix URL in the request address. If not, you can directly fill in "/".
Schema:Protocol Type
Connector online name:The name of the custom connector.
Icon Image address:The icon displayed by the connector. If you do not specify it, the default icon will be displayed.
Connector introduction:Basic Introduction of connectors
6.2.3 configure security verification information
The following figure shows three types of authentication:
(1) no authentication:It is an interface that is called directly without any authentication information. It is usually used to access some public interfaces.
(2) Basic authentication:BasicHTTPAuthorizationThe request header contains the credentials used by the server to verify the identity of the user proxy. For exampleAuthorization: Basic YWxhZGRpbjpvcGVuc2VzYW1l Base64 encoded account password information
You only need to configure the prompt label of the account password to prompt the user to know what to fill in the registration authentication information.
(3)api key:That is, apiKey authentication method,It is valid for a long time (please keep it properly). Visitors create a secret key in the system to be accessed. Developers can directly call public APIs that support such authentication through this credential.
Parameter label: prompts when Configuring authentication information
Parameter name: the name of the apiKey required by the system.
Parameter location: you can add authentication information to the query parameter or header, and select it according to the request system needs.
6.2.4 configuration function operation definition
Click Add to add an action configuration
Unique Identifier: identify different operations
Name: Name
Description: content description, optional
Request:
Request method: Select according to the http interface type, as shown in the figure.
URL: request link
Path: indicates the variable with braces configured in the URL, such as {pathParam}, where pathParam is used as the variable name.
Query: indicates the request parameter, which usually refers to the question mark of the URL? For additional parameters, click the plus sign to add
Header: the required parameter in the header, which is currently statically configured.
Body: if it is a POST situation, there may be a body field, which needs to be filled in when using it.
Response
Body: You can post an expected json result, and parse the field format when using it.
6.3 authentication configuration
All custom connectors need to create corresponding request authentication schemes, even 「No authentication」 You also need to create a
(1) Create
(2) select the connector you need to configure, and the content that needs authentication will be automatically displayed according to your configuration. After filling in, click create 」
6.4 test connector
(1) after the configuration is completed, the following figure will appear. You can start the test.
(3) select the authentication used and configure the test parameters
(4) click test operation. The expected result is that the configuration is successful.
6.5 connector use
(1) in the process canvas, select the connector node and click next 」
(2) select the authentication template, select the action to be executed, and click next 」
(3) select the parameter configuration to be entered in the execution action. Like other nodes, it supports input such as value, field, and formula. Click save.
7. FAQ
7.1 can cross-form replication trigger events?
- Only trigger events triggered by replication within the same form are supported, and cross-form replication is not supported.
-------------------- Get the latest information YIDA, welcome to follow US--------------------
