[{"data":1,"prerenderedAt":117},["ShallowReactive",2],{"legacy:engines:en":3},{"id":4,"title":5,"description":6,"keywords":7,"author":8,"robots":9,"bodyClass":10,"image":11,"jsonld":12,"html":116},"engines","Platform - JEDP Digital Platform","JEDP platform capabilities: six major engines for organization, permissions, forms, workflows, reports, and integration, paired with design-time \u002F run-time dual intelligences, supporting multi-language operation and SaaS multi-tenant isolation, enabling rapid construction of business products.","JEDP, platform capabilities, core engine, agent, multilingual, SaaS, multi-tenancy, digital platform","Shenzhen Langbowan Information Technology Co., Ltd.","index, follow","page-engines","https:\u002F\u002Fwww.jedp.cn\u002Fres\u002Fimages\u002Fproduct\u002Fplatform-overview.webp",[13,80,87],{"@context":14,"@type":15,"@id":16,"url":17,"name":5,"description":18,"mainEntity":19,"inLanguage":74,"isPartOf":75},"https:\u002F\u002Fschema.org","CollectionPage","https:\u002F\u002Fwww.jedp.cn\u002Fengines#webpage","https:\u002F\u002Fwww.jedp.cn\u002Fengines","JEDP platform capabilities: six engines, dual agents in design state and operation state, multi-language operation, SaaS multi-tenancy, support the rapid construction of business products and customer landing.",{"@type":20,"name":21,"numberOfItems":22,"itemListElement":23},"ItemList","JEDP Six Engines and Dual Agents",9,[24,30,35,40,45,50,55,60,65,69],{"@type":25,"position":26,"name":27,"description":28,"item":29},"ListItem",1,"Organization Engine","JEDP Organization Engine: unified department trees, post assignments and reporting lines—providing org context for permission scopes and workflow assignees, with multi-tenant isolation.","https:\u002F\u002Fwww.jedp.cn\u002Fengine\u002Forg",{"@type":25,"position":31,"name":32,"description":33,"item":34},2,"Permission Engine","JEDP Permission Engine: RBAC menu auth, department data scope, form\u002Flist field and button control, covering workflow nodes and report\u002Fdashboard views, with auditable login and operations.","https:\u002F\u002Fwww.jedp.cn\u002Fengine\u002Fperm",{"@type":25,"position":36,"name":37,"description":38,"item":39},3,"Form Engine","JEDP Form Engine: define business data with form models, generate PC and mobile UIs via form\u002Flist designers, and expose CRUD plus HTTP\u002FSQL through model services.","https:\u002F\u002Fwww.jedp.cn\u002Fengine\u002Fform",{"@type":25,"position":41,"name":42,"description":43,"item":44},4,"Workflow Engine","JEDP Workflow Engine: Flowable + BPMN 2.0 with competitive\u002Fparallel\u002Fserial sign-off and countersign; assignees resolve from org or form fields; includes inbox, instance monitoring, and versioning.","https:\u002F\u002Fwww.jedp.cn\u002Fengine\u002Fflow",{"@type":25,"position":46,"name":47,"description":48,"item":49},5,"Report Engine","JEDP Report Engine: custom report layouts and datasets with preview\u002Fprint and PDF\u002FWord\u002FExcel export, plus Dashboard and big-screen design for operations visibility.","https:\u002F\u002Fwww.jedp.cn\u002Fengine\u002Freport",{"@type":25,"position":51,"name":52,"description":53,"item":54},6,"Integration Engine","JEDP integration: outbound model and process APIs, auth templates, HTTP\u002FSQL services, scheduled jobs, and WeCom\u002FDingTalk\u002Fmail\u002FSMS channels plus OAuth2 to connect enterprise systems.","https:\u002F\u002Fwww.jedp.cn\u002Fengine\u002Fintegration",{"@type":25,"position":56,"name":57,"description":58,"item":59},7,"Dual Agents","JEDP dual agents: design-time models configuration in natural language, including ⌘K. Runtime queries within authorization, can show dialog text and charts or export Office, HTML, and Markdown, and can create data or complete reviews through business APIs. They are not the same chat window.","https:\u002F\u002Fwww.jedp.cn\u002Fengine\u002Fagent",{"@type":25,"position":61,"name":62,"description":63,"item":64},8,"Multi-language","Model once, run in many languages; about 49 business language directories, enabled by each tenant, with manually maintained translations and fallback to the source text when a translation is missing.","https:\u002F\u002Fwww.jedp.cn\u002Fengines#i18n",{"@type":25,"position":22,"name":66,"description":67,"item":68},"SaaS Multi-tenant","Suitable for group subsidiaries, partner operations and multi-delivery centers working in parallel.","https:\u002F\u002Fwww.jedp.cn\u002Fengines#saas",{"@type":25,"position":70,"name":71,"description":72,"item":73},10,"Technical architecture","Front and back ends are separate: Vue and Spring Cloud microservices, deployable with Docker or Kubernetes, or on-premises and in a private cloud. The edge is Nginx OpenResty and the gateway. The registry is Nacos. Processes use Flowable and BPMN 2.0. Databases and cloud are chosen per project.","https:\u002F\u002Fwww.jedp.cn\u002Fengines#stack","zh-CN",{"@type":76,"@id":77,"name":78,"url":79},"WebSite","https:\u002F\u002Fwww.jedp.cn\u002F#website","JEDP Digital Platform","https:\u002F\u002Fwww.jedp.cn\u002F",{"@context":14,"@type":81,"itemListElement":82},"BreadcrumbList",[83,85],{"@type":25,"position":26,"name":84,"item":79},"Home",{"@type":25,"position":31,"name":86,"item":17},"Platform",{"@context":14,"@type":88,"@id":89,"mainEntity":90},"FAQPage","https:\u002F\u002Fwww.jedp.cn\u002Fengines#faq",[91,97,101,105,109,113],{"@type":92,"name":93,"acceptedAnswer":94},"Question","What are JEDP’s six engines?",{"@type":95,"text":96},"Answer","Organization, Permission, Form, Workflow, Report, and Integration—covering org master data, authorization, modeling\u002FUI, approvals\u002Fflows, reporting\u002Fdashboards, and system connectivity.",{"@type":92,"name":98,"acceptedAnswer":99},"How do the six engines relate to the product lines?",{"@type":95,"text":100},"The six engines are the shared foundation. Seven product lines sit on it and can go live one at a time. Combined use does not create a second organization, permission model, or master-data set. The agents sit on the foundation—design-time modeling, and runtime query, export, and handling—and are not a seventh engine.",{"@type":92,"name":102,"acceptedAnswer":103},"What are the dual agents?",{"@type":95,"text":104},"Design-time uses natural language to build or change application categories, apps, modules, form models, and page or process configuration (⌘K assists scripts and SQL). Results must enter the designer for review before publish. Runtime, within authorization, answers questions as in-dialog text and charts or as Office, HTML, and Markdown, and creates data or completes reviews through business APIs. It does not write to the database directly and does not exceed the user's permissions.",{"@type":92,"name":106,"acceptedAnswer":107},"Does it support multilingual and overseas rollout?",{"@type":95,"text":108},"Yes. About 49 language catalogs are built in; tenants opt in, with fallback to the source string. Delivered locales include Simplified Chinese, Traditional Chinese, and English.",{"@type":92,"name":110,"acceptedAnswer":111},"Does it support multi-organization and multi-tenant?",{"@type":95,"text":112},"Yes. SaaS multi-tenant covers the full lifecycle with tenant-level isolation—fit for multi-plant and multi-subsidiary groups.",{"@type":92,"name":114,"acceptedAnswer":115},"What is JEDP's technical architecture?",{"@type":95,"text":72},"\u003Csection class=\"engines-section page-section\" id=\"platform\">\n    \u003Cdiv class=\"engines-hero-band\">\n      \u003Ch1 class=\"section-title scroll-reveal\">Platform\u003C\u002Fh1>\n      \u003Cp class=\"section-subtitle scroll-reveal\">Built on Six Engines and Dual Agents—with reports and big screens—supporting multilingual runtime and SaaS multi-tenant. Explore \u003Ca href=\"#engines\">Six Engines\u003C\u002Fa> · \u003Ca href=\"#agent\">Dual Agents\u003C\u002Fa> · \u003Ca href=\"#i18n\">Multi-language\u003C\u002Fa> · \u003Ca href=\"#saas\">SaaS Multi-tenant\u003C\u002Fa>\u003C\u002Fp>\n      \u003Cnav class=\"page-anchors scroll-reveal\" aria-label=\"On this page\">\n        \u003Ca href=\"#engines\">Six Engines\u003C\u002Fa>\n        \u003Ca href=\"#agent\">Dual Agents\u003C\u002Fa>\n        \u003Ca href=\"#stack\">Technical architecture\u003C\u002Fa>\n        \u003Ca href=\"#i18n\">Multi-language\u003C\u002Fa>\n        \u003Ca href=\"#saas\">SaaS Multi-tenant\u003C\u002Fa>\n      \u003C\u002Fnav>\n    \u003C\u002Fdiv>\n\n    \u003Cdiv class=\"engines-block\">\n      \u003Ch3 class=\"engines-block-title scroll-reveal\" id=\"engines\">Six Engines\u003C\u002Fh3>\n      \u003Cp class=\"engines-block-lead scroll-reveal\">Designed in three layers—data model, business process, and interface—as the shared foundation for seven product lines. Adopt a line for a given scenario, or one line at a time. Combined rollouts do not stand up a second organization or master-data set.\u003C\u002Fp>\n      \u003Cdiv class=\"engine-container\">\n        \u003Carticle class=\"engine-card scroll-reveal\">\n          \u003Cdiv class=\"engine-card-head\">\n            \u003Cdiv class=\"engine-card-icon\">\u003Ci class=\"fas fa-sitemap\">\u003C\u002Fi>\u003C\u002Fdiv>\n            \u003Ch3>Organization Engine\u003C\u002Fh3>\n          \u003C\u002Fdiv>\n          \u003Cp class=\"engine-card-lead\">People-centric org master data and reporting lines\u003C\u002Fp>\n          \u003Cul>\n            \u003Cli>Dept tree, assignments and org chart view\u003C\u002Fli>\n            \u003Cli>Posts \u002F job types and reporting lines\u003C\u002Fli>\n            \u003Cli>Tenant isolation for permission scopes and workflow assignees\u003C\u002Fli>\n          \u003C\u002Ful>\n          \u003Ca class=\"engine-card-more\" href=\"\u002Fengine\u002Forg\">Learn more \u003Ci class=\"fas fa-arrow-right\" aria-hidden=\"true\">\u003C\u002Fi>\u003C\u002Fa>\n        \u003C\u002Farticle>\n        \u003Carticle class=\"engine-card scroll-reveal\">\n          \u003Cdiv class=\"engine-card-head\">\n            \u003Cdiv class=\"engine-card-icon\">\u003Ci class=\"fas fa-user-shield\">\u003C\u002Fi>\u003C\u002Fdiv>\n            \u003Ch3>Permission Engine\u003C\u002Fh3>\n          \u003C\u002Fdiv>\n          \u003Cp class=\"engine-card-lead\">Across menus, data rows, page fields and reports\u003C\u002Fp>\n          \u003Cul>\n            \u003Cli>RBAC + department data scope\u003C\u002Fli>\n            \u003Cli>Form \u002F list field and button control\u003C\u002Fli>\n            \u003Cli>Login and operation logs for auditability\u003C\u002Fli>\n          \u003C\u002Ful>\n          \u003Ca class=\"engine-card-more\" href=\"\u002Fengine\u002Fperm\">Learn more \u003Ci class=\"fas fa-arrow-right\" aria-hidden=\"true\">\u003C\u002Fi>\u003C\u002Fa>\n        \u003C\u002Farticle>\n        \u003Carticle class=\"engine-card scroll-reveal\">\n          \u003Cdiv class=\"engine-card-head\">\n            \u003Cdiv class=\"engine-card-icon\">\u003Ci class=\"fas fa-clipboard-list\">\u003C\u002Fi>\u003C\u002Fdiv>\n            \u003Ch3>Form Engine\u003C\u002Fh3>\n          \u003C\u002Fdiv>\n          \u003Cp class=\"engine-card-lead\">Business-model-driven forms and list pages\u003C\u002Fp>\n          \u003Cul>\n            \u003Cli>Form models and advanced datasources\u003C\u002Fli>\n            \u003Cli>Form \u002F list designers (50+ widgets)\u003C\u002Fli>\n            \u003Cli>Model-service CRUD with HTTP\u002FSQL extensions\u003C\u002Fli>\n          \u003C\u002Ful>\n          \u003Ca class=\"engine-card-more\" href=\"\u002Fengine\u002Fform\">Learn more \u003Ci class=\"fas fa-arrow-right\" aria-hidden=\"true\">\u003C\u002Fi>\u003C\u002Fa>\n        \u003C\u002Farticle>\n        \u003Carticle class=\"engine-card scroll-reveal\">\n          \u003Cdiv class=\"engine-card-head\">\n            \u003Cdiv class=\"engine-card-icon\">\u003Ci class=\"fas fa-project-diagram\">\u003C\u002Fi>\u003C\u002Fdiv>\n            \u003Ch3>Workflow Engine\u003C\u002Fh3>\n          \u003C\u002Fdiv>\n          \u003Cp class=\"engine-card-lead\">Flowable + BPMN 2.0 approval and business flows\u003C\u002Fp>\n          \u003Cul>\n            \u003Cli>Competitive \u002F parallel \u002F serial sign-off and countersign\u003C\u002Fli>\n            \u003Cli>Assignees resolved from org or form fields\u003C\u002Fli>\n            \u003Cli>Inbox, instance monitoring and versioning\u003C\u002Fli>\n          \u003C\u002Ful>\n          \u003Ca class=\"engine-card-more\" href=\"\u002Fengine\u002Fflow\">Learn more \u003Ci class=\"fas fa-arrow-right\" aria-hidden=\"true\">\u003C\u002Fi>\u003C\u002Fa>\n        \u003C\u002Farticle>\n        \u003Carticle class=\"engine-card scroll-reveal\">\n          \u003Cdiv class=\"engine-card-head\">\n            \u003Cdiv class=\"engine-card-icon\">\u003Ci class=\"fas fa-chart-line\">\u003C\u002Fi>\u003C\u002Fdiv>\n            \u003Ch3>Report Engine\u003C\u002Fh3>\n          \u003C\u002Fdiv>\n          \u003Cp class=\"engine-card-lead\">Formatted reports, exports and big-screen dashboards\u003C\u002Fp>\n          \u003Cul>\n            \u003Cli>Report design, print and multi-format export\u003C\u002Fli>\n            \u003Cli>Dashboard and big-screen visualization\u003C\u002Fli>\n            \u003Cli>Business and external datasources supported\u003C\u002Fli>\n          \u003C\u002Ful>\n          \u003Ca class=\"engine-card-more\" href=\"\u002Fengine\u002Freport\">Learn more \u003Ci class=\"fas fa-arrow-right\" aria-hidden=\"true\">\u003C\u002Fi>\u003C\u002Fa>\n        \u003C\u002Farticle>\n        \u003Carticle class=\"engine-card scroll-reveal\">\n          \u003Cdiv class=\"engine-card-head\">\n            \u003Cdiv class=\"engine-card-icon\">\u003Ci class=\"fas fa-plug\">\u003C\u002Fi>\u003C\u002Fdiv>\n            \u003Ch3>Integration Engine\u003C\u002Fh3>\n          \u003C\u002Fdiv>\n          \u003Cp class=\"engine-card-lead\">Model APIs, service registration and system channels\u003C\u002Fp>\n          \u003Cul>\n            \u003Cli>Outbound model \u002F process APIs and auth templates\u003C\u002Fli>\n            \u003Cli>HTTP\u002FSQL services and scheduled jobs\u003C\u002Fli>\n            \u003Cli>WeCom \u002F DingTalk \u002F mail \u002F SMS channels\u003C\u002Fli>\n          \u003C\u002Ful>\n          \u003Ca class=\"engine-card-more\" href=\"\u002Fengine\u002Fintegration\">Learn more \u003Ci class=\"fas fa-arrow-right\" aria-hidden=\"true\">\u003C\u002Fi>\u003C\u002Fa>\n        \u003C\u002Farticle>\n      \u003C\u002Fdiv>\n      \u003Cp class=\"engines-block-bridge scroll-reveal\">Products sit on this foundation:\u003Ca href=\"\u002Fproduct\u002Fsrm\">SRM Procurement\u003C\u002Fa>、\u003Ca href=\"\u002Fproduct\u002Fwms\">WMS Warehouse\u003C\u002Fa>、\u003Ca href=\"\u002Fproduct\u002Fmes\">MES Manufacturing\u003C\u002Fa>、\u003Ca href=\"\u002Fproduct\u002Fqms\">QMS Quality\u003C\u002Fa>、\u003Ca href=\"\u002Fproduct\u002Fcrm\">CRM Customer Delivery\u003C\u002Fa>. The operating side can combine \u003Ca href=\"\u002Fproduct\u002Fpms\">PMS\u003C\u002Fa>、\u003Ca href=\"\u002Fproduct\u002Fehr\">EHR\u003C\u002Fa>。\u003Ca href=\"\u002Fproducts\">View products\u003C\u002Fa>\u003C\u002Fp>\n    \u003C\u002Fdiv>\n\n    \u003Cdiv class=\"engines-block engines-block--agent\">\n      \u003Ch3 class=\"engines-block-title scroll-reveal\" id=\"agent\">Dual Agents\u003C\u002Fh3>\n      \u003Cp class=\"engines-block-lead scroll-reveal\">Design-time delivers modeling. Runtime delivers query output and API-based handling. They are not the same chat window.\u003C\u002Fp>\n      \u003Cdiv class=\"agent-compare\">\n        \u003Carticle class=\"agent-panel scroll-reveal\">\n          \u003Cheader class=\"agent-panel-head\">\n            \u003Cspan class=\"ai-badge\">Design\u003C\u002Fspan>\n            \u003Ch3>Design-time agent\u003C\u002Fh3>\n          \u003C\u002Fheader>\n          \u003Cdl class=\"agent-facts\">\n            \u003Cdiv>\n              \u003Cdt>Who uses\u003C\u002Fdt>\n              \u003Cdd>Implementation, business, and custom development teams\u003C\u002Fdd>\n            \u003C\u002Fdiv>\n            \u003Cdiv>\n              \u003Cdt>What it does\u003C\u002Fdt>\n              \u003Cdd>Build\u002Fchange app categories, apps, modules, models, forms, lists\u002Fpages, reports, dashboards, and flows in natural language; developers can use ⌘K for scripts\u002FSQL\u003C\u002Fdd>\n            \u003C\u002Fdiv>\n            \u003Cdiv>\n              \u003Cdt>What you get\u003C\u002Fdt>\n              \u003Cdd>Real objects you can refine in the designer and then publish\u003C\u002Fdd>\n            \u003C\u002Fdiv>\n          \u003C\u002Fdl>\n        \u003C\u002Farticle>\n        \u003Carticle class=\"agent-panel scroll-reveal\">\n          \u003Cheader class=\"agent-panel-head\">\n            \u003Cspan class=\"ai-badge runtime\">Runtime\u003C\u002Fspan>\n            \u003Ch3>Runtime agent\u003C\u002Fh3>\n          \u003C\u002Fheader>\n          \u003Cdl class=\"agent-facts\">\n            \u003Cdiv>\n              \u003Cdt>Who uses\u003C\u002Fdt>\n              \u003Cdd>Executives, business owners, and authorized operations roles\u003C\u002Fdd>\n            \u003C\u002Fdiv>\n            \u003Cdiv>\n              \u003Cdt>What it does\u003C\u002Fdt>\n              \u003Cdd>Query results appear as in-dialog text and charts and can be exported to Office, HTML, or Markdown. Creating data and completing reviews go through business APIs.\u003C\u002Fdd>\n            \u003C\u002Fdiv>\n            \u003Cdiv>\n              \u003Cdt>What you get\u003C\u002Fdt>\n              \u003Cdd>Exports match that retrieval. Creating data and completing reviews stay within the user's permissions and do not write to the database directly.\u003C\u002Fdd>\n            \u003C\u002Fdiv>\n          \u003C\u002Fdl>\n        \u003C\u002Farticle>\n      \u003C\u002Fdiv>\n      \u003Cp class=\"agent-note scroll-reveal\">Configuration and permissions are completed and published in design-time. Runtime can query and export, and can create data or complete reviews through business APIs. It does not write to the database directly and does not exceed the user's permissions.\u003C\u002Fp>\n      \u003Cp class=\"engine-block-cta scroll-reveal\">\u003Ca class=\"engine-card-more\" href=\"\u002Fengine\u002Fagent\">View dual-agent details \u003Ci class=\"fas fa-arrow-right\" aria-hidden=\"true\">\u003C\u002Fi>\u003C\u002Fa>\u003C\u002Fp>\n\n      \u003Cfigure class=\"engine-figure scroll-reveal\">Design-time and runtime, admin console and app center overview\u003C\u002Ffigure>\n    \u003C\u002Fdiv>\n\n    \u003Cdiv class=\"engines-block\">\n      \u003Ch3 class=\"engines-block-title scroll-reveal\" id=\"stack\">Technical architecture\u003C\u002Fh3>\n      \u003Cp class=\"engines-block-lead scroll-reveal\">Front and back ends are separate. Deployment can be private or in the cloud. Databases and clouds are chosen per project.\u003C\u002Fp>\n      \u003Cdiv class=\"i18n-points scroll-reveal\">\n        \u003Cdiv>\u003Cstrong>Application architecture\u003C\u002Fstrong>\u003Cspan>Vue on the front end and Spring Cloud microservices on the back end. Design-time configures forms, processes, reports, and large screens, which enter runtime after release.\u003C\u002Fspan>\u003C\u002Fdiv>\n        \u003Cdiv>\u003Cstrong>Runtime and deployment\u003C\u002Fstrong>\u003Cspan>Nginx OpenResty and the gateway sit at the edge, with Nacos for service registry. Docker, Kubernetes, on-premises, and private cloud are supported.\u003C\u002Fspan>\u003C\u002Fdiv>\n        \u003Cdiv>\u003Cstrong>Process standard\u003C\u002Fstrong>\u003Cspan>Built on Flowable and BPMN 2.0. Approval, workflow, and data flows share one definition, and node permissions bind to the form.\u003C\u002Fspan>\u003C\u002Fdiv>\n        \u003Cdiv>\u003Cstrong>Databases\u003C\u002Fstrong>\u003Cspan>Oracle, SQL Server, MySQL, Dameng, and other relational databases can be used. Cache, message queue, and log collection are chosen per project.\u003C\u002Fspan>\u003C\u002Fdiv>\n        \u003Cdiv>\u003Cstrong>Integration\u003C\u002Fstrong>\u003Cspan>Connect through model services, HTTP, and Web Service. SAP, Yonyou U9, Digiwin T100, and PLM can be linked.\u003C\u002Fspan>\u003C\u002Fdiv>\n        \u003Cdiv>\u003Cstrong>Endpoints\u003C\u002Fstrong>\u003Cspan>One design covers PC web and desktop, plus app, mini program, official account, WeCom, DingTalk, and H5.\u003C\u002Fspan>\u003C\u002Fdiv>\n      \u003C\u002Fdiv>\n    \u003C\u002Fdiv>\n\n    \u003Cdiv class=\"engines-block\">\n      \u003Ch3 class=\"engines-block-title scroll-reveal\" id=\"i18n\">Multi-language\u003C\u002Fh3>\n      \u003Cp class=\"engines-block-lead scroll-reveal\">One-time modeling, multilingual operation; about 49 business language directories, which are enabled by the tenant, manually maintained translations, missing translations and falling back to the original text\u003C\u002Fp>\n      \u003Cdiv class=\"i18n-points scroll-reveal\">\n        \u003Cdiv>\u003Cstrong>Language catalog\u003C\u002Fstrong>\u003Cspan>Includes right-to-left scripts; you can start with Chinese only\u003C\u002Fspan>\u003C\u002Fdiv>\n        \u003Cdiv>\u003Cstrong>Human-maintained translations\u003C\u002Fstrong>\u003Cspan>Maintained per page; switches take effect immediately\u003C\u002Fspan>\u003C\u002Fdiv>\n        \u003Cdiv>\u003Cstrong>Tenant-selected\u003C\u002Fstrong>\u003Cspan>Default language configurable; expandable for global markets\u003C\u002Fspan>\u003C\u002Fdiv>\n      \u003C\u002Fdiv>\n      \u003Cdiv class=\"lang-chips scroll-reveal\" aria-label=\"Language samples\">\n        \u003Cspan class=\"lang-chip\">Chinese\u003C\u002Fspan>\n        \u003Cspan class=\"lang-chip\">English\u003C\u002Fspan>\n        \u003Cspan class=\"lang-chip\">العربية\u003C\u002Fspan>\n        \u003Cspan class=\"lang-chip\">日本語\u003C\u002Fspan>\n        \u003Cspan class=\"lang-chip\">Español\u003C\u002Fspan>\n      \u003C\u002Fdiv>\n    \u003C\u002Fdiv>\n\n    \u003Cdiv class=\"engines-block\">\n      \u003Ch3 class=\"engines-block-title scroll-reveal\" id=\"saas\">SaaS Multi-tenant\u003C\u002Fh3>\n      \u003Cp class=\"engines-block-lead scroll-reveal\">Suitable for group subsidiaries, partner operations and multi-delivery centers in parallel\u003C\u002Fp>\n      \u003Col class=\"saas-flow scroll-reveal\">\n        \u003Cli>\u003Cem>01\u003C\u002Fem>\u003Cstrong>Apply\u003C\u002Fstrong>\u003Cspan>Submit account details and contact person\u003C\u002Fspan>\u003C\u002Fli>\n        \u003Cli>\u003Cem>02\u003C\u002Fem>\u003Cstrong>Onboard\u003C\u002Fstrong>\u003Cspan>Assign codes, domains, and runtime environments\u003C\u002Fspan>\u003C\u002Fli>\n        \u003Cli>\u003Cem>03\u003C\u002Fem>\u003Cstrong>Run\u003C\u002Fstrong>\u003Cspan>Tenant-level isolation with optional dedicated data environments\u003C\u002Fspan>\u003C\u002Fli>\n        \u003Cli>\u003Cem>04\u003C\u002Fem>\u003Cstrong>Deactivate\u003C\u002Fstrong>\u003Cspan>Expiry, freeze, or deactivation with a controlled lifecycle\u003C\u002Fspan>\u003C\u002Fli>\n      \u003C\u002Fol>\n    \u003C\u002Fdiv>\n\n    \u003Cdiv class=\"engines-cta scroll-reveal\">\n      \u003Cp>The engine and agent are ready to see the recent evolution or directly into the product landing\u003C\u002Fp>\n      \u003Cdiv class=\"engines-cta-actions\">\n        \u003Ca href=\"\u002Fupdates\" class=\"btn btn-outline\">Updates\u003C\u002Fa>\n        \u003Ca href=\"\u002Fproducts\" class=\"btn\">View products\u003C\u002Fa>\n        \u003Ca href=\"\u002Fcontact?from=platform\" class=\"btn btn-outline\">Book a Meeting\u003C\u002Fa>\n      \u003C\u002Fdiv>\n    \u003C\u002Fdiv>\n  \u003C\u002Fsection>\n\n  \u003C!-- GEO:faq-visible:BEGIN · 由 scripts\u002Finject_geo.py 生成，请勿手改 -->\n  \u003Csection class=\"contact-faq page-section\" id=\"faq\">\n    \u003Ch2 class=\"section-title\">FAQ\u003C\u002Fh2>\n    \u003Cp class=\"section-subtitle\">Common platform and agent questions—start here; still stuck? Contact us.\u003C\u002Fp>\n    \u003Cdiv class=\"faq-list\">\n        \u003Cdetails class=\"faq-item\" open>\n          \u003Csummary>What are JEDP’s six engines?\u003C\u002Fsummary>\n          \u003Cp>Organization, Permission, Form, Workflow, Report, and Integration—covering org master data, authorization, modeling\u002FUI, approvals\u002Fflows, reporting\u002Fdashboards, and system connectivity.\u003C\u002Fp>\n        \u003C\u002Fdetails>\n        \u003Cdetails class=\"faq-item\">\n          \u003Csummary>How do the six engines relate to the product lines?\u003C\u002Fsummary>\n          \u003Cp>The six engines are the shared foundation. Seven product lines sit on it and can go live one at a time. Combined use does not create a second organization, permission model, or master-data set. The agents sit on the foundation—design-time modeling, and runtime query, export, and handling—and are not a seventh engine.\u003C\u002Fp>\n        \u003C\u002Fdetails>\n        \u003Cdetails class=\"faq-item\">\n          \u003Csummary>What are the dual agents?\u003C\u002Fsummary>\n          \u003Cp>Design-time uses natural language to build or change application categories, apps, modules, form models, and page or process configuration (⌘K assists scripts and SQL). Results must enter the designer for review before publish. Runtime, within authorization, answers questions as in-dialog text and charts or as Office, HTML, and Markdown, and creates data or completes reviews through business APIs. It does not write to the database directly and does not exceed the user's permissions.\u003C\u002Fp>\n        \u003C\u002Fdetails>\n        \u003Cdetails class=\"faq-item\">\n          \u003Csummary>Does it support multilingual and overseas rollout?\u003C\u002Fsummary>\n          \u003Cp>Yes. About 49 language catalogs are built in; tenants opt in, with fallback to the source string. Delivered locales include Simplified Chinese, Traditional Chinese, and English.\u003C\u002Fp>\n        \u003C\u002Fdetails>\n        \u003Cdetails class=\"faq-item\">\n          \u003Csummary>Does it support multi-organization and multi-tenant?\u003C\u002Fsummary>\n          \u003Cp>Yes. SaaS multi-tenant covers the full lifecycle with tenant-level isolation—fit for multi-plant and multi-subsidiary groups.\u003C\u002Fp>\n        \u003C\u002Fdetails>\n        \u003Cdetails class=\"faq-item\">\n          \u003Csummary>What is JEDP's technical architecture?\u003C\u002Fsummary>\n          \u003Cp>Front and back ends are separate: Vue and Spring Cloud microservices, deployable with Docker or Kubernetes, or on-premises and in a private cloud. The edge is Nginx OpenResty and the gateway. The registry is Nacos. Processes use Flowable and BPMN 2.0. Databases and cloud are chosen per project.\u003C\u002Fp>\n        \u003C\u002Fdetails>\n    \u003C\u002Fdiv>\n  \u003C\u002Fsection>\n  \u003C!-- GEO:faq-visible:END -->\n\n  \n  \n  \n  \n  \u003C!-- GEO:faq:BEGIN · 由 scripts\u002Finject_geo.py 生成，请勿手改 -->\n  \n  \u003C!-- GEO:faq:END -->",1793937990053]