2024.03.28 update-exclusive YIDA product upgrade

Main feature upgrade summary

• Work handover: quickly transfer the process approval task.
• Agent Center: upgrade the secondary editing to optimize the default agent.
• Process upgrade: the process approver can check the status of read and unread.
• Form comments: you can delete comments.
• Platform statistics: data volume and attachment volume are no longer included in statistics for dedicated storage.
• Internationalization: DingTalk Workbench YIDA application name supports English.
• Priority experience: the maximum performance of forms and integration automation is improved.
• Enterprise Performance: The latest authorization time is added to the authorization details.

Dedicated open interface

• OpenAPI: integrate automated O & M logs.

Dedicated Cluster Upgrade

• Version Management and Task Center support the synchronization of viewing, Task Center, and approval tasks that I create.

The following is a detailed update description

Work handover: quickly transfer process approval tasks

It is used to transfer the responsibilities of the current position and the matters in charge to the successor in batches when the staff's job changes.

Step 1: query the in-transit approval task of a designated person
Step 2: transfer to task successors in batches and notify task reminders

Agent Center: upgrade the secondary editing to optimize the default agent

• The agent task of the resigned personnel is optimized to support secondary editing and adjustment of the agent.
• If the resignation has a historical approval task, the system will automatically set an agent relationship for the resignation on the day of departure. The order of the agent's effective is as follows: the specified new agent> direct supervisor> department supervisor> YIDA platform administrator> DingTalk organization administrator. This time, the notification policy for the platform administrator is optimized. Notify manually added YIDA platform administrators (platform administrators responsible for low-code services, Figure 4 Green Label type), try to avoid DingTalk primary administrators and sub-administrators (The Blue Label type in Figure 4 is that DingTalk administrators automatically synchronize to YIDA platform administrators)
• Note: the proxy relationship is not to transfer the approval task, but to allow the agent to have relevant approval permissions.

Before	After
The historical task for the resigned personnel cannot be transferred. After the agency relationship takes effect, it cannot be edited twice and can only be revoked. Figure 1	The historical task of the resigned personnel supports multiple reassignments and flexibly adjusts the task execution agent. Figure 2
Resignation settings: A platform administrator is randomly selected from the red box. By default, the DingTalk administrator becomes the YIDA platform administrator (blue), and the YIDA platform administrator (green) is manually added. Figure 3	Resignation settings: Only one platform administrator is randomly selected from the platform administrator with the green logo to avoid disturbing the DingTalk master and child administrators. Figure 4

Note: This feature is supported for all paid versions.

Process upgrade: add a node to view the status (read/unread)

Process participants can view the review status of the current approver to facilitate timely understanding of the approval progress.

Before	After
The approval node has not been processed for a long time and cannot reflect the reading status. The CC node has not been viewed for a long time and cannot reflect the reading status.	If the approval node is not processed in time, process participants can view the review status of the current approver, which is convenient. The CC node that has been reached can display the read and unread status, but cannot display the read status.

Instructions

• The completed process displays the read unread status within one year at most.
• If the process is not completed, the review status will always be displayed.
• All applicable versions support this feature.

Form comment: delete comments

The comments on the form and flow chart details page can be deleted and cannot be recovered after confirmation of deletion. The behavior of deleting comments is automatically recorded in the enterprise log operation record.

Before	After
Commented content can be replied but cannot be deleted.	In addition to supporting replies to existing comments, comments are added to support deletion. After confirmation of deletion, the content cannot be recovered. The behavior of deleting comments is automatically recorded in the enterprise log operation record.

Description:

All paid versions support the comment deletion function, and enterprise log records are only supported by YIDA.

Platform statistics: data volume and attachment volume are no longer included in statistics for dedicated storage

The data recording logic in platform management will only count the amount of data on the cloud, and the data consumption of exclusive storage will be automatically removed from the cloud, helping enterprises save costs.

Before	After
After the application has enabled dedicated storage, neither data volume nor attachment statistics will be displayed.

Description

Since non-dedicated YIDA does not involve independent dedicated storage scenarios, no change occurs.

If the application has been exclusively stored, the business data volume of enterprise performance will not participate in detailed statistics and analysis.

Internationalization: DingTalk Workbench YIDA application name support English

The DingTalk application name of the YIDA Workbench supports English. When the DingTalk client switches to the English environment, the YIDA application name automatically matches the multi-language content.

Before	After
The application name is configured with an English title. The correct English application title cannot be displayed on the DingTalk workbench.	According to the multi-language title set by the application, the current DingTalk language environment can be automatically matched within DingTalk terminals, and the English title of the application can be automatically displayed.

Description

• The history of applications that have been published to the Workbench needs to be removed and then released to take effect.
• The newly released application takes effect immediately.

Priority experience: increase the maximum performance of forms and integration automation

Dedicated YIDA (non-dedicated storage) has prioritized performance improvement in three scenarios:Form data,Process Data,Integration automation and business rulesSpeed up the product. The performance specifications of other versions will be gradually upgraded in the future. Dedicated storage is continuously optimized.

	Before	After
Common form (Batch data import)	Import 5,000 pieces of data at a time	10-fold increase to 50000 pieces of data
Flow chart (Batch launch)	Import 1,000 pieces of data at a time	10-fold increase to 10000 pieces of data
Integrate automation and business rules (Data acquisition, update, and deletion)	Process 100 pieces of data at a time	20-fold increase to 2,000 pieces of data Instructions Update node only forNode update", raise the upper limit,Direct updateThe method remains unchanged. If you obtain 2000 pieces of data by obtaining a data node and insert the data into a subform by adding a node, you will be limited to 500 pieces of data in the subform and only 500 pieces can be written.

Enterprise Performance: authorization details add the latest authorization time

The latest authorization time is added to the authorization details. Administrators can manage the allocation of authorized accounts more scientifically.

Before	After
The authorization is obviously only the last access time (the initial access time is the authorization time)	The latest authorization time is added to facilitate administrators to manage the allocation of authorized accounts more scientifically. Data can be quickly sorted and exported in Excel.

Dedicated Cluster Upgrade

Version Management and Task Center support the synchronization of view, Task Center, and approval tasks I created.

[Navigation optimization] global navigation logo for easy viewing

Development environment: it is used for application development and construction, and provides a complete data testing and acceptance environment, which is convenient for application developers to build applications.

Formal environment: it is used to access application products in cluster mode, access and run applications, and data storage of applications will be executed and saved in the privatized environment of enterprises.

Before	After
1. The multi-version environment that should be built cannot be visually viewed in the formal environment. 2. Unable to determine whether the current access page is in private cluster mode	1. [easy to view] you can visually view the build version of the current application. 2. [convenient switching] the application navigation will add an environment identifier to flexibly switch to the development/formal environment.

[Task Center] compatible with application physical column storage, adding queryable types

Compatible with the application of physical column mode, the data of the Task Center is compatible; In the organization-level task Center, the details of the common form are added to the details I created,

Before	After
1. If the physical column mode is enabled for application storage in the organization, a query exception occurs when I create a list in the Task Center; 2. View the form type. Only flow chart types are supported;	1. If the physical column mode is enabled for application storage in the organization, the Task Center can display and query normally; 2. Common forms and flow chart details are displayed in the list in chronological order, and quick filtering is supported;

[Open interface] supports OpenAPI in cluster local mode

Before	After
The running state of the cluster environment is completely executed in the customer's local environment. DingTalk YIDA of the original OpenAPI development platform need to be accessible on the public Internet.	Dedicated YIDA has opened high-frequency data service interfaces. At present, more than 30 core interfaces in forms, processes, and applications have been opened.

OpenAPI

[Service log] added integrated automatic execution log

It integrates automated running logs and supports manual pull and analysis by using OpenAPI methods. It supports data query in the last month, which is consistent with the query duration on the product side.

Function: you can manually view the running logs of specific tasks.	Data service: you can use OpenAPI to query organization-level logs in multiple rules.
	https://open.dingtalk.com/document/orgapp/api-getautoflowlogdetail Return results: Instance id, application code, process code, status, and details id Open platform interface description: View more running logs:https://www.yuque.com/yida/vmlc9a/phapgoel2nig25ep

Description

Only the dedicated version is available for customers.