2023.06.27 update-YIDA platform capability optimization and SaaS capability upgrade

V4.2.1

YIDA SaaS R & D Workbench capability upgrade:

• NEW: Integrated Automation/scheduled trigger supports SaaS and customer second section
• Add:Integrated Automation open three-party connector supports SaaS and customer second section
• Added: YIDA SaaS applications support self-service application skip security self-test
• NEW: YIDA platform or SaaS application page supports hide Navigator

YIDA platform function optimization and repair

• Fixed: a problem with the display of alert notification member fields for timeout processing.
• Fixed: the problem that the lower-level organization accesses the application distributed by the higher-level organization and shows that it has no permission.
• Fixed: an application distribution failure caused by a deleted role referenced in the process.
• Fixed: the problem that the form is sent regularly after the application is deleted.
• Fixed: the problem that exclusive applications are associated with non-exclusive applications and the search times are wrong.
• Fixed: cache problem after proxy expiration
• Fixed: the problem that the order of the selected components changed after they were added through business rules.
• Fixed: error triggered by attachment update and integration automation
• Fixed: the to-do template is too long, resulting in the problem of not receiving To-do notifications.
• Fixed: the problem that the department component does not display the full path after batch import.
• Fix: The hidden subform field after data editing is empty

The following is a detailed update description

---

1 New: Integrated Automation/scheduled trigger supports SaaS and customer second section

Supported versions: YIDA SaaS R & D Workbench

• Integration automation flow: supports user-defined integration automation flow, orchestrates business logic, and supports scheduled triggering to complete scheduled push messages, scheduled update data, and coordination with existing node types, various timing scenarios such as scheduled approval. For more information, see触发类型 | 钉钉宜搭·帮助中心

Function description: ISV supports the integration of automatic flow configuration timing triggers when developing SaaS applications. After subscribing to SaaS applications on the customer side, you can enter the management background to modify the integration automation flow and timing trigger logic.

SaaS R & D Workbench> integration automation> scheduled trigger DingTalk Workbench enter the SaaS application purchased> Application Management background> integrated automation flow

2 New: Integrated Automation and open three-party connectors support SaaS and customer second section

Supported versions: YIDA SaaS R & D Workbench

• Integrated Automation flow open three-party connector: Allows you to customize integrated automation flow and configure three-party connector from DingTalk application market. For more information, see集成&自动化-连接器 | 钉钉宜搭·帮助中心

Function description: ISV supports integrated automated stream configuration when developing SaaS applications DingTalk application market three-party connectors After subscribing to SaaS applications on the customer side, you can enter the management background to modify any content of the integrated automation stream.

SaaS R & D Workbench> integration automation> connector nodes> three-party connectors DingTalk Workbench enter the purchased SaaS application> Application Management background> integration automation> connector node> three-party connector

3 New: YIDA SaaS applications support self-service application skip security self-test

Supported versions: YIDA SaaS R & D Workbench

• After developing third-party SaaS applications on the SaaS R & D Workbench YIDA and associated with the DingTalk open platform, you can configure relevant information according to the following process, the security self-test will be automatically skipped (no need for contact workers to skip the self-test). After skipping, you can add the application to the experience test organization in Release & shelf, you can test the application function by yourself. For more information, seeSaaS应用开发指南 | 钉钉宜搭·帮助中心
• How to configure skip self-test process:

You need to set events and callbacks, as shown in the following figure:

step1: encrypts Aes_key by using the followingdecryptMethod for YIDAsystemTokenSet after encryption private static final char[] HEX_ARRAY = "0123456789abcdef".toCharArray(); public static String bytesToHex(byte[] bytes) { char[] hexChars = new char[bytes.length * 2]; for (int i = 0; i < bytes.length; i++) { int v = bytes[i] & 0xFF; hexChars[i * 2] = HEX_ARRAY[v >>> 4]; hexChars[i * 2 + 1] = HEX_ARRAY[v & 0x0F]; } return new String(hexChars); } private static String decrypt(String input) throws NoSuchAlgorithmException { MessageDigest digest = MessageDigest.getInstance("SHA-256"); byte[] hash = digest.digest(input.getBytes(StandardCharsets.UTF_8)); // 将散列码转换成43位加密串 return bytesToHex(hash).substring(0, 43); } YIDA of systemToken is obtained in YIDA application settings-deployment O & M. step2: The signature Token, which is the YIDA of the preceding systemToken. step3: callback request address (https://www.aliwork.com/saasAppCallback/{appKey}) where appKey is applied by YIDA, such as the application code of APP_XXX

4 New: YIDA platform or SaaS application page supports hide Navigator

Supported versions: any version of YIDA platform and YIDA SaaS R & D Workbench

• When the YIDA page is integrated into other systems, you can configure the hide top navigation bar and the left page function navigation bar. Concatenated after the embedded page URL? isRenderNav=falseOK.

Function description: When a page of the YIDA application is embedded in other three-party applications, you can hide the top menu of the page and the left menu bar.

YIDA the navigation of a page on the platform is hidden, such as the platform settings enterprise performance page. A menu navigation of SaaS applications is hidden, such as SaaS application role management. The navigation of a page menu in the application is hidden, such as the page permission configuration page.