[ 
https://issues.apache.org/jira/browse/AIRAVATA-298?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Chathura Herath resolved AIRAVATA-298.
--------------------------------------

    Resolution: Fixed
      Assignee: Chathura Herath  (was: Lahiru Gunathilake)


Fixed  r 305483 
                
> Allow workflow intepreter to start executing even when all the "Input Node" 
> valuese are not set
> -----------------------------------------------------------------------------------------------
>
>                 Key: AIRAVATA-298
>                 URL: https://issues.apache.org/jira/browse/AIRAVATA-298
>             Project: Airavata
>          Issue Type: New Feature
>          Components: XBaya
>            Reporter: Chathura Herath
>            Assignee: Chathura Herath
>            Priority: Minor
>             Fix For: 0.4-INCUBATING
>
>
> Motivating usecase from LCCI is as follows.
> User plans to run a workflow with two components(A,B). Each of the components 
> have input nodes attached to them. Also B follows A so output of A goes to an 
> input of B.
> In this particular situation the user shall know the iput to component A, but 
> does not know input to component B until such time component A finishes and 
> user gets a chance to open and evaluate the output (we shall differ 
> discussion on how we can make it easy to evealuate the outputs for later).
> Once the user evaluates the output of A he will know what to put into the 
> input Node of B.
> Currently we ask all the inputs at the begining of the workflow launch thus 
> workflow interpreter assumes that all the input nodes are filled.  So we make 
> the input boxes to FInish state at the very begining.
> Now we simply have to make some input boxes Gray(the ones for which we got 
> the input) and others to be waiting/or some special state.
> For workflowinterpreter execution purposes this shall be as any other 
> waiting(yellow) node. If at any point of time user click on config of such a 
> input node and set the input value, we can move them to the finished state 
> and workflow intepreter shall handle the rest of the execution.
> One optimization to keep in mind though is, during execution, if ALL the 
> remaining waiting nodes in a workflow directly or transitively wait on such 
> an input, workflow should goto a PAUSE mode  until such time user enters a 
> inputvalue.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to