Hub
NodeNode / Manipulator

CASE Switch Start

Workflow Control Switches
Drag & drop
Like
Copy short link

This node routes its input to a selectable output port, allowing different branches of the workflow to be activated manually or using a flow variable. The input port type can be chosen when adding an input port using the “…” menu. The type can be changed by removing the input port and adding it again.

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

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.
  1. Type: Table
  2. Type: Flow Variable
  3. Type: MOE Model
  4. Type: Image
  5. Type: Distance Measure
  6. Type: PMML
  7. Type: Naive Bayes
  8. Type: Cluster Tree
  9. Type: Sota
  10. Type: Regression Tree
  11. Type: Regression Tree
  12. Type: PortObject
  13. Type: Feature Elimination
  14. Type: Correlation
  15. Type: Feature Selection Model
  16. Type: Transformation
  17. Type: Radial Basis Function
  18. Type: Rowset Filter
  19. Type: PCA
  20. Type: Fuzzy Basis Function
  21. Type: LibSVM
  22. Type: Tree Ensembles
  23. Type: Gradient Boosting Model
  24. Type: Tree Ensembles
  25. Type: Weka 3.6 Classifier
  26. Type: Weka 3.6 Cluster
  27. Type: Weka 3.7 Classifier
  28. Type: Weka 3.7 Cluster
  29. Type: Weka Classifier
  30. Type: Weka Cluster
  31. Type: Outlier
  32. Type: Network
  33. Type: OpenNlpNerTaggerModelPortObject
  34. Type: StanfordNERModelPortObject
  35. Type: DocumentVectorPortObject
  36. Type: VectorHashingPortObject
  37. Type: JChem Database Connection
  38. Type: Fingerprint Bayes
  39. Type: URI Object
  40. Type: Arx Config
  41. Type: XLS Formatter
  42. Type: de.tarent.cumulocity.connector.CumulocityPortObject.TYPE
  43. Type: Binning Port Object
  44. Type: de.mpicbg.knime.scripting.r.port.RPortType2
  45. Type: Moz API Connection
  46. Type: Twitter
  47. Type: URI Object
  48. Type: se.redfield.node.port.orientdb.connection
  49. Type: Portable Format for Analytics
  50. Type: Event Log
  51. Type: Petri Net
  52. Type: Directly Follows Model
  53. Type: Database Query
  54. Type: Database Connection
  55. Type: AWS Comprehend Connection
  56. Type: DB Session
  57. Type: DB Data
  58. Type: Google API
  59. Type: FilterDefinition
  60. Type: File System
  61. Type: Density Scorer Model
  62. Type: KNFST Model
  63. Type: Arima
  64. Type: DLNetworkPortObject
  65. Type: DL4J Model
  66. Type: Spark Context
  67. Type: Spark Data
  68. Type: Normalizer
  69. Type: Python
  70. Type: R Workspace
  71. Type: Remote Connection
  72. Type: Word Vector Model
  73. Type: Word Vector Model (deprecated)
  74. Type: Keras Deep Learning Network
  75. Type: ONNX Deep Learning Network
  76. Type: TensorFlow Deep Learning Network
  77. Type: DLPythonNetworkPortObject
  78. Type: Google Sheets
  79. Type: H2O Context
  80. Type: H2O Frame
  81. Type: H2O Model
  82. Type: MOJO
  83. Type: Lucene
  84. Type: KafkaConnection
  85. Type: Compiled PMML
  86. Type: Neighbourgram
  87. Type: Universe
  88. Type: OPTICS Clustering Port
  89. Type: Semantic Web Connection
  90. Type: Weak Label Model
  91. Type: XGBoostModel
  92. Type: PMML Preprocessing
  93. Type: CAIM
  94. Type: Python
  95. Type: Python (deprecated)
  96. Type: Google Analytics
  97. Type: Large Filestore
  98. Type: Spark MLlib Model
  99. Type: Spark ML Model
  100. Type: Color
  101. Type: Shape
  102. Type: Size
  103. Type: GNE SDF Port
  104. Type: se.redfield.knime.neo4jextension.neo4jconnector
  105. Type: Workflow Port Object
  106. Type: Microsoft Credential
  107. Type: KnimeConnection
  108. Type: TensorFlow 2 Model
  109. Type: Spark Data Legacy
  110. Type: AzureConnection
  111. Type: FileStorePrefixURIPort
  112. Type: Google Drive
  113. Type: Inactive branch
  114. Type: Keras Deep Learning Network
  115. Type: Spark Context Legacy
  116. Type: Spark Data (legacy com)
  117. Type: Google Cloud Storage Connection
  118. Type: Spark Model Legacy
  119. Type: FileStoreReferenceURIPort
  120. Type: AWSConnection
  121. Type: FileStoreURIPort
  122. Type: PMML Discretization
  123. Type: Ligand-Set
  124. Type: URIPortObject managed by FileStore
  125. Type: Process Tree
  126. Type: Salesforce OAuth2 Connection
  127. Type: KnoxHdfsConnection
  128. Type: Spark Model (legacy com)
  129. Type: Keras Deep Learning Network
  130. Type: Spark Context (legacy com)
  131. Type: Replay Result in Alignment
  132. Type: H2O Driverless AI MOJO
  133. Type: H2O Driverless AI Dataset Connection
  134. Type: se.redfield.bert.nodes.port.BertModelPortObject
  135. Type: se.redfield.bert.nodes.port.BertClassifierPortObject
  136. Type: RPortObject
  137. Type: PDB Advanced Query Port
  138. Type: com.schrodinger.knime.port.connection
  139. Type: DirectAccessTablePortObject (for testing)
  140. Type: org.knime.mongodb.connection.port.MongoDBConnectionPortObject
  141. Type: SeleniumFirefoxPort
  142. Type: SP_Conn
  143. Type: se.redfield.bert.nodes.port.BertPortObjectBase
  144. Type: Weka 3.7 Classifier
  145. Type: Weka 3.7 Cluster
  146. Type: Weka 3.7 Classifier
  147. Type: Weka 3.7 Cluster
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.

    Extension

    The CASE Switch Start node is part of this extension:

    Related workflows & nodes

    1. Chapter 7 / Exercise 1
      Books KNIME Advanced Luck Exercise
      +1
      In this exercise, we generate numbers from 1 to 10 and we multiply even numbers by 3 and …
      rs1 > Public > KNIMEPress > KNIME_Advanced_Luck_4.5_2022011 > AdvancedLuck > Chapter8 > Exercises > Exercise 1
    2. Dynamic Port Edge Cases
      phisch > Public > Dynamic Port Edge Cases
    3. Chapter 7 / Exercise 2
      Books KNIME Advanced Luck CASE Switch
      +2
      This workflow processes data differently depending on day of the week, which is a very co…
      rs1 > Public > KNIMEPress > KNIME_Advanced_Luck_4.5_2022011 > AdvancedLuck > Chapter8 > Exercises > Exercise 2
    4. CASE Switch
      Books KNIME Advanced Luck CASE Switch
      +2
      The goal of this workflow is to classify the car makers based on the cars they produce. T…
      rs1 > Public > KNIMEPress > KNIME_Advanced_Luck_4.5_2022011 > AdvancedLuck > Chapter8 > 4. CASE Switch
    5. Empty Table Switch
      Books KNIME Advanced Luck Empty Table Switch
      +2
      In this workflow we select one car maker and type of drive wheels. We then move to a CASE…
      rs1 > Public > KNIMEPress > KNIME_Advanced_Luck_4.5_2022011 > AdvancedLuck > Chapter8 > 5. Empty Table Replacer
    6. Workflow Control - Solution
      Loop Reading many files Switch
      +3
      Solution to exercise 11 for the KNIME Analytics Platform for Data Wranglers course - Writ…
      scottf > Public > Cargill_Workshop > Solutions > 11_Workflow_Control_Solution
    7. Workflow Control - Solution
      Loop Reading many files Switch
      +3
      Solution to exercise 11 for the KNIME Analytics Platform for Data Wranglers course - Writ…
      knime > Education > Courses > L2-DW KNIME Analytics Platform for Data Wranglers - Advanced > Solutions > 11_Workflow_Control_Solution
    8. Cascading Dialogs to Dashboard
      Cascade Cascading Dynamic
      +3
      This is an example of a Single-Page Dynamic application built using exclusively KNIME nod…
      knime > Examples > 09_Enterprise > 02_WebPortal > 14_Dynamic_Data_App_Cascading_dialogs
    9. Control_Workflow
      kathrin > Forum Questions > Combine multiple reports in a Dashboard > Control_Workflow
    10. Anomaly Detection. Control Chart
      Anomaly detection Time series analysis IoT
      +4
      This workflow performs anomaly detection using a control chart: - Calculate the "normal c…
      knime > Codeless Time Series Analysis with KNIME > Chapter 11 > 04_Creating_a_ControlChart_of_a_Time_Series