Skip to main content
  • Global variable - Manages page state and controls page re-rendering, similar to state in React.
  • Remote API - A set of configurations that describe Server-side HTTP interfaces, including the request URL, parameters, and data processing functions.
  • Schema - The low-code protocol used to describe elements of the low-code system, such as pages and components, similar to HTML.
  • Component unique identifier - YiDA assigns a globally unique identifier to each component to identify component instances (equivalent to a DOM id). You can view a component’s unique identifier in the component property panel. Because changing the unique identifier of a form component affects database storage (the Model may differ, which can cause data mismatches), we provide the Schema editing mode to prevent regular users from making mistakes. Developers should use it with caution when needed.
  • Page - A standalone display interface. It is the primary Entity built in YiDA. From the workbench, you can create different types of YiDA pages, such as Forms, reports, and custom pages.
  • Material - Front-end capabilities that can be accumulated and reused directly, typically in the form of business components, blocks, and Templates.
  • Business Component - A Component defined on top of Basic components within a business domain. It may include interactions or business data specific to that domain, exposes only configurable properties externally, and must be published to a public registry (such as Alibaba NPM). It can circulate within the same business domain but is not required to be reusable across business domains.
  • Low-Code Business Component - Built with a low-code editor. Unlike source-code-based development, it is a type of business Component that follows the definition of a business Component. In addition, a low-code business Component can be edited multiple times through the low-code editor.
  • Block - Built through low-code, a block is composed by nesting a series of business components and Layout components. It exposes no configurable properties externally. Wrapped by a block container Component, a block features complete style, event, lifecycle management, state management, and data flow mechanisms internally. It can exist and run independently, and can be quickly reused across pages and Apps by copying its schema, ensuring proper functionality and data.
  • Template - Within a specific vertical business domain, business components and blocks can be combined into a single Page, or further combined with routing into a set of multiple pages. Together they are referred to as a Template.