In general we discourage this - but there is some conversation about this here - at least as it pertains to the instance URL and API key: http://dev.list.galaxyproject.org/find-UUID-of-current-history-in-tool-XML-w... The workflow is more tricky - if you are sure the job is going to be coming from a workflow - you might be able to pull off something like: #set $workflow_id=$__app__.security.encode_id(output.creating_job.workflow_invocation_step.workfow_invocation.workflow.stored_workflow.id) or #set $workflow_id=$__app__.security.encode_id(output.creating_job.workflow_invocation_step.workfow_invocation.workflow.id) One of those might be the right id to invoke a workflow through the API using. It is discouraged - I'd track this information somewhere else I guess - but I understand the expediency tools can provide sometimes. -John On Mon, Aug 22, 2016 at 9:07 AM, Katherine Beaulieu <katherine.beaulieu014@gmail.com> wrote:

Hi everyone, We are trying to obtain the three things in the tile of this post to enable a tool to use the bioblend api and get the .ga file so that any user can go back into our system, get the workflow associated with the end file, get the input parameters which are tags associated with the end file, and rerun that workflow if necessary. So simply put I am asking if there is a way to access a galaxy instance through the bioblend api from within a tool's config xml file.

I have asked about getting the .ga file beforehand but still have not solved this problem so if anyone has any experience with this please let me know. Cheers, Katherine

___________________________________________________________ Please keep all replies on the list by using "reply all" in your mail client. To manage your subscriptions to this and other Galaxy lists, please use the interface at: https://lists.galaxyproject.org/

To search Galaxy mailing lists use the unified search at: http://galaxyproject.org/search/mailinglists/