Copyright©2025 Yonyou Group All rights reserved.Without the written permission of Yonyou Group, no part or whole of the content of this user manual may be copied, reproduced, translated, or reduced for any purpose. The content of this user manual may change without notice, please be aware.Please note: The content of this user manual does not represent the commitments made by Yonyou.Overall OverviewIn addition to the general low-code platform capabilities, the application construction service focuses on the core capabilities required for enterprise-level applications, which include models, events, automation, integration, and the Intelligence Platform, leveraging its own platform, general domains, industry applications, and the advantages of customers of different scales across multiple industries.The app is built on the basis of Cloud Native, multi-tenant, and model-driven technologies, organically integrating decentralized and independent building models through visualization and business component assembly. It provides developers, implementers, and frontline business personnel with low-code or even no-code application building capabilities, enabling rapid response to business changes and achieving commercial innovation.The app is built based on the analysis of different types of developers and scenarios, launching two versions of the product: Standard Version and Professional Version.The standard version provides two modes: low-threshold no-code declarative configuration and online low-code functional development. It is supported by a multi-tenant, secure, and reliable public engine provided by the application construction platform, allowing users to focus on their business without worrying about code and deployment operations. This enables implementation personnel and business staff with no-code development experience to quickly get started and execute personalized tasks for the enterprise tenant. The visual construction process of the standard version consists of five modules: data modeling, page modeling, workflow, automation (workflow, RPA, functions), integration configuration, and release management. Within these five modules, there are eight related designers: Entity Designer, Query Metadata Designer, Document Page Designer, Canvas Page Designer, Print Template Designer, Workflow Designer, Business Process Designer, and Function Programming Designer. The designers provide components for model description, and models, components, designers, events, functions, etc., are integrated throughout the visual construction process, allowing users to focus more on their business descriptions and creative realizations.The professional version of the application building service fully encompasses the modeling process and capabilities of the standard version, while providing users with the creation of a self-built application engine, scaffolding downloads, local development and debugging, CICD, deployment, and full life cycle management of ecosystem application launch.Overall ValueFull-stack visual programming: Provides a no-code visual designer for different groups such as implementers, tenant operators, and junior developers, allowing for quick online configuration to achieve typical business processes and seamless integration of the entire development workflow.Full Life Cycle Management: Provides developers with online agile development process management, supporting the entire workflow of code project creation, Git integration, code download, feature development, integrated deployment of front-end and back-end separation, functional testing and validation, and other engineering services.Low-Code Extension: Follows a Cloud Native technology and multi-tenant architecture programming model. Based on a unified Metadata specification for model-driven implementation, the platform supports code generation to local, deep customization of source code, and provides a complete set of standard examples, development red books, and training courses, suitable for in-depth and complex extension development for senior developers and above.Related ContentBuild PlatformProfessional DevelopmentDevelopment ServiceSandbox ManagementFunction DescriptionThe sandbox is an independent, secure, and destructible environment that can be recycled, with specific applications, configurations, or data, used for various scenarios such as development configuration, testing and debugging, integration verification, and patch upgrades.Development Sandbox: Open a new sandbox tenant for the current tenant; within the sandbox tenant, testing changes or creating new applications will not damage the customer's official data and configuration; after change validation, the transmission pack tools within the sandbox can be used to pack and upload change data to the current tenant for deployment and import for use.Testing Sandbox: Based on the development of sandbox capabilities, it provides you with the ability to select certain data from the current tenant to synchronize to the sandbox tenant, achieving the construction of a UAT validation environment that simulates the formal tenant, which can better ensure the effectiveness of the implementation and validation during the go-live.Business RuleCreate New Sandbox: Enter the "Sandbox Management" function, users can create the corresponding number of sandboxes based on the number of sandboxes purchased. When creating a new sandbox, product specifications within the tenant are automatically enabled, and when the status changes to "Enabled," it indicates that the creation is complete. The creator of the sandbox is automatically set as the tenant administrator for that sandbox.Enable Sandbox: The sandbox will be disabled when it expires. After successful renewal, the disabled sandbox needs to be manually enabled. The expiration time of the enabled sandbox is the same as the expiration time of the license.Import Users: After creating a new sandbox, the sandbox creator can select the users from the current tenant who need to enter the sandbox and import them into the sandbox. The imported users can then access the sandbox.Enter Sandbox: After importing users to a specific sandbox, users can quickly log in to the sandbox environment from the sandbox list.View Sandbox History: You can view the history of key operations such as creating, deleting, and modifying sandboxes within the Sandbox Management feature on the Sandbox History tab.Column DescriptionColumnDescriptionTotal SandboxesThe total number of unexpired sandboxes purchased by the current tenantUsed SandboxesThe number of sandboxes that the current tenant has created and is currently usingAvailable SandboxesThe number of sandboxes that the current tenant can still create, equal to the total sandboxes minus the number of used sandboxesStatusIndicates the activation status of the sandbox, including three states: Activating, Activated, and Failed; please be patient during the Activating state, the Activated state indicates successful activation and is ready for use, and the Failed state indicates activation failure, requiring contact with the administrator for resolutionOperation InstructionsSandbox Management Home PageThrough the iuap > App Build Service > Build Platform > Sandbox Management, enter the homepage of the Sandbox Management function, where you can view the total number of valid development sandboxes and testing sandboxes purchased by the current tenant, as well as the used and available status.The Sandbox Management function provides users with the ability to add, delete, modify, and query sandboxes, import users, and access the sandbox. Additionally, key operation records of additions, deletions, and modifications can be viewed in the sandbox history tab.Create SandboxWhen there are available sandbox quantities for the tenant, the user can click the create button to select the corresponding development sandbox or testing sandbox for creation. When creating a new sandbox, the product specifications within the tenant are automatically activated for the sandbox. When the status changes to activated, it indicates that the creation is complete. The creator of the sandbox is automatically set as the tenant administrator of that sandbox.Enable SandboxWhen the sandbox expires, it will be disabled. After successful renewal, the disabled sandbox needs to be manually re-enabled. The expiration time of the enabled sandbox will be the same as the expiration time of the license.Import UserAfter creating a new sandbox, the sandbox creator can select the users from the current tenant who need to enter the sandbox and import them into the sandbox. The imported users will then have the right to enter the sandbox.Enter SandboxAfter the sandbox is successfully created, users imported into the sandbox can click the Enter Sandbox button on the sandbox row to quickly jump to that sandbox. After logging in, they will enter the workbench of that sandbox tenant.Sandbox HistoryIn the Sandbox History tab, view the key operation history of creating, deleting, and modifying sandboxes executed within the Sandbox Management function.App EngineProduct ValueThe low-code development platform includes two development modes: visual application building and professional development. The professional development mode primarily targets users who possess coding development skills. YonBuilder is derived from Yonyou's over 30 years of experience in enterprise service product R&D and customer delivery. Its goal is to provide comprehensive low-code development platform support for YonBIP public cloud customers, dedicated customers, ecosystem ISVs, and domain product development. It offers suitable development tools and workflows for different user groups with varying development experience, including no-code standard services for business personnel and implementation staff with little or no development experience, as well as professional services for developers that manage the entire life cycle of code development, testing, and deployment. The application engine is the core of YonBuilder's professional development services, used to manage microservices developed by professional developers based on cloud-native technology, thereby extending the default framework.Operation InstructionsThe application engine list page can manage application engines, and developers can view the engines they have created.The developer clicks on "Create New Engine" to create a self-built engine, needing to input the engine code and name. Select the corresponding resource pool and fill in the git-related information. Click "Confirm."The application engine will automatically perform related initialization operations, including generating code, configuring YMS and data, registering supporting services, initializing pipelines, and creating product trays.If the automatic execution process fails, you can adjust the environment configuration based on the reason for the failure and then click retry.You can start the app build after creation is complete.Development Resource ManagementResource CenterFunction OverviewBy extending components through the component registration center, shared components can be achieved. Defined in one place and used in multiple places. Custom settings for component properties and actions can be made through the designer to support user secondary development.Key AppsThe component registration center is divided into four statuses: Development Status, Configuration Status, Design Status, and Operating Status.Development Status: Developing and debugging components.Configuration State: Define the properties, actions, and other information of components on the component registration center management page.Design State: Define the information for the extended components in the Designer.Runtime State: Rendering of runtime extension components.Operation InstructionsDevelopment StatusInstall CLI tools, create a project, first determine our current development directory, execute the following command in the root directory, and it will enter an interactive state, prompting for the project name and other information.Before running the component scaffolding project, we need to install the dependencies. You can use npm, cnpm, and within the intranet of the park, you can also use ynpm.Enter the project directory, and input this command to create a new component in the ./components directory. The component name is a required field. This name will be used later in the component center configuration page, so it's best to remember it.In the project directory, entering this command will pack the written demo and preview it in the browser. The default component styles will not be included in the package, and a default index.css will be generated. If you need to pack it into index.js, you need to add "extraCss": false in config.json.Configuration StatusLog in to the Workbench, under the App Build menu, find the Component Extension Center menu.The homepage will have two tabs, one is the Resource Library and the other is the Component Package. In the Resource Library, components can be added to the Component Library, and relevant information about the components can be configured in the Component Library. In the Component Package, the creation of the Component Package and the packing of the Component Package can be done. After packing, the Component Package will automatically sync to the Designer of the current tenant.1.Click the
button to add to the Component Library.2.Add ComponentSelect the data from the newly added Component Library, click the button to enter the configuration page of the Component Library, and perform component addition and resource upload on the configuration page.Upload the resource index.min.js (in the dist directory) generated during the build (npm run build) of the above development.Note: Each time new resources are uploaded, only after packing on the component package management page will the design state and runtime state reference the latest version.3.Add component properties and actionsThe extended component properties and actions will be displayed in the left panel of the Designer. The set property values will be passed into the component via props. Users can also extend related actions through the actions panel.In the props of the basic component, there will be a pageModel property, which represents the current page model viewModel. Events are triggered through the execute time of the viewModel. In the extension script, the model is bound through the on event of the viewModel.The props of the container component will pass the page model viewModel, and events are triggered through the execute time of the viewModel. In the extension script, the model is bound using the on event of the viewModel.Design StateLog in to the workbench, open the designer, and you can see your own extension components. Drag the component into the canvas area, select the component to configure its properties and actions.Operating StateAfter designing, click , and you can directly see the final effect during the preview. The rendering mechanism of the extension component in the running state is consistent with that in the design state. Therefore, no additional processing is required in the running state.
