Implementers Guide: Flaw in Car Repair flow?

[GoogleCodeExporter]

On a more careful review, based on the model we have right now, it appears that 
all New Issue(s) Found (1st loop back) are automatically rejected (as a result 
of "Handle New Found Issue"), which is different than what we are saying in the 
Process Description (2.1.1/3.b).
Am I correct?

Assuming I'm right, to fix this we'd need another decision (Data-based 
exclusive) Gateway after "Handle...", with 2 outcomes: Approve, Reject...

Is the meaning of "Handle New Found Issue" task really "Add (or Don't add) the 
New Issue to the Issues List"? Or, "Estimate cost of New Issue" (which would 
demand a decision whether or not to add it to the Issues List)?
Bottom line, at least in my understanding, it is quite ambiguous and I suggest 
we clarify it... unfortunately, can't suggest a change, since I'm not entirely 
clear what the intent is/was in that loop.

If I'm entirely wrong, apologies for the long digression.

Original issue reported on code.google.com by razvan.r...@wwhc.us on 8 Mar 2013 at 5:38

[GoogleCodeExporter]

- Remove the existing labels on the sequence flow out of Handle New Found Issues

Original comment by dga...@trisotech.com on 28 Mar 2013 at 3:02

• Changed state: Decided

[GoogleCodeExporter]

- Remove the existing labels on the sequence flow out of Handle New Found Issues

Original comment by dga...@trisotech.com on 28 Mar 2013 at 3:02

• Changed state: Decided

[GoogleCodeExporter]

Original comment by dga...@trisotech.com on 28 Mar 2013 at 7:24

• Changed state: Applied