2024.05.10 update-exclusive YIDA capability upgrade

Capability release

• Single sign-on: the single sign-on process has been improved. Now, users can directly return to the page viewed before login after automatic login is completed, which improves the consistency of use.
• Upstream and downstream interconnection: optimized the ability of integration automation to send cool application message cards to downstream teams. Now, it supports directed sending to internal groups and designated members of downstream organizations.
• Application Distribution: You can flexibly adjust the editing permissions for application distribution to view the distribution status in real time.
• OpenAPI:

• AddPreview approval processInterface.
• Initiate YIDA approval process interfaceAddprocessDataField to configure the initiator-selected node.

BUG fixes

• DingTalk roles: fixed an unexpected page turning function exception during page turning to query role information.
• Exclusive Design: optimized the function of modifying the Logo of the application and platform navigation to ensure that the Logo in the upper-left corner of the Workbench can be automatically updated after the change, which solves the problem of accidental unsynchronization before.

The following is a detailed update description

Capability release

Single sign-on

Supported versions: Exclusive Edition

The single sign-on process has been improved. Now, after the automatic sign-on is completed, users can directly return to the page viewed before logging on, which improves the consistency of use.

Before	After
The single sign-on service can only be adjusted to a fixed page and needs to be manually filled in by the platform administrator.	After you jump to another system for single sign-on, the source page before login is automatically opened (instead of the specified callback address).

Integrated Automation

Supported versions: Exclusive Edition

The ability of integrated automation to send cool application message cards to downstream teams has been optimized. Now, it can be directed to internal groups and designated members of downstream organizations.

Before	After
It can only be sent to internal groups of downstream organizations.	It can be sent to downstream groups or specific downstream members to flexibly push data cards for timely business reminders.

Application Distribution

Supported versions: enable the service provider to authenticate the paid version of the organization

For DingTalk eco-partners, the application distribution function is improved, which enables flexible adjustment of application editing permissions anytime and anywhere, and enhances the convenience of management. At the same time, it adds the function of querying the distribution status of applications in real time, and can immediately feedback the cause of failure when distribution problems occur, thus improving the troubleshooting efficiency.

Before	After
When distributing an application, the application editing permission cannot be modified twice. If the permission is not enabled during distribution, it will no longer be enabled.	Allows you to flexibly switch the editing permissions of applications anytime and anywhere.
Application distribution is a time-consuming and batch operation, and the service provider cannot perceive the sending status of the application.	You can view the distribution status of applications at any time. When the distribution exception occurs, the cause of the failure is automatically returned.

OpenAPI

• AddPreview approval processInterface, which is used to preview before initiating the approval process.Status of approvers after the process is initiated, for more information, seePreview approval process.

Description:

This interface does not actually initiate the process and therefore does not generate business data.

• Initiate the YIDA approval process interface,AddprocessDataField, which is used to fill in the approver information selected by the initiator's optional node. For more information, seeInitiate YIDA approval process.

Description:

• processDataThe parameter is ajsonArray. The number of elements represents the number of initiator nodes.
• The node selected by each initiator,keyThe unique identifier of the node selected by the initiator,valueRepresents the approver to be specified.userIdList,valueIt is in array format, separated by commas.
• The unique identifier of the initiator-selected node can be obtained fromPreview approval processIn the return value of the interfaceoperatorObtained in the field. When you preview the approval process that contains the initiator-selected node,operatorThe field returns a prefix* *_optionalApprovalUnique identifier,For example:_optionalApproval_node_ocltdztr2b3 * *.

BUG fixes

• DingTalk roles: Fixed the problem that page turning may fail occasionally when querying role information.
• Exclusive Design:Optimized and modifiedApplication and platform navigation LogoTo ensure that the Logo in the upper-left corner of the Workbench can be automatically updated after the change, which solves the problem of unsynchronization that occurred before.