Related to #152.
Actually it would also make sense for the generically generated nodes to allow such a mechanism. If you are at a certain point where you have digested your data far enough that you only have small files (e.g. IdXML) you might want to save the data in place such that the workflow can easily be restored after closing and reopening. Currently you would need to save the file(s) with Outputfile/folder and actually edit your workflow after reopening to use these files instead of just leaving the workflow as is. The priority of this issue is not so high since there are workarounds and at the point where you got to a table, it is saved by KNIME anyway. But once it is in a table, you can't go back to the original file formats for different kinds of processing.
Actually I think the problem occurred after transformations with FilePortToURI and URIToFilePort.
In this case, the Filestores get lost. Not sure if there is an easy workaround.
Related to #152. Actually it would also make sense for the generically generated nodes to allow such a mechanism. If you are at a certain point where you have digested your data far enough that you only have small files (e.g. IdXML) you might want to save the data in place such that the workflow can easily be restored after closing and reopening. Currently you would need to save the file(s) with Outputfile/folder and actually edit your workflow after reopening to use these files instead of just leaving the workflow as is. The priority of this issue is not so high since there are workarounds and at the point where you got to a table, it is saved by KNIME anyway. But once it is in a table, you can't go back to the original file formats for different kinds of processing.