refactor: 简化工作台上手入口和个人设置(portal-onboarding-profile-simplification)
这个提交包含在:
@@ -236,6 +236,33 @@ and admin tools available without dominating the default path.
|
||||
asserting the task surface, primary action and secondary/advanced entry
|
||||
behavior.
|
||||
|
||||
## Convention: Workbench Onboarding And Profile Scope
|
||||
|
||||
**What**: PC workbench and account settings should stay task-first, not become
|
||||
training or permission-maintenance surfaces:
|
||||
|
||||
- Do not add a persistent `快速上手` / onboarding checklist to the workbench by
|
||||
default. If first-login guidance is needed, use a dismissible welcome dialog
|
||||
with at most three real business entries.
|
||||
- Welcome or onboarding entries must point to executable user tasks, such as
|
||||
`处理待办`, `提交报销` or `请假`; do not use explanatory entries like
|
||||
`了解流程`, and do not route users to settings or notifications as a
|
||||
substitute for task guidance.
|
||||
- `个人设置` default content is account identity, notification preference and
|
||||
Enterprise WeChat binding. Organization, report line and role summary may be
|
||||
folded under `账号详情`; permission code lists and full employee dossier fields
|
||||
stay out of the default view.
|
||||
|
||||
**Why**: Small teams need fewer default decisions. Persistent onboarding and
|
||||
permission-heavy profile pages make ordinary users inspect system internals
|
||||
before doing work.
|
||||
|
||||
**Tests Required**:
|
||||
|
||||
- Focused Playwright coverage for changed workbench or profile routes.
|
||||
- Screenshot evidence for first-login welcome, workbench first screen and
|
||||
profile default view when changing these surfaces.
|
||||
|
||||
## Convention: Detail And Mobile Command Surfaces
|
||||
|
||||
**What**: PC detail pages and notification-like flows should reuse the Wave3
|
||||
|
||||
在新工单中引用
屏蔽一个用户