DingTalk Low-Code System Terminology Explanation

• Global Variable - Used to manage page state and control page re-rendering, similar to state in React;
• Remote API - A series of configurations used to describe server-side HTTP interfaces, including request address, parameters, data processing functions, etc.;
• Schema - Low-code protocol: Used to describe low-code related components, such as pages/components, etc., similar to HTML.
• Component Unique Identifier - Yida will set a globally unique identifier for each component to identify component instances (equivalent to DOM id). The component unique identifier can be viewed through the component property panel; since changing the unique identifier of form components will affect database storage (different models may cause data misalignment), to prevent ordinary users from making mistakes, we provide Schema editing mode, which can be used carefully by developers when needed;
• Page - An independent display interface, the main entity built in Yida. Different types of Yida pages can be created through the workspace, such as: forms, reports, custom pages, etc.;
• Material - Front-end capabilities that can be沉淀 and used directly, generally manifested as business components, blocks, templates.
• Business Component - Components defined based on basic components within a business domain, which may include specific business domain interactions or business data. Only configurable properties are exposed externally, and must be published to the public domain (such as Alibaba NPM); they can circulate within the same business domain but do not need to ensure cross-business domain reusability.
• Low-Code Business Component - Built through low-code editors, different from source code developed business components. It is a type of business component that follows the definition of business components; at the same time, low-code business components can continue to be edited multiple times through low-code editors.
• Block - Composed by nesting a series of business components and layout components through low-code building methods. It does not expose configurable properties externally. By wrapping with a block container component, the block internally has complete styles, events, lifecycle management, state management, and data flow mechanisms. It can exist and run independently, and can achieve quick reuse across pages and applications through copying schema, ensuring normal functionality and data.
• Template - Business components and blocks within a specific vertical business domain can be combined into a single page, or combined with routing to form multiple page sets, collectively called templates.