Publication has failed

Question

In BPM studio 10g, a process has 4 interactive activities. After activity A, there is a conditional gateway. In each brunch, there is an interactive activity. Then, it is the final interactive activity.
I set the runtime property of all activities to user select transition. However, it shows error as follow:
The project publication has failed. Reason: This activity has the user select transition property enabled and has outgoing transitions with measurement marks or outgoing tranitions that target a conditional activity.
Then, I unselect the select transition of activity 1. It works.
However, the participant of the activity 1 cannot select the participant before send the activity.
How to let the participant of the fist activity can select the participant before sending?
Thanks

Answer 1

Hi Ye,
Others will disagree (and rightly so), but I don't use Conditional activities (commonly referred to as "Decision Diamonds) very often. Typically I'll just have the transitions that would have come out of the Conditional activity instead come directly out of the preceding activity. While business analysts who use Conditional activities are modeling processes correctly and in accordance with what industry pundits like Bruce Silvers would prefer seeing, my personal feeling is that their use just adds clutter to a process. There's an elegance to a well designed business process. I always strive to keep them as simple and as understandable as possible to both the business and IT.
I'll use Conditional activities in two cases:
1) When the business is more familiar with Condtional activities and have used them extensively when modeling processes in the past using process modeling tools (e.g. Visio). If they're used to seeing Conditional activities, not using Conditional activities would be a distraction that some business analysts or business people would find annoying.
or
2) When I have a process design pattern where there are nested Conditional activities. For example:
<pre class="jive-pre"><p />
"Activity A" -> Conditional -> "Activity B"
V
"Activitiy C" -> Conditional -> "Activity D"
V
"Activity E"</pre>
Here, the work item instance flows from A to either B or C. If it goes to C then it either flows to D or E. While having Conditional activities for this use case is not essential (again - you could have the transitions come out of A and C directly), it makes the process easier to understand for business analysts and the business. I think not having the Conditional activities here makes the process look a bit like an electronics wiring diagram.
Hope this helps,
Dan