英文:
BPMN Intermediate Events Attached to an Activity Boundary
问题
我应该绘制图表 - 示例A或示例B或两者都可以吗？在示例A中有一个事件，一个额外的任务，并且过程回到主流程中。示例B - 如果事件发生，过程不会回到主流程。是否可以像示例A中那样绘制过程？示例附上。提前感谢您的帮助。 
我绘制了示例（附上）并查阅了BPMN规范，但仍然有疑虑。
英文:
how would you drow diagram - example A or Example B or both are fine? In Example A there is an event, one extra task and process is back in the main flow. Example B - if the event occurs process is not back in main flow. Is it correct to draw process like in example A? Examples enclosed. Thank you in advance for help.
I draw examples (enclosed) and checked in BPMN specification but still have doubs.
答案1
得分: 1
我认为可以再进一步，将“应用程序分析”前面放置一个网关，然后从消息事件连接到该网关（因此该网关仅用于合并，不需要条件，这是最佳实践，你也可以直接从消息事件返回到任务本身，这将表达相同的意思）。
基本的原因是，除非在工作流程中真的处于不同阶段，否则在图表中不应该有多个相同的任务。
然而，这与您的工作流程不完全相同，因为这样客户可以多次更改贷款金额，而不仅仅是一次。
存在一些问题：
-
我认为您希望将消息事件设置为中断，否则您将同时批准原始贷款和更改后的贷款。
-
在“应用程序分析”之后，可能应该有一个网关，检查分析结果，只有在分析结果正确时批准贷款。
英文:
I would go a step further and put a gateway in front of "Application Analysis" and then draw the arrow from the message event to that gateway (so the gateway is only used to join, doesn't need a condition, it is best practice, you could draw the arrow from the message event directly back on the task itself and it would express the same thing).
The basic reasoning is that you shouldn't have multiple tasks for the same thing in the diagram unless it is really at a different stage in the workflow.
However it isn't exactly the same as your workflow, because like this the customer could change the loan amount multiple times and not just once.
There are some problems:
-
I think you want to make the message event interrupting, otherwise you grant both loans, the original one and the changed one.
-
After "Application Analysis" there should probably be a gateway that checks the result of the analysis and only if it was ok you grant the loan.
通过集体智慧和协作来改善编程学习和解决问题的方式。致力于成为全球开发者共同参与的知识库，让每个人都能够通过互相帮助和分享经验来进步。
评论