bos-features-index

Indexes Kingdee K/3 Cloud BOS platform customization capabilities and tool coverage boundaries.

24|7|Updated Apr 20, 2026
One-click install
npx skills add https://github.com/qiaolei227/opendeploy --skill bos-features-index-qiaolei227
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: bos-features-index
Source: https://github.com/qiaolei227/opendeploy/tree/main/knowledge/skills/k3cloud/bos-features-index
Command: npx skills add https://github.com/qiaolei227/opendeploy --skill bos-features-index-qiaolei227

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? When an ERP implementation requirement exceeds standard Kingdee K/3 Cloud features, consultants and AI agents need to know two things: whether the BOS platform itself can handle it, and whether the OpenDeploy toolset currently automates it. This Skill separates those two answers so users get correct guidance instead of over-promised automation. ## Core Features & Use Cases - Capability index: Maps 8+ BOS capability categories (extension objects, custom fields, entry entities, business rules, convert rules, approval workflows, operations/buttons, plugin types) to their automation status. - Decompiled engineering references: Provides reverse-engineered models of EntityServiceRule, ConvertRuleElement, FieldMapElement, and FKERNELXML serialization verified against Kingdee.BOS.Core.dll and live databases. - Customization-level decision tree: Guides selection among extension fields, business rules, convert rules, approval flows, and Python plugins based on requirement type. - Use Case: A consultant asks whether a sales order can auto-calculate amounts and push to a delivery notice. The Skill identifies business rules and convert rules as the right BOS layers, then states which parts OpenDeploy automates versus which require manual BOS Designer configuration. ## Quick Start Ask whether a specific K/3 Cloud customization requirement can be solved by BOS configuration and which parts OpenDeploy automates.

Frequently Asked Questions about bos-features-index

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I decide between BOS business rules and Python plugins in K/3 Cloud?▼

Use business rules for field calculations and multi-field linkage expressible in one IronPython expression. Use Python form plugins only for event-driven logic like BeforeSave validation, cross-document queries, or external API calls that rules cannot handle.

What BOS capabilities does OpenDeploy currently automate?▼

OpenDeploy automates extension lifecycle, custom fields across 12 types, entry entity and tab operations, Python form plugin registration, and enum types. Business rules, convert rules, approval flows, print templates, and permissions remain manual BOS Designer tasks.

Can K/3 Cloud business rules use SQL functions like IIF or CONCAT?▼

No. BOS expressions are an IronPython 2.7 subset, not SQL. Use ternary expressions instead of IIF, string concatenation with + instead of CONCAT, and .NET methods like AddDays instead of DATEADD.

How are K/3 Cloud convert rules stored and queried?▼

Convert rules live in T_META_CONVERTRULE with FKERNELXML containing a ConvertRuleElement and up to 10 ConvertPolicy subclasses. They can be read via the Metadata.ConvertService GetAllPaths and GetConvertRule JSON RPC endpoints without direct SQL.

Why do field value update rules not fire during document push-down?▼

Document conversion bypasses field value updates and entity service rules entirely; values are copied directly. Calculations during conversion must be attached as form service strategies on the convert rule itself.