summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorVrishali Doke2013-02-22 01:43:40 (EST)
committer Sven Rottstock2013-03-11 07:38:42 (EDT)
commitfff2099c16150ed11a112c9ea63579fffc6ce0ab (patch)
treee3699f65ce19a0a99490acc32cda4f38b1506cef
parent6466fe893662b1768128ec288206e2b8d9dbd2ad (diff)
downloadorg.eclipse.stardust.documentation-fff2099c16150ed11a112c9ea63579fffc6ce0ab.zip
org.eclipse.stardust.documentation-fff2099c16150ed11a112c9ea63579fffc6ce0ab.tar.gz
org.eclipse.stardust.documentation-fff2099c16150ed11a112c9ea63579fffc6ce0ab.tar.bz2
CRNT-27989 - Prevent dnd of process across models
git-svn-id: http://emeafrazerg/svn/ipp/product/trunk/stardust/documentation@63173 8100b5e0-4d52-466c-ae9c-bdeccbdeaf6b
-rw-r--r--org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/images/pro-dnd.pngbin0 -> 12645 bytes
-rw-r--r--org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/pep-pools-lanes.htm11
-rw-r--r--org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/pep-process.htm13
3 files changed, 19 insertions, 5 deletions
diff --git a/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/images/pro-dnd.png b/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/images/pro-dnd.png
new file mode 100644
index 0000000..11661ef
--- /dev/null
+++ b/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/images/pro-dnd.png
Binary files differ
diff --git a/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/pep-pools-lanes.htm b/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/pep-pools-lanes.htm
index 341c306..fd6dec3 100644
--- a/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/pep-pools-lanes.htm
+++ b/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/pep-pools-lanes.htm
@@ -175,7 +175,12 @@ Existing elements can be dragged across lanes.
<li><a href="#hov">Hovering the Mouse Over the Element</a></li>
<li><a href="#dou">Double-clicking an Element</a></li>
<li><a href="#click">Clicking an Element</a></li>
- <li><a href="#ele">Dragging and Dropping of Elements</a></li>
+ <li><a href="#ele">Dragging and Dropping of Elements</a>
+ <ul>
+ <li><a href="#did">Dragging and Dropping Elements with Same ID</a></li>
+ <li><a href="#dmode">Dragging and Dropping Elements across Models</a></li>
+ </ul></li>
+
</ul>
@@ -242,7 +247,7 @@ You can drag and drop the elements as described in the chapter <a href="model-vi
</tr>
</table>
-<h4>Dragging and Dropping Elements with Same ID</h4>
+<h4 id="did">Dragging and Dropping Elements with Same ID</h4>
<p>However, whenever you drag and drop any element within the model or across the models, a validation
is performed on the ID of the elements. If the element with the same ID exists, then you cannot drag and
drop the element. In that case, the following message is displayed:</p>
@@ -252,7 +257,7 @@ drop the element. In that case, the following message is displayed:</p>
<strong>Figure:</strong> Validation Drag and Drop Operation - Element with same ID</p>
<p>You should change the name of the element which changes the ID accordingly, to enable drag and drop operation.</p>
-<h4>Dragging and Dropping Elements across Models</h4>
+<h4 id="dmode">Dragging and Dropping Elements across Models</h4>
<p>Elements that are not publicly visible cannot be dragged and dropped across the models from the
My Process Models panel. If you try to drag and drop element for which the Public Visibility option is not
selected, the following error message is displayed and the element do not get added to the process diagram canvas.</p>
diff --git a/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/pep-process.htm b/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/pep-process.htm
index 4fd3085..54dffd3 100644
--- a/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/pep-process.htm
+++ b/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/pep-process.htm
@@ -149,10 +149,10 @@ So there are three valid states concerning declared and implemented process inte
other consumer model should choose this option. When a process interface property
of a process definition is set to Provides Process Interface,
it can be referenced from the consumer model.
-When you select the Provides Process Interface, the following options are displayed:
+When you select the Provides Process Interface, the following options are displayed:</p>
<p class="image"><img src="images/provide.png" alt=""> <br>
<strong>Figure:</strong> Provides Process Interface</p>
-</p>
+
<ul>
@@ -334,6 +334,15 @@ a relationship between models.
</span><span class="hideReference">
<strong>Multi-model Audit Trail Setups</strong> in the <strong>@productname@ Documentation</strong>.</span>
+<p>Processes that do not have process interface defined cannot be dragged and dropped
+across the models. If you try to drag and drop the process for which the process interface is not defined then
+the following message is displayed in the process diagram message area and the process do not get added to the
+process diagram canvas:</p>
+
+<p class="image"><img src="images/pro-dnd.png" alt=""> <br>
+ <strong>Figure:</strong> Drag and Drop Process - No Process Interface</p>
+
+
<script language="JavaScript" type="text/javascript">
<!--