统一业务台账首屏布局(05-30-fix-payment-ledger-layout-consistency)
这个提交包含在:
@@ -280,8 +280,9 @@ pages must pick one primary template before implementation:
|
||||
- `业务台账列表`: reimbursement, contracts, projects, payments, AP and invoices.
|
||||
Page-header primary action, command bar, list/table body and folded ledger
|
||||
tools.
|
||||
- `主从工作台`: procurement, assets and inventory checks. Left/index list plus
|
||||
right/current-object detail and actions.
|
||||
- `主从工作台`: only for true task execution after an explicit user selection,
|
||||
such as an inventory-check task that has been opened. It is not the default
|
||||
first screen for procurement, assets, payments, AP or invoices.
|
||||
- `详情工作区`: reimbursement detail, workflow task detail, project detail and
|
||||
future contract detail. Overview, facts/evidence, right-side summary/command
|
||||
panel and history.
|
||||
@@ -297,9 +298,11 @@ pages must pick one primary template before implementation:
|
||||
- Mobile is the responsive expression of these templates: top status/focus,
|
||||
card list or sectioned detail, bottom primary action. Do not create a PC shell
|
||||
inside mobile routes.
|
||||
- B-class business pages should usually choose `业务台账列表` or `主从工作台`.
|
||||
Use a ledger when records open into details; use master-detail when users
|
||||
select one object and edit/process it in the same workspace.
|
||||
- B-class business pages should usually choose `业务台账列表`. Procurement,
|
||||
assets, payments, AP and invoices must start as a list and open details only
|
||||
through an explicit row action, `?id=` detail mode, drawer or detail route.
|
||||
Use `主从工作台` only for explicit execution tasks, and never auto-select the
|
||||
first item merely to fill a detail column.
|
||||
- A-class task pages must not drift into configuration surfaces. C-class
|
||||
configuration pages must not appear as ordinary employee task pages.
|
||||
|
||||
|
||||
在新工单中引用
屏蔽一个用户