2024.05.20 version update-approval process capability upgrade
Capability release
- Process return:Custom process return range
- CC settings:Support the initiator to select a CC
- Integration automation:Add system fields such as process participants.
- Automatic deduplication of approval:Optimize the automatic deduplication function when the process is returned.
- Complex process expansion:The maximum number of process nodes is expanded. (Exclusive version directional gray scale)
The following is a detailed update description
Process capability upgrade
Process return: Customize the scope of process return
Instructions
- All paid versions are supported.
Before | After |
Process approval does not have the ability to select the return of process nodes. When you approve the return configuration, you can only select from the list of all nodes and cannot control the selection range. | In the return operation of the approval node, you can select the following three return range configurations to flexibly control the return conditions;
   |
Process return: optimize the automatic deduplication function for approval
Instructions
- All paid versions support
Before | After |
Take the financial approver as an example. If the amount is incorrect during the approval, it needs to be returned to a previous approval node. After the data is modified and resubmitted, because the automatic deduplication process is enabled, the approver of the intermediate environment will directly pass the approval without secondary confirmation, resulting in the failure of the business approval purpose.  | If automatic deduplication is enabled and the process is returned to the previous approval node for approval again, the automatic deduplication logic will be downgraded. The intermediate approvers need to approve and confirm the process twice.  |
CC settings: supports Initiator SelectionCC sender
Instructions
- All paid versions support
Before | After |
The CC of YIDA can only be configured in advance in the process design background. The initiator cannot dynamically select the specified CC sender (only the approver can select it by himself).  | The process initiator can dynamically select a specified CC person for business CC when the process is initiated according to business requirements.  |
Integration automation: add process participants to system Fields
Instructions
- All paid versions support
Before | After |
In integration automation, the system variable fields are not rich enough, resulting in business automation unable to remind key process personnel.  | When a variety of business events such as business comments, business data submission, business data editing, and business data deletion are triggered, you can selectively notify the approvers, CC senders, and executors involved in the process. |
Complex process expansion:Maximum number of process nodes
Instructions
- Supported version: Exclusive version
- If there are too many process approval nodes or each node role is a large number of process participants, there is a certain probability that the page opens slowly or times out. In this case, you can configure Zygote process, optimize conditional branches and parallel nodes to try to solve the problem.
Before | After |
The YIDA simple process designer can support up to 100 design nodes. For complex business scenarios, the number of nodes is insufficient.  | The number of process designer nodes has doubled, and the number of dedicated YIDA has increased to 150 nodes, making business process orchestration more free.  |