2022.05.17 update-YIDA product update in May overview

1. This product capability optimization map

We upgraded the basic capabilities of many products in April, focusing on coveringStability,Performance,Functional experienceRelated.

2. Product optimization and update:

2.1 optimization of business association rules

Scenario 1: Non-delayed display of log lists

The validity period when the content of the business rule is displayed in the log list.

Before optimization	After optimization
The display will be delayed. The second time or a few minutes later will appear.	In the log, you can immediately see the executed

Scenario 2: Failed business rules support retry

Failed rules support retry

Before optimization	After optimization
Unable to retry after failure	For failed tasks, the business rule task supports the retry button. After success, the log record of the current rule is automatically updated.

Scenario 3: One-click jump to view the target instance

One-click jump to view the change details of the target instance page

Before optimization	After optimization
Target table result viewing is not supported in Business Association rules.	The target table results cannot be viewed in the business association rules; Automatically jump to the target table-details page-change records to support automatic triggering of related usage descriptions

Scenario 4: log support for unexecuted tasks

Running log support failed execution details

Before optimization	After optimization
After a node in the middle of a multi-business rule group fails, the business rules of subsequent nodes cannot be seen and retry is not supported.	Asynchronous execution status of business rules: In addition to success and failure, add the "not executed" status, reveal the execution sequence number of the rule, and solve the status self-examination during business peak hours. With the retry button, you can rerun the list of failed tasks in batches.

Scenario 5: Job notification anti-disturbance optimization

Job notification-free optimization

Before optimization	After optimization
Too many notifications of invalid failed work lead to excessive interruptions to customers in some scenarios.	Batch notifications caused by system jitter are optimized (after automatic retries are successful) without disturbing customers; At the same time, customers can view the business rule running log independently.

Scenario 6: supports subsequent operations to terminate abnormal tasks

After the task node fails, you can terminate subsequent tasks.

Before optimization	After optimization
After the node in the middle of the multi-business rule group fails, the switch cannot be controlled.	After the node in the middle of the multi-business rule group fails, you can switch to control whether the subsequent rule Group needs to continue to execute (previously, you cannot terminate the subsequent task)

2.2 import/export optimization

Scenario 1: The performance of import/export is greatly improved

Import description:

• 当前状态：The normal form is full and has no version limit. Both the old and new storage applications support it;
• Improved import performance of common forms🔝 32Times(Import 5000 entries as an example)
• Flow chart related scenarios are not overwritten yetFor example, the batch initiation process will continue to be optimized;

Export description:

• 当前状态：Fully published
• Normal/flow chart export performance improved🔝 24Times(The export takes 5000 as an example)

Note:

• Import/Export optimization does not cover 1.0 and 2.0 applications;
• Common forms and Business Association rules are still affected by business association rules, resulting in slow import/export speed.

Scenario 2: import/export solves the problem of high typical import failure rate and inaccurate data

Fix and resolve the following common scenarios:

1. Import failure caused by system architecture jitter/timeout
2. Large data volume batch import some instances due to timeout will fail to import
3. The data imported by users in batches has been deleted due to system architecture jitter/timeout, but there are still problems on the data management page.
4. Fixed data duplication during batch import

2.3 process-related function optimization

Scenario 1: New Configuration mode for process return

Before optimization	After optimization
It takes approval at all levels to approve and return the initiator. For small change points, users want to quickly return to the current approver node but cannot implement it.	Configuration allows process designers to roll back nodes and process efficiencyPromotion90%
重新依次审批：If the process node is A> B> C ,C returns the process to A, and the process will re-flow according to the link of C> A> B> C, each node triggers message notifications and business rules.	从当前节点审批：If the process node is A> B> C and C returns the process to A, the process will flow according to the link of C> A> C, and does not trigger the corresponding message notification and business rules.

Scenario 2: Process View/comment 」

Before optimization	After optimization
🚫Process participants can only view the approval details of their nodes. 🚫Only platform/application administrators have comment permissions 🚫The number of attachments in the comment area is limited to 2. 🚫Comments do not support uploading attachments in ppt format.	✅ 查看及评论权限：Process participants can view the process after the process is initiated, and all participants have the permission to view and submit comments. ✅ 评论中附件数量上限提升：Up to 5 ✅ 新增附件种类：Add support for ppt format based on the original format in the comment area attachment

2.4 YIDA formula optimization

Scenario 1: Optimization of Exist function during flow chart Rollback

The approval flow of flow chart can be revoked and returned. At this time, the data of the form is already stored in the system.

EXIST()Function: checks whether the form data and the database data already exist.

Before optimization	After optimization
The existing detection rule is triggered when flow chart resubmit is revoked or returned.	YIDA will be intelligently detected. If the returned flow chart is resubmitted, the exist detection rule will be automatically skipped.

Scenario 2: When the form is submitted and saved, the formula calculation that has not been run is checked.

Before optimization	After optimization
The running Formula calculation is not detected before the form is saved or submitted.	If a formula calculation is being performed, the user is prompted.

2.5 Integration & automation function optimization

Scenario 1: improve the continuous triggering capability of automation

Multiple forms are configured with automatic update triggers, which support continuous triggering of data linked by three layers.

Before optimization	After optimization
Form A> Form B	Form A> Form B> Form C> form D; Upper limit description: a serial trigger is triggered at most500Stripe integration automation instance

Scenario 2: Integration & automation and business association rules

• Integration & automation and business association rules are both RPA implementations within YIDA.
• As an easier visual upgrade of business association rules, Integration & automation supports more triggering events and data linkage capabilities in addition to business association rules,In the future, it will be the RPA function solution that is suitable to be promoted..
• This optimization of business association rules adds summary information of the Integration & automation function to the form designer, and adds guidance to the creation of links.

Before optimization	After optimization
A form is configured with business association rules 」, At the same time, "Integration & Automation" is configured, and relevant information of "integration & Automation" cannot be seen in the "business association rules" configuration, the execution time sequence cannot be effectively controlled when two types of tasks are triggered.	When the same form is automatically referenced by integration, information can be exchanged. In the future, the same form will not be recommend to participate in the mixed use of two RPA (Business Association rules and Integration & Automation) functions at the same time. Recommend implement relevant requirements through the integration & automation function.

2.6 YIDA openAPI new interface

3 DingTalk open interfaces added to the YIDA open platform

Scenario 1: query all comments of a process

For more information, see:Query comments on YIDA form instances in batches

Scenario 2: query the change records of a process

For more information, see:Obtain approval Records

Scenario 3: perform batch approval tasks

For more information, see:Perform YIDA approval tasks in batches

2.7 upgrade associated form components

1. Associated forms can be assigned values and filled with associated forms, and can be used within formulas/business rules.
2. Data Linkage condition rules, with logical characters greater than and less than for numeric components

Before optimization

After optimization

Data filling, Data Association, and other linkageYou cannot use associated form fields ",You cannot establish an "equal" connection between the associated form component and the text fields of other forms., a text component needs to be added to the same field and filled by the associated form component, which will cause a lot of data redundancy.

✅Enable the associated formData fillingAfter,Set fill conditions, in the current form field, you can select the associated form component of the current form ",Reference the main information fields set by the associated form ✅ Data LinkageComponent support. The conditional rule value field of the current form supports selecting the associated form component of the current form,Reference the main information fields set by the associated form ✅ Within the formulaYou can reference associated form fields (the metadata type of the value is array type) ✅ Business rulesAssociated form fields can be referenced in Through the existing formulaGet ArrayItem/Get ObjectFieldTo directly reference associated form fields

2.8 platform basic capability optimization

Scenario 1: Application page navigation optimization

Before optimization	After optimization
🚫Application page navigation only supports Level 2 🚫The main menu is still displayed if the access status submenu does not have permission.	✅Application page navigation supports level 3 ✅If you do not have permission to access the state submenu, the main menu is linked to hide it.

Scenario 2: delete an attachment to release storage capacity

Before optimization	After optimization
🚫The uploaded attachment will not release the storage capacity after it is deleted.	✅Release storage capacity after attachment deletion Attachment points: Delete attachments directly Delete form/process instance data Delete form Delete an application

Description of real-time attachment storage statistics:

Attachment Upload and attachment deletion are released. Capacity statistics are delayed for about one hour;

Storage capacity release range description:

1. The attachment uploaded after the function is released (2022.5.30) can be deleted to automatically release the storage capacity;
2. Attachments uploaded before the feature release (2022.5.30) are deleted after the feature is released:

1. Deleting an application automatically releases the storage capacity of attachments involved in the application;
2. Delete forms, delete instance data, and directly delete attachments. Release is not supported;

3. Attachments deleted before the release of the function (2022.5.30) cannot be released;

2.9 known bug fixes

修复Integration & automation when the add data node is in use, if a field does not have a value, the bug uniquely identified by the component is passed by default.

修复A bug in which the fields required by the integration & Automation initiate approval node are inconsistent with the configuration of the process initiator node.

修复When the mobile terminal submits flow chart, the system automatically repeats the submitted bug.

修复Single-line text, multi-line text, and detailed address are out of focus to filter spaces before and after, avoiding spaces in fields and data linkage.

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