Hub
Pricing About
NodeNode / Manipulator

CASE Switch End

Workflow ControlSwitches
Drag & drop
Like

This node complements the CASE Switch Start node. It merges the created branches into a single output port. Typically, only one branch is active, and the content on that branch is forwarded to the output port. In case the Switch is used for data ports, additional options for merging the data tables on multiple active branches are offered.
The type of the input and output ports can be chosen when adding an output port using the “…” menu. The type of the output port can be changed by removing and adding it again with a new type.

Note for flow variable ports: The values for existing flow variables will always be those at the top-most port of the end node, even if they are changed on an active branch (that is not connected to the top-most port). However, new variables created in any active branch will behave as expected. If you want to change the value of existing variables, please create a new flow variable, and use its value to overwrite the old variable after the CASE Switch End node.
If all branches are inactive, the flow variables of the top branch are passed through.

To migrate from the deprecated CASE Switch Model (End) node, select Generic Port when creating the output port.

External resources

  • KNIME E-Learning Course: Creation and usage of Flow Variables in a KNIME workflow

Node details

Input (Dynamic Inport)
Select the input port type and connect it. Only one input port can be selected at a time. If the input port is removed, all output ports are also removed.
Output (Dynamic Outport)
The output ports. They are only present and editable if an input port type was selected and always have the same type. At least two outputs are required.
  1. Type: Petri Net
  2. Type: Flow Variable
  3. Type: MOE Model
  4. Type: Image
  5. Type: Distance Measure
  6. Type: PMML
  7. Type: Sota
  8. Type: Regression Tree
  9. Type: PortObject
  10. Type: Correlation
  11. Type: Feature Selection Model
  12. Type: Transformation
  13. Type: Radial Basis Function
  14. Type: Fuzzy Basis Function
  15. Type: Gradient Boosting Model
  16. Type: Tree Ensembles
  17. Type: Outlier
  18. Type: Network
  19. Type: OpenNlpNerTaggerModelPortObject
  20. Type: StanfordNERModelPortObject
  21. Type: DocumentVectorPortObject
  22. Type: VectorHashingPortObject
  23. Type: JChem Database Connection
  24. Type: URI Object
  25. Type: Table
  26. Type: Arx Config
  27. Type: XLS Formatter
  28. Type: Binning Port Object
  29. Type: de.mpicbg.knime.scripting.r.port.RPortType2
  30. Type: Event Log
  31. Type: Directly Follows Model
  32. Type: AWS Comprehend Connection
  33. Type: DB Session
  34. Type: DB Data
  35. Type: FilterDefinition
  36. Type: File System
  37. Type: Density Scorer Model
  38. Type: KNFST Model
  39. Type: DLNetworkPortObject
  40. Type: DL4J Model
  41. Type: Spark Context
  42. Type: Spark Data
  43. Type: Normalizer
  44. Type: Python
  45. Type: R Workspace
  46. Type: Remote Connection
  47. Type: Word Vector Model
  48. Type: Keras Deep Learning Network
  49. Type: ONNX Deep Learning Network
  50. Type: TensorFlow Deep Learning Network
  51. Type: DLPythonNetworkPortObject
  52. Type: H2O Context
  53. Type: H2O Frame
  54. Type: H2O Model
  55. Type: MOJO
  56. Type: KafkaConnection
  57. Type: Semantic Web Connection
  58. Type: Weak Label Model
  59. Type: XGBoostModel
  60. Type: CAIM
  61. Type: Spark MLlib Model
  62. Type: Spark ML Model
  63. Type: Color
  64. Type: GNE SDF Port
  65. Type: se.redfield.knime.neo4jextension.neo4jconnector
  66. Type: Workflow Port Object
  67. Type: KnimeConnection
  68. Type: TensorFlow 2 Model
  69. Type: AzureConnection
  70. Type: FileStorePrefixURIPort
  71. Type: Google Drive
  72. Type: Google Cloud Storage Connection
  73. Type: FileStoreReferenceURIPort
  74. Type: AWSConnection
  75. Type: FileStoreURIPort
  76. Type: PMML Discretization
  77. Type: URIPortObject managed by FileStore
  78. Type: Process Tree
  79. Type: KnoxHdfsConnection
  80. Type: Replay Result in Alignment
  81. Type: H2O Driverless AI MOJO
  82. Type: H2O Driverless AI Dataset Connection
  83. Type: se.redfield.bert.nodes.port.BertModelPortObject
  84. Type: se.redfield.bert.nodes.port.BertClassifierPortObject
  85. Type: org.knime.mongodb.connection.port.MongoDBConnectionPortObject
  86. Type: SeleniumFirefoxPort
  87. Type: SP_Conn
  88. Type: se.redfield.bert.nodes.port.BertPortObjectBase
  89. Type: Weka 3.7 Classifier
  90. Type: Weka 3.7 Cluster
  91. Type: org.knime.python3.nodes.PythonBinaryBlobFileStorePortObject
  92. Type: Causal Graph
  93. Type: Hybrid Petri Net
  94. Type: Directly Follows Msd
  95. Type: spaCy pipeline
  96. Type: se.redfield.textprocessing.nodes.port.SpacyModelPortObject
  97. Type: spaCy pipeline
  98. Type: Replay Result in Alignment
  99. Type: Symanto Brain Api Key
  100. Type: org.knime.python3.nodes.PythonConnectionPortObject
  101. Type: org.knime.credentials.base.CredentialPortObject
  102. Type: Report Fragment
  103. Type: AbstractHubAuthenticationPortObject
  104. Type: FSK object
  105. Type: FSK object
  106. Type: FSK object
  107. Type: FSK object
  108. Type: FSK object
  109. Type: PCML PortObject
  110. Type: Email Session
  111. Type: Combined FSK object
  112. Type: Combined FSK object
  113. Type: Combined FSK object

Extension

The CASE Switch End node is part of this extension:

  1. Go to item

Related workflows & nodes

  1. Go to item
  2. Go to item
  3. Go to item

KNIME
Open for Innovation

KNIME AG
Talacker 50
8001 Zurich, Switzerland
  • Software
  • Getting started
  • Documentation
  • Courses + Certification
  • Solutions
  • KNIME Hub
  • KNIME Forum
  • Blog
  • Events
  • Partner
  • Developers
  • KNIME Home
  • Careers
  • Contact us
Download KNIME Analytics Platform Read more about KNIME Business Hub
© 2025 KNIME AG. All rights reserved.
  • Trademarks
  • Imprint
  • Privacy
  • Terms & Conditions
  • Data Processing Agreement
  • Credits