Visio Error - Source and Target must not be the same

[Brian P]

Hi all, 

can't seem to figure out why Visio is giving  an error when I check the attached diagram. It tells me the source and target cannot be the same. It's my understanding that the inclusive gateways below read:

First gateway - "take one path or the other or both "

Second gateway "wait until whatever paths initiated are finished until moving onto next steps"

Also, I'm new to this forum, does anybody know how to imbed a diagram in the body of the text of one of these posts like I have seen on other posts here so that people won't have to click a link to open my diagrams ?

thanks in advance for any help

Brian

[Neal McWhorter]

Brian,

I don't see anything wrong with this but I suspect that Visio is not handling the flows from error boundary events correctly. Just as a note... You're using error events which have a well defined meaning in the execution context (destroy existing activity and discard unsaved work and transfer control the the exception flow path) to mean something closer to a "business exception" from what I gather. There's nothing wrong with doing this... I do something similar myself... but this is a good illustration of the difference between applying BPMN per the spec for execution reasons and applying it for communication reasons. When making these kinds of decisions to give differing semantics to BPMN symbols for use in communication I define a separate style guide that essentially tailors the BPMN standard for communications purposes so that there is a consistent semantic within an organization. 

Neal

-- 

	Experience + Leadership
Neal McWhorter | Connect with me on Linkedin Business Architecture Guild Board Member neal.mc...@strategicvaluepartners.com www.strategicvaluepartners.com	Strategic Value Partners, Inc. Chicago, Illinois Tel: 773-570-0020

--
--
You received this message because you are subscribed to the Google
Groups "BPMN Forum" group.
Public website: http://www.bpmnforum.com
To post to this group, send email to BPMN...@googlegroups.com
To unsubscribe from this group, send email to
BPMNforum+...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/BPMNforum?hl=en_US?hl=en

---
You received this message because you are subscribed to the Google Groups "BPMN Forum" group.
To unsubscribe from this group and stop receiving emails from it, send an email to BPMNforum+...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Brian P]

Hi Neal, 

thanks for your help. I ended up just deleted the second inclusive gateway and putting it right back in again and hey presto Visio was happy ....  Thanks for the tip on the error event treatment and setting up a Style Guide - very helpful. 

Much appreciated. 

Brian

On Saturday, February 13, 2016 at 3:00:58 AM UTC+11, neal wrote:

Brian,

I don't see anything wrong with this but I suspect that Visio is not handling the flows from error boundary events correctly. Just as a note... You're using error events which have a well defined meaning in the execution context (destroy existing activity and discard unsaved work and transfer control the the exception flow path) to mean something closer to a "business exception" from what I gather. There's nothing wrong with doing this... I do something similar myself... but this is a good illustration of the difference between applying BPMN per the spec for execution reasons and applying it for communication reasons. When making these kinds of decisions to give differing semantics to BPMN symbols for use in communication I define a separate style guide that essentially tailors the BPMN standard for communications purposes so that there is a consistent semantic within an organization. 

Neal

-- 

	Experience + Leadership

Neal McWhorter | Connect with me on Linkedin Business Architecture Guild Board Member

neal.mcwhorter@strategicvaluepartners.com www.strategicvaluepartners.com