关于BPMN同一池内泳道间通知实现方式的技术问询

Great question—this is a common point of confusion when mapping intra-pool workflows, and the answer boils down to how explicit you need the process logic to be, based on your business context.

Let’s break down the two valid approaches, and when to use each:

1. Use a Dedicated Task for the Notification #

You absolutely can create a task like "Notify Admin of Shipped Order" (similar to your cross-pool example) for intra-lane communication. This is the right choice when:

• The notification is a distinct, intentional action requiring work from the sender (e.g., the seller has to compose an internal message, fill out a notification form, or manually trigger a system alert).
• You need to track that the notification was sent (for audit trails, accountability, or process metrics).
• The notification triggers a specific, verifiable response from the recipient (e.g., the admin must acknowledge receipt before proceeding).

Treating the notification as a task makes the workflow transparent—anyone reading the diagram immediately sees that the seller has a clear responsibility to initiate communication, rather than it being an implicit side effect.

2. Rely on Process Entity Flow (No Separate Task) #

In many cases, you don’t need a dedicated notification task—you can let the flow of the process itself serve as the "notification." This works when:

• The notification is a natural consequence of the process moving forward (e.g., once the seller completes the "Mark Order as Shipped" task, the order record automatically moves to the admin’s lane for follow-up).
• The recipient’s next task directly signals the status change (e.g., the admin sees a "Process Shipment Confirmation" task in their lane, which inherently tells them the order was shipped).

This approach keeps the diagram cleaner, avoiding cluttering the flow with redundant steps when the intent is already clear from the sequence of tasks.

Key BPMN Principle to Follow #

At the end of the day, BPMN is about clear communication of business logic. Choose the approach that best aligns with how your team actually works:

• If the notification is a discrete action your team performs, model it as a task.
• If the notification is just a byproduct of the process moving from one lane to another, stick to the entity flow.

Just make sure you’re consistent across your diagrams—your team should agree on which approach to use for similar scenarios to avoid confusion.

内容的提问来源于stack exchange，提问作者Matnagra