1. myGrid
  2. TAV-675

t2 should support implicit iteration in input port


    • Type: Improvement Improvement
    • Status: Closed Closed
    • Priority: Major Major
    • Resolution: By Design
    • Affects Version/s: None
    • Fix Version/s: 1.7.1
    • Component/s: None
    • Labels:


      Perhaps a discussion point, but it is my view that users do currently (in t1) use the possibility to immediately change a workflow to do implicit iteration on its input ports by providing more than one value, even if the first services in the list expects a single value.

      t2 does not support this and is stricter on that the input value needs to match the input port's depth (which again has to match to the depth of the next service, since there is no way in t1 to specify the depth on an input port directly).

      This could easily be achieved by wrapping the translated t1-workflow in a nested workflow. For core t2 workflows we probably want to keep the current strict rule.


        Stian Soiland-Reyes made changes -
        Field Original Value New Value
        Demand Factor 3
        Fix Version/s First New Year 2008 Release [ 10054 ]
        Tom Oinn made changes -
        Status Open [ 1 ] Closed [ 6 ]
        Resolution By Design [ 8 ]
        David Withers (Inactive) made changes -
        Workflow New features and improvements [ 11004 ] jira [ 11939 ]
        Alan Williams made changes -
        Component/s t2 maelstrom [ 10042 ]


          • Assignee:
            Tom Oinn
            Stian Soiland-Reyes
          • Votes:
            0 Vote for this issue
            0 Start watching this issue


            • Created: