What A Plugin App Usually Includes
Common Business Domains
Plugin Apps are grouped by business domain. Common domains include:
Currently listed Plugin Apps include:
How To Choose A Plugin App
When choosing a Plugin App, check whether:- The App matches the target business domain and real workflow.
- It provides Workbench views for human review and operations.
- Assistant tools have clear call order, input structure, and evidence requirements.
- Permission boundaries separate normal use, write operations, and administrator capabilities.
- It can reuse UOSE Knowledgebase, ontology resources, audit, and organization permissions.
- It has official or partner maintenance guidance for upgrades and troubleshooting.
How To Develop A Plugin App
To develop a UOSE Plugin App, use the AI product plugin development system instead of scattering business logic across prompts or temporary scripts. Recommended references: A UOSE business App usually needs to:- Define plugin metadata, icon, target products, and marketplace content.
- Declare
targetApps: ['data-xpert']andtargetAppMetato describe views, tools, business App capabilities, templates, and permissions. - Register a server module with entities, services, Agent middleware, and a Workbench view provider.
- Split core business actions into explicit, retryable, and auditable Assistant tools.
- Provide Workbench views or Remote Components for workflows that need human review.
- Contribute business Assistant templates so users can create a usable Assistant in one step.
- Configure permissions, defaults, publishing, and upgrade guidance.