[HOP-4457] HOP-Server: Switch/case transform always uses default path

• Type: Bug
• Status: Closed
• Priority: Normal
• Resolution: Fixed
• Affects Version/s: 2.0.0
• Component/s: Hop Server
• Assignee: Shl Xue
• Reporter: kboersch
• Created: 11/Oct/22 14:57
• Updated: 20/Mar/23 09:03
• Resolved: 20/Mar/23 09:03

Description

It seems, that the switch/case transform always uses the default path under following circumstances:

Parent-WF "testWF" with remote run config calls pipeline "testSwitch" with local run config.

Pipeline "testSwitch" generates some rows, adds sequence and maps some values in field "SWH" depending on sequencenumber and finally calls another pipeline "logging" with SWH as parameter and local run config as well.

Pipeline "logging" gets SWH as variable and switches cases depending on SWH, then writes something in the log.

 

I created this case to simulate what my origin WF does. As it's far more complex I tried to reconstruct it that way.  Behaves exactly, as it does in the origin, where I use the filter rows transform as workaround.

I'll attach the three HWF/HPL files as well, as the Log-Output.

Ran on the local machine it works properly.