Pipeline Node should not need to be connected to every task

[AlexandreSajus]

Description
We must connect the Pipeline Node to every Task Node we want to execute.
This was misleading during beta testing: testers would forget to connect new tasks, and since the error logs don't explain much, they could not find what was wrong.

A tester expected that the pipeline should only be connected to the first Task Node, every Task Node connected indirectly to this first Task Node should also be executed like here:

[jrobinAV]

I believe there is a misunderstanding of what is a Pipeline vs a Scenario. In Taipy 3.0 it should be simpler.

Basically, a pipeline is a subset of tasks that can be executed together independently from the other scenario tasks.
When building your ScenarioConfig in studio, you want to define the sets of taskConfigs that belongs to the various PipelineConfigs created. There could be some taskConfig attacched to multiple PipelineConfigs and some TaskConfigs attached to zero pipelineConfig.

The proposal "the pipeline should only be connected to the first Task Node" does not make sense in this context.

Still the issue is interesting cause it shows that it is not intuitive. Probably both the Pipeline concept itself and Studio config are not intuitive regarding the usage of Pipeline.
I would recommend at this stage, to simply remove the Pipeline Box and the Scenario Box.

What do you think ?
@AlexandreSajus @FredLL-Avaiga @FlorianJacta @FabienLelaquais

[AlexandreSajus]

I agree. Removing the Pipeline Box and Scenario Box would make things more straightforward and more intuitive

[FredLL-Avaiga]

Shall we close this @AlexandreSajus @jrobinAV ?

[jrobinAV]

I don't know.
A question has been raised. Do we want to remove the Pipeline box and the Scenario Box? Does it make sense for everyone?

[FredLL-Avaiga]

Not the scenario I suppose pipeline will go when we support 3.0?

…

On Wed, Jul 19, 2023, 12:07 Jean-Robin ***@***.***> wrote: I don't know. A question has been raised. Do we want to remove the Pipeline box and the Scenario Box? Does it make sense for everyone? — Reply to this email directly, view it on GitHub <#57 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AVQBA5CP6FLFFERHVIVGLKLXQ6WUXANCNFSM6AAAAAAYOLDD6Y> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[AlexandreSajus]

I don't know. A question has been raised. Do we want to remove the Pipeline box and the Scenario Box? Does it make sense for everyone?

In my mind, removing both of these would significantly improve accessibility which is the main bottleneck of Core currently.

[jrobinAV]

@FredLL-Avaiga Yes, removing the pipeline would be part of 3.0 anyway.

In 3.0 ScenarioConfig will directly hold TaskConfigs and some additional data node configs unrelated to any taskConfig.

If we keep the Scenario Box, that means it will be linked to all the task boxes and all the additional data node boxes. I guess it will degrade the accessibility a lot.

[FabienLelaquais]

If we use the link representation, yes.
But we can change that, and add a 'Holding Scenario' label in the task and invent something for building the relationship.
Now I suspect that tasks can be used by different scenario configs...

[jrobinAV]

Yes, both task configs and data node configs may be used by multiple Scenario configs...

Maybe the Scenario config can be displayed as a "title" of the graph displayed. I don't know.
The difficulty would be on a global view with multiple scenario configs.