summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorVrishali Doke2013-09-20 05:49:46 (EDT)
committerStephan Born2013-10-23 06:46:15 (EDT)
commit10c6051c2fc53010b973dfe4136c35a76323c925 (patch)
treee6b37a81c685d507b24348a6c0976da67ba2cea2
parentaca88dbd89f597c9b868fb54550c89c3958134c3 (diff)
downloadorg.eclipse.stardust.documentation-10c6051c2fc53010b973dfe4136c35a76323c925.zip
org.eclipse.stardust.documentation-10c6051c2fc53010b973dfe4136c35a76323c925.tar.gz
org.eclipse.stardust.documentation-10c6051c2fc53010b973dfe4136c35a76323c925.tar.bz2
Jira-ID: CRNT-30598
Moved binding and unbinding section git-svn-id: https://svn.csa.sungard.com/repos/ipp2/product/trunk/stardust/documentation@67460 8100b5e0-4d52-466c-ae9c-bdeccbdeaf6b Signed-off-by: Vrishali Doke <vrishali.doke@sungard.com>
-rw-r--r--org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/pep-events.htm13
-rw-r--r--org.eclipse.stardust.docs.dev/html/concepts/workflow-basics/mg-basics-11.htm19
2 files changed, 13 insertions, 19 deletions
diff --git a/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/pep-events.htm b/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/pep-events.htm
index 30714a0..ad91d19 100644
--- a/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/pep-events.htm
+++ b/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/pep-events.htm
@@ -597,6 +597,7 @@ However, an Intermediate Event does not start or directly terminate a process.
<li><a href="#do">Dos and Don'ts wrt. Boundary Event Modeling</a></li>
<li><a href="#use">Using Intermediate Event Flyout Menu</a></li>
<li><a href="#view">Viewing and Editing Properties</a></li>
+ <li><a href="#bindun">Binding and Unbinding Boundary Events to and from Activities</a></li>
<li><a href="#exam">Examples</a></li>
</ul>
@@ -846,6 +847,18 @@ at the time of deployment.
</p>
<p class="image"><img src="images/dusjunct.png" alt=""> <br>
<strong>Figure:</strong> Multiple Error Event - Deployment Validation</p>
+<h3 id="bindun">Binding and Unbinding Boundary Events to and from Activities</h3>
+<h4>Binding Boundary Events</h4>
+<p>To bind boundary events to an activity, they can be dropped onto another activity
+or the drawing canvas. The existing exception flow, e.g. a connection, is maintained
+in that case.</p>
+<p>When binding an unbound event that has incoming and outgoing connections,
+the incoming is deleted, whereas the outgoing will be maintained.
+An exception is thrown when the event is bound to the activity that is attached
+to the event's outgoing connection. In this case both, the incoming and
+outgoing connections, are deleted.</p>
+<h4>Unbinding Boundary Events</h4>
+<p>Boundary Events can be unbound from activities via drag-and-drop.</p>
<h2 id="exam">Examples</h2>
<p class="note"><strong>Note</strong><br>
To execute following examples, please start Event Daemon.</p>
diff --git a/org.eclipse.stardust.docs.dev/html/concepts/workflow-basics/mg-basics-11.htm b/org.eclipse.stardust.docs.dev/html/concepts/workflow-basics/mg-basics-11.htm
index b591fd8..695c395 100644
--- a/org.eclipse.stardust.docs.dev/html/concepts/workflow-basics/mg-basics-11.htm
+++ b/org.eclipse.stardust.docs.dev/html/concepts/workflow-basics/mg-basics-11.htm
@@ -257,25 +257,6 @@ All Intermediate Events in a model must have both an incoming and outgoing seque
<p>Note that Data may not be connected directly to Events in the Business Process Modeler.</p>
<p>An existing exception flow (i.e., connection) is maintained when dropped
onto another activity or onto the drawing canvas.</p>
-
-<h3 id="bindun">Binding and Unbinding Boundary Events to and from Activities</h3>
-<h4>Binding Boundary Events</h4>
-<p>To bind boundary events to an activity, they can be dropped onto another activity
-or the drawing canvas. The existing exception flow, e.g. a connection, is maintained
-in that case.</p>
-<p>When binding an unbound event that has incoming and outgoing connections,
-the incoming is deleted, whereas the outgoing will be maintained.
-An exception is when the event is bound to the activity that is attached
-to the event's outgoing connection. In this case both, the incoming and
-outgoing connections, are deleted.</p>
-
-<h4>Unbinding Boundary Events</h4>
-<p>Boundary Events can be unbound from activities via drag-and-drop.</p>
-
-
-
-
-
<script language="JavaScript" type="text/javascript">
<!--
writeFooter();