YiDA Glossary - DingTalk Help Center

Use this glossary as a quick reference when you need to confirm the meaning of a specific YiDA term while building or configuring your apps.

Workbench

Term	Definition
Start	After you sign in to YiDA and click Workbench, you land on the Start page first. This page is a comprehensive hub where you can view an overview of important information.
Template Gallery	Browse templates in the Template Gallery to see what YiDA can do and the results you can achieve.
Solutions	Industry-specific solutions delivered by YiDA certified service providers. They offer flexible, efficient, and tailored customization to ensure the final solution fully fits your business.
App Center	Displays apps that have been released within YiDA or template apps that have been enabled.
My Apps	My Apps shows the interface visible to the currently signed-in user. The interface varies based on the user’s permissions.
Task Center	The Task Center aggregates the forms and workflow records you have submitted in YiDA apps. You can view the details of submitted forms and workflows that require your action.
Customization Center	Certified service providers build business apps tailored to your organization’s needs. To provide broader and higher-quality services, we have added a customization entry point on the YiDA Start page.
Help Center	The YiDA User Guide, including videos, case studies, and detailed documentation.
Version	For YiDA tenants activated after January 7, 2021, this page displays your edition: Free plan, Basic edition, or Professional edition.
Platform management	The entry point for configuring platform admin permissions, message templates, roles, and contacts.

Regular Form

Term	Definition
Regular form	A regular form is made up of multiple components and is used to collect and submit data.
Component	A container for storing data. Different component types store different data types. For example, a numerical component stores numerical data, and text components store text data.
Formula editing	When filling out or editing form data, you can have a component’s value calculated automatically based on a formula. This improves data entry efficiency and reduces errors.
Associate data from other forms	Use association settings to pull data from an associated form into the current form.
Data linkage	When the value of one field in a form changes, the value of another field in the same form changes accordingly. This is often used to set default values for components.
Business association rules	Business association rules apply when data in two forms is associated. For example, in inventory management, inbound and outbound records must be aggregated into the final inventory table for display and review.

Workflow Form

Term	Definition
Workflow form	A form with a workflow. Compared with regular forms, workflow forms include an additional workflow routing stage.
Workflow settings	Configure routing rules for data in a workflow form so that data flows according to the predefined workflow.
Step	Each stage of a workflow is called a step. For each step, you can configure component visibility and editability, as well as the approver, executor, and CC users.
Step submission rules	Step submission rules use formula checks to determine whether a user can submit a workflow or an approver can process the workflow when they take action.

Report

Term	Definition
Report designer	When you need to aggregate data submitted by employees for review, create a report page and use the components in the report designer to analyze, aggregate, and query data.
Report component	Displays data submitted in a form as a chart.
Report formula	Used to process data from the original form.
Data set	When a report chart component displays data, select a form or workflow form in the app as the data set.
View table	A view table preprocesses existing form data by associating a single table or multiple tables. It also supports intermediate table mode to enhance data processing. Report visualizations, form linkage, and other scenarios can reference data from view tables directly.
Cross-app	Also known as “cross-app data retrieval.” It refers to calling form data from another YiDA app within the current app, enabling data connectivity across YiDA apps.

External Link

Term	Definition
External link	When you need to display content from another website, paste the website URL here.
Open in new window	Opens the external link in a new window when clicked.

Custom Page

Term	Definition
Custom page	Customize the style and display data from all forms in the app for greater flexibility in meeting your specific business needs. Custom pages are more complex than regular forms and typically require code configuration.
Custom page designer	The custom page designer consists of four parts: top action bar, left toolbar, center canvas, and right attribute configuration panel.

Premium Features

Name	Definition
Serial number	Automatically generates a unique identifier after form data is submitted. It is commonly used to number items in inventory management scenarios.
Data preparation	Data preparation refers to the series of processing steps performed on data sources and data sets before visual analysis, such as multi-table insertion and data transformation. It is a preliminary step in visual analysis.
Logic orchestration	In certain scenarios, submitting a form triggers business logic. YiDA currently supports two built-in core business logic flows—records and workflows—along with secondary logic flows such as comments. Each business logic flow has its own lifecycle. Events are emitted at each stage of the lifecycle and can be used as extension points. Once an event is received, the corresponding execution plugin runs to perform the business logic.
Advanced workflow	To meet advanced workflow requirements, YiDA provides an advanced workflow designer. It covers nearly all features of the standard designer and adds extra capabilities. For example, it includes components such as branch and aggregation. It also enhances component features and settings, distinguishing between basic and advanced settings. You can customize executor rules and completion strategies. Standard workflow editors can be upgraded to the advanced workflow editor.
Service callback	In YiDA, any interaction that involves calling an API service is known as a third-party service callback. This support for API calls allows YiDA to integrate with external systems and exchange data, preventing YiDA apps from becoming isolated silos.
App distribution	App distribution helps service providers quickly deploy apps developed in their own organization to customer organizations’ YiDA tenants. Service provider developers can also access customer organizations through a dedicated channel to develop customized features and configure attributes.
Service registration	Service registration is a prerequisite for using the service callback feature. It involves registering the APIs of third-party services with the YiDA platform. Key configurations include the API’s input and output parameters, authentication and encryption information, permission control, and API descriptions, so that the API can be referenced quickly when needed.
Integration & Automation	Provides an overall upgrade to the logic orchestration feature and integrates the DingTalk Connector. Official DingTalk apps, apps in the DingTalk ecosystem, and enterprises’ own systems can be integrated with YiDA in a lightweight manner, giving YiDA apps native interoperability.
Connector Factory	Use the YiDA Connector Factory to build custom connectors for in-house systems or third-party apps.
Associated organizations	With DingTalk’s Associated organizations feature, an organization can associate a sub-organization with a parent organization. During association, you can select all members or members of specific departments in the sub-organization to join the associated organization.
DataV dashboard	Seamlessly use various established data sets (including cross-app, sub-tables, and view tables) to build visually stunning digital dashboards, delivering striking data-driven impact to your YiDA apps.
CorpId	CorpId is the unique identifier of a DingTalk organization. It is required for purchasing services, calling APIs, and other operations. A CorpId looks like: dingfa087xxxx55b. You can obtain your CorpId in either of the following ways: • Option 1: View it on the YiDA platform settings page. Go to YiDA Home > Platform Settings > Basic Information. • Option 2: View it in the DingTalk Open Platform developer console. For details, see the DingTalk Open Platform documentation.