[TAV-574] Nested workflow location Created: 2007-08-15  Updated: 2013-12-11  Resolved: 2008-03-18

Status: Closed
Project: myGrid
Component/s: None
Affects Version/s: None
Fix Version/s: 1.7.1

Type: Improvement Priority: Minor
Reporter: Alan Williams Assignee: Ian Dunlop
Resolution: Implemented Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
depends on TAV-559 Referenced nested workflow support sh... Closed


The location of sub-workflows is recorded as an absolute path. This can cause problems when a hierarchy of workflows is moved aroound a file system or between machines.

Comment by Stian Soiland-Reyes [ 2008-03-07 ]

My suggestions:

The easiest way to work around this bug without handcrafting the XML is to in Taverna where the workflow containing a nested workflow has been correctly loaded, right click on the nested workflow and select "Edit nested workflow". Click the "Workflows" menu and go back to the parent workflow. This should have created a copy of the nested workflow so that if you now save the parent, the nested workflow will be saved as part of the SCUFL of the parent.

We'll try to find a way to improve this, one reason why some users still like the reference version is that they can then update the nested workflow, save it, and all of the workflows including that as a nested workflow would use the new version.

My suggestion for how we (the developers) are going to fixing this is to show this explicitly in the GUI and not just in the XML, and allow the user to choose which one they want to go for, the copy or the filename, and additionally to save the filename as a relative reference if possible.

myExperiment should also give a warning if people try to upload a workflow with such missing references.

Another workaround is to use "Add Nested Workflow ... Open Location" and paste in the download URL of the nested workflow as it is on myExperiment. As long as the other user of the parent workflow is connected to the Internet, myExperiment is online, and the other user has access to the nested workflow there, such a parent workflow would also be shareable.

Comment by Ian Dunlop [ 2008-03-17 ]

Setting the URL temporarily to null in a nested workflow forces it to be written out in full when saving the SCUFL

Comment by Ian Dunlop [ 2008-03-18 ]

In the SaveWorkflowAction it uses a new JFileChooser called NestedFileChooser which has a checkbox to select saving the full nested workflow or not. If you check this box ithe SaveWorkflowAction uses a NestedWorkflowSwitch which can set the nested workflow to null. This causes it to write it's XML out in full. The same class is then used to reset the URL back to what it was later.

Generated at Sat Sep 19 19:35:47 BST 2020 using JIRA 6.1.2#6157-sha1:98c729218aad6de1537eb8e98889ee5562c90d96.