Overview of application distribution

Application distribution is an application sales method provided by the YIDA Low-Code platform for service providers. It can help service providers quickly deploy product applications developed by the organization to customer organizations, in addition, service provider developers can enter the customer organization through a dedicated channel to complete the development and attribute configuration of some customized functions.

Preparations

Before using the YIDA application distribution function for sale, you need to complete the following preparations:

• BecomeDingTalk partners.
• ApplicationApplication Distribution permission.
• (Optional) becomeYIDA senior partner.

Features

YIDA application distribution is an agile delivery method for service provider partners. After the service provider reaches a sales agreement with his customers, the YIDA application distribution function can be used, quickly deliver product applications to customer organizations. The application distribution feature currently supports the distribution of all form pages, custom pages, portals, AI assistants, data preparation, cool applications, custom components,YIDA roles and interfaces, integration automation, connectors, message notifications, and to-do notifications. It also supports incremental and inventory distribution to upgrade customer applications.

First distribution

When distributing applications, all pages except the data dashboard are sent to the target application by default when they are first distributed, and the association rules (such as data linkage, etc.), formulas, the front-end code is sent to the target application along with the page. In addition, it supports YIDA AI assistants, data preparation, integration automation, connectors, message notifications, and to-do messages.

• Applications distributed to customer organizations can carry sample data. Each page can carry 15 pieces. After the application is distributed to customer organizations, sample data can be deleted with one click.

• Applications distributed to customer organizations are closed.EditIn the case of permission, allow the customerApplication permissionsAndPage permissionsMake custom edits. That is, customers can freely decide which enterprise users can use the application.

Disable editing permissions	The customer lost the editing permission.

• When distributing an application, the customer organization is verified to meet the relevant rights and interests of the application. If the rights and interests of the customer organization do not meet a certain functional permission of the application (such as data volume hitting a wall, etc.), the distribution fails, there is also an error message.

Secondary distribution

• Incremental distribution

Incremental distribution refers to the ability of service providers to upgrade distributed customer applications after adding new function pages. The incremental distribution page appears at the bottom of the Directory of the customer's target application. The system automatically creates a new folder and places the new distribution page in this folder.

• Stock Distribution

Inventory distribution refers to the ability of service providers to upgrade and optimize existing function pages in applications and upgrade distributed customer applications. Inventory distribution does not overwrite user-definedApplication permissions,Page permissionsAndProcess design.

Note:

Inventory distribution will overwrite and update the distributed customer target page. Therefore, you must confirm with the customer in advance and proceed with caution when distributing the inventory.

Distribution of page Association capabilities

Because functions such as roles, interfaces, AI assistants, data preparation, and custom connectors have organizational relevance, you need to enter the customer organization through remote maintenance after the application is successfully distributed, configure and enable these features.

YIDA roles and interfaces

Application Distribution supports the distribution of role and interface person information in the application. After the application is successfully distributed, you need to re-maintain the role and interface person list in the customer's organization, then it can be used normally in the customer organization.

• Common form: Page message notification and integration automation (nodes such as message notification).
• Flow chart: Page message notification, integration automation (nodes such as message notification), and process designer.

AI assistant

YIDA AI assistant support with applicationsFor distribution, the AI assistant after distribution needs to manually create activation. After successful creation, it will automatically synchronize the source application capabilities such as intelligent analysis, intelligent reporting, and active broadcasting.

Data Preparation

After the data preparation and distribution are successful, the data preparation in the user group organization is in the unexecuted state by default, and reports related to the data preparation dataset will not display data. You need to be in the user's organization, find the corresponding data preparation and manually trigger the data preparation.

Custom connector

When a custom connector is distributed, only the definition and configuration of the distribution interface are supported. The key of the connector does not support automatic distribution. It can only be used after the application is distributed successfully and manually configured in the customer organization. The FaaS connector does not distribute code synchronously. You also need to manually synchronize and deploy the code after the application is distributed successfully.