Third party service approver

1. What is the third party service approver

We can obtain the employee ID from the third-party system to match the employee ID in the DingTalk address book. If the employee ID is successfully matched, it can be approved as an approver.

Applicable scenarios: for some enterprises with their own service systems, they want to obtain personnel information from their own systems and act as approvers in YIDA.

2. How to configure third-party service approver

Note: to use a third-party service to obtain the approver, first check whether you have registered your callback service on YIDA. You can view it through platform management> service registration, if you have not registered, register the service you want to call first. For more information about the registration process, seeService registration.

In the manual node of the YIDA process, you can use a third-party service to dynamically obtain the approvers of the approval node.

Procedure:Select human nodes> Basic Settings> approver rules> Other Rules> third-party services, as shown in the following figure:

Set approver rules

Attention

• The format of the acquirer must be as follows:

[
  "工号1",
  "工号2"
]

Note: If some nodes do not want to set approvers, the returned parameters can return null values and directly return []

Pay special attention:

When using this function, if you need to take the value of a component in the form as the approver, the placeholder format used in parameter configuration is as follows:# The id of the form component.

For example:

In the following process, the first-level approver specifies a person, and the second-level approver needs to dynamically obtain the parameter values in the form.

Then, the Http service call takes the placeholder format of the form variable as# The id of the form component, so that the value filled in by the component in the form can be obtained, the following example directly configures the value of a Member component as a parameter. After the configuration is completed, the selected personnel in the Member component can be used as approvers. As shown in the following figure:

If the callback interface is an HTTP interface, the requirements for writing the interface are as follows:

• HTTP Method is POST
• The request parameters are placed in @ RequestBody.

• uuid is a system keyword and cannot be used.
• If SHA256 signature key is used during service registration, the callback parameter :__ hmacSha256

• md5 is the signature method added to the service callback by default. If no key is set during service registration, the default key signature will be used by our system. If a key is set, the signature is signed with the set key. The callback parameter is sign.

You can refer to the following simple sample callback interfaces written in Java:

@RequestMapping(value = "/callback",method = RequestMethod.POST)
@ResponseBody
public List<String> callback(@RequestBody CallbackParam callbackParam) {
  // 返回值格式：["工号1","工号2"]，如果返回空，直接返回null
  List<String> result = new ArrayList<>();
  // do something
  return result;
}

YIDA in order to better optimize the content and quality of YIDA user manual, it takes you 3-5 minutes to fill in the document feedback questionnaire. The document feedback questionnaire is submitted anonymously, and the questionnaire information is only used for YIDA document experience feedback collection. Thank you for your support for YIDA!

Click this link to fill in the questionnaire

-------------------- Get the latest information YIDA, welcome to follow US--------------------