artifact: add FPA analysis outputs through round 6
This commit is contained in:
@@ -0,0 +1,42 @@
|
||||
---
|
||||
artifact_type: feature
|
||||
slug: supplement-request-response
|
||||
round: 4
|
||||
status: draft
|
||||
project: maxcpa
|
||||
title: 补件响应处理
|
||||
---
|
||||
|
||||
# 补件响应处理
|
||||
|
||||
## Page
|
||||
|
||||
- 资料提交与进度页
|
||||
|
||||
## Persona Served
|
||||
|
||||
- Client
|
||||
|
||||
## Business Responsibility
|
||||
|
||||
在客户收到缺件提醒后,把缺什么、为什么缺、下一步怎么补说清楚,并支持客户直接完成补件响应。
|
||||
|
||||
## State Type
|
||||
|
||||
- both
|
||||
|
||||
## Cross-Page Reuse
|
||||
|
||||
- 是,可与会计师端提醒编排能力共用提醒结果。
|
||||
|
||||
## Source Story
|
||||
|
||||
- `客户 / Activity 4 / Step 3`: 在收到提醒后补齐缺失内容
|
||||
|
||||
## Independence Signals
|
||||
|
||||
- 有独立业务目的:推动提醒后的补件闭环。
|
||||
- 有独立数据来源:提醒事件、缺件原因、资料状态。
|
||||
- 有独立交互流:查看提醒、进入补件、完成再提交。
|
||||
- 有跨页面复用潜力:与会计师提醒能力天然关联。
|
||||
- 可独立测试:可覆盖单项补件、多项补件和重复提醒场景。
|
||||
Reference in New Issue
Block a user