<html>
<head>
<base href="http://bugzilla.ecoinformatics.org/" />
</head>
<body><table border="1" cellspacing="0" cellpadding="8">
<tr>
<th>Bug ID</th>
<td><a class="bz_bug_link
bz_status_ASSIGNED "
title="ASSIGNED --- - wrong behavior when trying to Export a run when module dependencies not satisfied"
href="http://bugzilla.ecoinformatics.org/show_bug.cgi?id=5782">5782</a>
</td>
</tr>
<tr>
<th>Summary</th>
<td>wrong behavior when trying to Export a run when module dependencies not satisfied
</td>
</tr>
<tr>
<th>Classification</th>
<td>Unclassified
</td>
</tr>
<tr>
<th>Product</th>
<td>Kepler
</td>
</tr>
<tr>
<th>Version</th>
<td>trunk
</td>
</tr>
<tr>
<th>Hardware</th>
<td>Other
</td>
</tr>
<tr>
<th>OS</th>
<td>All
</td>
</tr>
<tr>
<th>Status</th>
<td>ASSIGNED
</td>
</tr>
<tr>
<th>Severity</th>
<td>normal
</td>
</tr>
<tr>
<th>Priority</th>
<td>P2
</td>
</tr>
<tr>
<th>Component</th>
<td>workflow run manager
</td>
</tr>
<tr>
<th>Assignee</th>
<td>barseghian@nceas.ucsb.edu
</td>
</tr>
<tr>
<th>Reporter</th>
<td>barseghian@nceas.ucsb.edu
</td>
</tr>
<tr>
<th>QA Contact</th>
<td>kepler-dev@kepler-project.org
</td>
</tr></table>
<p>
<div>
<pre>If you attempt to Export a run from the Workflow Run Manager when its module
dependencies are not satisfied, the Import Module Dependencies action is
invoked. This is desirable, so the user is warned, and if relevant, offered the
option to restart into the right modules. However the dialog only offers a
'Force Open' option, which doesn't make sense here -- instead it needs to offer
a 'Force Export' option, with slightly different text and warning. The warning
should explain that it's possible not all artifacts will make it into the KAR
(inactive modules' KAR entry handlers are not present in the system to be able
to place the artifacts they're responsible for into the KAR, a restriction of
our KAR saving design). Also, when Force Export is used, the module dependency
list in the KAR's manifest should not utilize the 'override module
dependencies' functionality in our code -- e.g. if you attempt to save a run
that was created within reporting, from within just the workflow-run-manager
suite, the reporting artifacts will not be placed into this 'forced KAR', and
it's then less desirable to include reporting in that kar's mod dep list than
simply use the currently active module suite.
I'll commit a fix shortly.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the QA Contact for the bug.</li>
</ul>
</body>
</html>