知识卡片
抽取子流程保持粒度
主流程中的任务应处于接近的抽象层次。若CRM接入需要先创建、再补资料、异步等待与重试,可抽为独立流程,减少主模型技术噪声并支持复用。但只能在同一服务边界内使用子流程;全局共享能力可能应成为API服务。过度细分又会增加导航负担,并使取消等回退行为难表达。
这张卡片看不懂?
这张卡片已通过人工审查,不再接受失败反馈。
已有反馈 · 0 条
还没有人提交反馈。
在整书笔记中的位置
原书出处 · 1 处
- 业务与IT协作 · 查看原书依据
Figure 10-10 shows a separate process handling these specifics, to avoid polluting the main application process. The technical details to call the CRM system are extracted into a separate model and invoked from the application process. This way, you keep the same level of details for all tasks in the onboarding process, making that model
参考来源
- 位置:《Practical Process Automation》第10章《业务与IT协作》(来源项目:book-sources;源文件:extracted/Practical Process Automation (Bernd Ruecker)/_epub-src/OEBPS/ch10.xhtml)
- 结论依据:原文给出的机制、实例与边界支持本卡的解释。
- 原始内容:Figure 10-10 shows a separate process handling these specifics, to avoid polluting the main application process. The technical details to call the CRM system are extracted into a separate model and invoked from the application process. This way, you keep the same level of details for all tasks in the onboarding process, making that model