summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorVrishali Doke2013-03-14 02:00:28 (EDT)
committer Sven Rottstock2013-03-14 02:00:28 (EDT)
commita03a183b4b409a920011f29cf68f9cd59d6871bf (patch)
treebb968779b127ee62f4d9a9c0ced85db63cf0dfe5
parentc4ac310b74adba0063d5a33cf67b2d66a9b67bd5 (diff)
downloadorg.eclipse.stardust.documentation-a03a183b4b409a920011f29cf68f9cd59d6871bf.zip
org.eclipse.stardust.documentation-a03a183b4b409a920011f29cf68f9cd59d6871bf.tar.gz
org.eclipse.stardust.documentation-a03a183b4b409a920011f29cf68f9cd59d6871bf.tar.bz2
CRNT-27834 - Updated for events
git-svn-id: http://emeafrazerg/svn/ipp/product/trunk/stardust/documentation@63717 8100b5e0-4d52-466c-ae9c-bdeccbdeaf6b
-rw-r--r--org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/images/file-config.pngbin10853 -> 13333 bytes
-rw-r--r--org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/images/mail-config.pngbin12775 -> 13850 bytes
-rw-r--r--org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/pep-events.htm18
3 files changed, 9 insertions, 9 deletions
diff --git a/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/images/file-config.png b/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/images/file-config.png
index c98e44d..951e182 100644
--- a/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/images/file-config.png
+++ b/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/images/file-config.png
Binary files differ
diff --git a/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/images/mail-config.png b/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/images/mail-config.png
index 4c183b5..9541ff4 100644
--- a/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/images/mail-config.png
+++ b/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/images/mail-config.png
Binary files differ
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 8c9b9f7..cd1a09d 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
@@ -38,9 +38,6 @@ The Business Process Modeling perspective supports two types of events:</p>
</ul>
-
-
-
<h2 id="adds">Adding Start Event</h2>
<p>In the toolbar, click <strong>Create Start Event</strong> icon and drop it to swim lanes.
@@ -285,7 +282,9 @@ its content is retrieved and mapped accordingly. To configure the file event, sp
<ul>
<li>Configuration
<ul>
- <li>File or Directory - Specify the path for a file or directory</li>
+ <li>Directory Name - Specify the path for a file or directory</li>
+ <li>File Name - If you want to consume a single file only, you can specify the file name
+ . </li>
<li>Recursive - If a directory path is provided, if looks for files in all the sub-directories, as well.</li>
<li>Initial Interval - Duration before polling starts for file or directory</li>
<li>Repeat Interval - Duration before the next poll of the file/directory</li>
@@ -338,7 +337,7 @@ and passing all the information contained as input data.
<li>Initial Delay - Specify time period before the polling starts</li>
<li>Unseen - Processes only unseen messages</li>
<li>Delete - Deletes the messages after they have been processed</li>
- <li>Copy To - After processing a mail message, it can be copied to a mail folder specified in the adjacent text box.</li>
+ <!-- <li>Copy To - After processing a mail message, it can be copied to a mail folder specified in the adjacent text box.</li> -->
</ul>
</li>
<p class="image"><img src="images/mail-config.png" alt=""> <br>
@@ -423,10 +422,11 @@ is already provided under the in WEB-INF/config/spring folder.
</p> -->
<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 @productnameonly@ 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,
-to allow process instances to be started manually and via @productname@ Scan.
+<p>Using the Scan event, you can start the process instance via Scan Tool.
+For more information on scan tool, please
+refer to the @productnameonly@ Scan guide. You can use the scan
+event with Manual Trigger in one process definition. It allows process instance
+to be started manually and via @productname@ Scan.
</p>