Hi BigD!

When you say that the "Initial Submit" activity is using its own Outcome field, you don't mean the one attached to that activity in particular, correct? It's actually form XML? There is no client event in your "Initial Submit" activity so the actual "Outcome" field for the activity would never get set (it wouldn't even get created unless you manually create it).

Have you checked the report for the process instance in question to confirm the form actually has the XML value you're looking for set at the time this line rule executes?

Can you attach a screenshot of your line rule? Or at least describe exactly how it's set?

Assuming the XML value is getting set as expected, the problem has to be with the line rule coming from "Initial Submit" to "In Progress".

HTH,

Tyler

The initial outcome is set in the form by the user in a drop-down with manual entries. No activity owns that field. The line rules coming out of the Initial Submit activity are looking at that field. They worked fine before I added the InfoPathClient event to the In Progress activity. While I was building and testing, that activity simply held a placeholder event (dead end). Just to be clear, with the process as-is:

Initial Submit to Submit to Technical Review: works

Initial Submit to In Progress: fails

Thanks for making me look at that line rule, 'cause the answer was right there: the field name was wrong. As for the looping activity, I deleted the Infopath event and rebuilt it from scratch and that seemed to fix that.

When all else fails, delete and start over, I guess!