[Vernalis] Configurable End IF/Case: Enable individual Output Port Types

[mwiegand]

Hi @Vernalis,

I’d like to suggest to enable configuring each output port type individually.

I have a scenario where I create a workflow which allows to chose between different upload methods. I could try to work around this by enclosing each upload type into an individual workflow and calling that remotely.

Though, this might be more logically and providing the great benefit of more flexibility.

What do you think?

Cheers
Mike

[mlauber71]

@mwiegand the (new) case nodes allow different ports, just for the record

CASE Switch End

[mwiegand]

Thanks for the info @mlauber71 … I wasn’t aware that the neglected switch-case finally got some love. However, I literally meant to be able to add different but not a singly type of output port with the intend to pass one i.e. for AWS, GitHub, Google Drive etc…

I am close top completing a workflow which will enable everyone to backup the entire workspace and to allow to sync it between devices comfortably.

[mlauber71]

@mwiegand concerning a backup and restore I have proposed this solution some time ago:

Copy/Move Files Node

@zedleb I created and example where the KNIME workflow (or workflow group) is being zipped into a file with a current timestamp. And can later be restored to a (separate) folder. [image] [image] This restore can either be automated also or you could do it manually if you need it. [image] [image] Please note you will have to configure the Path variables and workflow names to your needs. I use local paths that will be created dynamically.

About the different ports and connections to backup. Would it be an option to use Flow Variables and then point to different connectors.

This example switches database connections. You can actually mix the ports. So the CASE start can be a Flow Variable and the end can be a database connection.

DB_Query- case Switch

@pszpadro from your description it could look something like this. Based on a query from the database a decision is made to take the ‘road’ of either Bubu or Jogi and continue afterwards. [image] The Case Switch node is very flexible. [image] You can combine a wide range of input and output ports and decide the port number (starting with 0) with the help of Flow Variables. [image] The two streams can be separated and the end could just be to bring the Flow Variables back together. Just k…

[mwiegand]

Thanks for the recommendations. What do you think about us joining forces on that?

The workflow I created seems to offer some extras so we could merge our both workflows to create something magically

What mine is currently capable of is:

1. Interactive view to chose the archive type, destination and conditionally configure the credentials and other requirements
   
   
2. Fetching each individual workflow, extracting meta data such as last last modification for delta processing later on
3. Identifying which workflows have a lock file in place to skip these
4. Creating one archive per workflow (stuck here because of a possible bug 82519

Preparations made for:

1. Delta processing
2. Conditional file transfer based on destination type

Additions planned:

1. Option to skip data directory
2. Depending on 82516 to call sub-workflows for specific upload methods (GitHub, Google Driver, network Drive etc.)

And some other but rather vague ideas.

Cheers
Mike