summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorVrishali Doke2013-03-04 08:00:47 (EST)
committerSven Rottstock2013-03-11 07:39:28 (EDT)
commit2385184d90df36843bad337aa3419f5e6b3fb822 (patch)
tree8cf2636188bd20c86e812404090e2c422c3c9c2f
parent7654d22cffc4dfdfbf8a03e6d2494aafe4291355 (diff)
downloadorg.eclipse.stardust.documentation-2385184d90df36843bad337aa3419f5e6b3fb822.zip
org.eclipse.stardust.documentation-2385184d90df36843bad337aa3419f5e6b3fb822.tar.gz
org.eclipse.stardust.documentation-2385184d90df36843bad337aa3419f5e6b3fb822.tar.bz2
CRNT-27834 - Camel events added
git-svn-id: http://emeafrazerg/svn/ipp/product/trunk/stardust/documentation@63451 8100b5e0-4d52-466c-ae9c-bdeccbdeaf6b
-rw-r--r--org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/pep-events.htm7
1 files changed, 4 insertions, 3 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 2b67e2d..7423a91 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
@@ -57,9 +57,10 @@ Eclipse-based modeler do not display labels for the event. For more information,
<li>None
<ul>
<li><a href="#simpl">Manual Trigger</a>
+ <li><a href="#scan">Scan Event</a></li>
</ul>
</li>
- <li>Message
+ <li> Camel Message Events
<ul>
<li><a href="#file">File Event</a></li>
<li><a href="#mail">E-mail Event</a></li>
@@ -67,7 +68,7 @@ Eclipse-based modeler do not display labels for the event. For more information,
<li><a href="#cam">Generic Camel Route Event</a></li>
</ul>
</li>
- <li>Timer
+ <li>Camel Timer Event
<ul>
<li><a href="#time">Timer Event</a></li>
</ul>
@@ -431,7 +432,7 @@ downloaded jars should be copied to <tt>ipp-portal/lib</tt> folder </p>
is already provided under the in WEB-INF/config/spring folder.
</p> -->
-<h3>Scan Event</h3>
+<h3 id="scan">Scan Event</h3>
<p>Using the Scan event, you can start the process instance via Scan Tool. For more information on scan tool, please
refer to the Infinity Scan guide. Scan events are non-exclusive, which means that it is
possible to have both in one process definition, a Manual Trigger and a Scan event,