统一业务台账首屏设计(05-30-unified-page-design-review)
这个提交包含在:
@@ -74,6 +74,23 @@ reference, not a copy of Feishu or Ant Design branding.
|
||||
action, visible common filters, table/card list and right-side operation
|
||||
column. `台账工具` contains export, batch, statistics, templates, full-scope
|
||||
views and advanced filters.
|
||||
- Business ledger first screens are single-column list pages. Do not use a
|
||||
default left-list/right-detail workspace for procurement, contracts, projects,
|
||||
assets, payments, AP or invoices. Open details through a detail route, drawer
|
||||
or explicit detail/edit area after the user chooses a row; the initial list
|
||||
page must not auto-select the first item just to fill a second column.
|
||||
- Ledger status summaries use tabs, segmented controls or compact chips with
|
||||
counts. Do not place four or five large status cards above ordinary business
|
||||
lists, and do not put explanatory sentences inside status cards.
|
||||
- Ledger filters fit the first PC row around `search`, `status` and `scope`
|
||||
when those capabilities exist. Supplier, legal entity, cost center, date
|
||||
ranges, contract type, sensitivity, export and test-data toggles belong in
|
||||
`筛选`, `台账工具` or a tab-specific advanced area; default-visible filters
|
||||
should not occupy multiple rows.
|
||||
- Business list columns show object identity, counterpart/person, amount/date,
|
||||
state and operation. `下一步` is not a default list column or right-side help
|
||||
panel. Use short state labels such as `待补材料` or `待你处理`; longer guidance
|
||||
belongs in detail pages, exception blocks or confirmations.
|
||||
- PC detail pages use an Ant Design Pro style detail workspace: top summary,
|
||||
main facts/details/evidence, right-side state and action panel, and bottom
|
||||
history. Do not build PC details as a free stack of equal-weight large cards.
|
||||
@@ -93,10 +110,10 @@ reference, not a copy of Feishu or Ant Design branding.
|
||||
|
||||
| Surface | Template | First-screen content | Primary action rule |
|
||||
| --- | --- | --- | --- |
|
||||
| `工作台` | 工作台总览 | 待办摘要、常用业务入口、必要提醒 | No forced header action. Use `去处理`, `新建报销`, `查看全部` inside relevant sections. |
|
||||
| `工作台` | 工作台总览 | Compact counts, common entries, real reminders | No forced header action. Use `去处理`, `新建报销`, `查看全部` inside relevant sections; do not show helper sentences for ordinary items. |
|
||||
| `待我处理` | 任务处理列表 | `待处理` / `已处理` tabs, count, minimal filters, task list | Row action is `处理`; `已处理记录` is a tab, not a separate header button. |
|
||||
| `审批详情` | 详情工作区 | Summary, facts/evidence, right summary/action panel, history | One action bar: primary `通过`, secondary `退回`/`驳回`, `转审` in `更多`. |
|
||||
| `报销` / `采购` / `合同` / `项目` / `资产` / `付款` / `应付账款` / `票据` | 业务台账列表 | Common filters plus table/card list | Header creation only when the route owns creation; risky tools in `台账工具` or detail. |
|
||||
| `报销` / `采购` / `合同` / `项目` / `资产` / `付款` / `应付账款` / `票据` | 业务台账列表 | One-row common filters plus table/card list | Header creation only when the route owns creation; risky tools in `台账工具` or detail; no default left-list/right-detail split. |
|
||||
| Business details | 详情工作区 | Summary, facts, evidence, relations, history | Right-side state/action panel on PC; bottom primary action on mobile. |
|
||||
| `管理` | 管理配置页 | Grouped landing: `人员组织`, `审批流程`, `基础资料`, `系统设置`, `审计排障` | Management subpages use search/filter, table and right operation column. |
|
||||
| `个人设置` | 管理配置页 variant | `个人资料`, `账号安全`, `通知偏好`, `企业微信绑定` | No employee dossier, permission matrix or org maintenance in the default profile path. |
|
||||
|
||||
在新工单中引用
屏蔽一个用户