Great catch, Alan! With some search-replace then you would have the run uuid.
Do you think it would be useful for this and other metadata to be accessible formally somehow within the workflow? As a special activity or hidden variables to Beanshell? On 16 Apr 2016 13:42, "Alan Williams" <[email protected]> wrote: > On 16-Apr-16 13:21, Stian Soiland-Reyes wrote: > >> Ah.. but then I'm not sure if my UUIDs will help you, as those >> identify the command line engine's run ID - while I guess you want to >> match the UUIDs used in the REST interface of the Taverna Server. >> >> I am not sure if the Taverna Server can be told to inject the external >> run UUID into the workflow.. Donal? >> > > I think the Taverna Server's run UUID may be used as part of the > environment variables for running the command line tool in? That (along > with lots of other environment variables) is made visible by the > Get_Environment_Variables_as_XML service. If so, it can be pulled out and > fed into the beanshell. > > For example, that XML contains (for my test run): > > <property name="taverna.interaction.feed_path" > value="%2Ftserver%2Frest%2Fruns%2Fff2bc479-8260-427b-ac1b-004055d65e02%2Finteraction"/> > > So, I think the run ID might be 2Fff2bc479-8260-427b-ac1b-004055d65e02 > > I think it's worth trying :) > > Alan >
