Agent Center

The agent center can set a designated person to undertake the approval of your process within the validity period. The resignation agent must contact the platform administrator. When you set up an agent, the immediate supervisor can set it on behalf of the subordinate.

Instructions

The agent is also applicable to the previous process, but the agent flag is not displayed in the process instance.

Usage scenarios

In our daily office, there are often cases where approvers ask for leave or fail to process approval forms in time, resulting in delays in business operation. This YIDA upgrade provides agent capabilities, you can assist in the approval process when the approver takes leave or leave.

Description:

All employees in the organization can set up agents. The supervisor can establish agents for themselves and subordinates. The resignation agent only supportsPlatform administratorIdentity settings.

Set agent

1. Log on to the YIDA workbench.
2. Click in the upper-right cornerTask Center
   
   Button, clickAgent Center.

3. ClickAdd agent, and then set in the pop-up dialog boxAgent,AgentAndAgent time, clickOK.

Description:

Please select the approval agent carefully, and the agent will undertake your process approval within the validity period after the setting is successful. After the agency takes effect, you still need to be responsible for the approval results. Please do a good job handover and risk assessment in advance to avoid various related risks in the agency.

Instructions

Optional whether the proxy task notifies the delegate.

Resignation settings

When the approver leaves, you can set the agent of the resigned person with one click.If the resignation has a historical approval task, the system will automatically set an agent relationship for the resignation on the day. The priority of the agent's effective is:

The specified New Agent>Direct Supervisor>Department head>YIDA platform administrator>DingTalk organization administrator.

Description:

The proxy relationship is not to transfer the approval task, but to allow the agent to have relevant approval permissions.

• When leaving the company, the original common agency relationship will be revoked and the resignation agency relationship will be automatically generated.
• The dedicated version can perform secondary editing of proxy tasks.

Proxy Record

Agent records are in the following four states:

• To take effect
• Proxy
• Expired
• Revoked

Note: You can only revoke instances in the proxy center to take effect and delete proxy instances.

FAQ

Q: Why didn't the agent approval form be automatically transferred?

If the approver cannot continue to perform his duties due to resignation, YIDA will be automatically transferred to the direct supervisor of the approver who has resigned. If the supervisor does not set the situation, it will be automatically transferred to the platform administrator.

Instructions

When the approval task is transferred to the platform administrator, it is transferred to the first person in the platform administrator list. YIDA will optimize this feature in subsequent versions, and add the default distribution to the New manually added platform administrator instead of the DingTalk master and sub-administrators who manage background synchronization from DingTalk to reduce interruptions.

Q: Can I modify the wrong proxy time?

Currently, you cannot modify the created proxy instance. If the information is incorrect, we recommend that you cancel the re-creation.

Q: What is the allocation logic of agents?

The allocation logic of the agent is as follows:

• Automatic transfer to direct supervisor: the system immediately identifies the resignation status of the approver and transfers the tasks to be approved to the direct supervisor of the resignation approver according to the established rules.
• Automatically transferred to the platform administrator: if the direct supervisor of the resignation Approver is not explicitly specified in the organizational structure of DingTalk, the system will start the standby scheme. In this case, the resignation task to be approved will not stay in the unattended state, but will be automatically forwarded to the platform administrator by the system.