summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorVrishali Doke2013-09-20 06:32:24 (EDT)
committer Stephan Born2013-10-23 06:46:56 (EDT)
commitf078c771b2ec0fb26894adbbf51590801d5e746c (patch)
tree5bd3fc41203b2644c065a8ca1bf991bd22813459
parentaa199751192537fb1c69624c919fe56eafcd57c9 (diff)
downloadorg.eclipse.stardust.documentation-f078c771b2ec0fb26894adbbf51590801d5e746c.zip
org.eclipse.stardust.documentation-f078c771b2ec0fb26894adbbf51590801d5e746c.tar.gz
org.eclipse.stardust.documentation-f078c771b2ec0fb26894adbbf51590801d5e746c.tar.bz2
Jira-ID: CRNT-30217
Updated for events git-svn-id: https://svn.csa.sungard.com/repos/ipp2/product/trunk/stardust/documentation@67469 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-modeler-compatibility.html6
1 files changed, 2 insertions, 4 deletions
diff --git a/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/pep-modeler-compatibility.html b/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/pep-modeler-compatibility.html
index d039d53..39437fa 100644
--- a/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/pep-modeler-compatibility.html
+++ b/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/pep-modeler-compatibility.html
@@ -131,10 +131,8 @@ of the chapter <a href="models/model-props.html">Model Properties</a>.
point is the return value of the completion method. Only these access points are displayed in the
Web-based modeler.</p>
<h3 id="eve">Events</h3>
-<p>Modeling of Intermediate events is not supported in Eclipse-based modeler.
-However, if you import a model which contains intermediate events to Eclipse-based modeler,
-it should work as expected. But you should not edit the intermediate events activities including
-transitions.</p>
+<p>Models containing intermediate events may cause inconsistency warnings and errors when opened
+in the Eclipse-based modeler which may prevent direct deployment from the Eclipse-based modeler.</p>
<!--
However, if you import a model which contains non-boundary event to Eclipse-based modeler,
you need to adjust the model accordingly as the non-boundary event icon will not be visible but