You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When exporting a workbench project it creates a project zip file (so you can import on another machine). It would be nice to be able to export it as a named config file that can be passed to the singlemachine variant as the formats are (understandably) very different.
The text was updated successfully, but these errors were encountered:
Do you want to export a XML file according to the Silk Link Specification Language [1]? You can do this if you go to the linkage rule editor and click on "Get Linkspec". The resulting link spec should be executable in Silk SingleMachine.
Cool, thanks. I did not know that. That is good and helpful. But I would have to do that on a per linkage and transform basis...if I have several defined and want to run them all...I would want the project. :-)
Of course, I could do them individually and just add the Interlinks...
You are right, exporting a link spec that contains all tasks in the project is currently not possible, but would be helpful. I have marked this issue as enhancement, so it can be done as soon as there is time.
When exporting a workbench project it creates a project zip file (so you can import on another machine). It would be nice to be able to export it as a named config file that can be passed to the singlemachine variant as the formats are (understandably) very different.
The text was updated successfully, but these errors were encountered: