Solved

Filename selector in new Branch connector fails

  • 28 August 2023
  • 5 replies
  • 68 views
RichardG
Userlevel 1
Badge

I started using the new Branch connector with an existing AS2 connector. The Branch connector will be used to save specific messages based on the Filename to a different folder.

I've setup the Branch connector as shown in the image provided in the Help for the Branch connector.
IF Filename matches glob CUS*.*

But instead of the output being send to the provided File Connector to save the message in a different folder, the message is forwarded to the ELSE clause and forwarded to that attached connector.

The log-file shows the following information (not really helpful at the moment):

[2023-08-25T15:36:47.403] [Info] CUSDEC325-0000000000062014 is routed to File_SHPP2MEP_Test (which is the ELSE clause). [2023-08-25T15:36:47.403] [Info] Message CustomerAS2_TEST-20230825-153646575-eCIr is finalized. Name: CUSDEC325-0000000000062014, Type: Output, Status: Success, Message: , Processing Time: 16ms. [2023-08-25T15:36:47.403] [Info] Arc Version: 23.2.8606.0 [2023-08-25T15:36:47.403] [Info] System Version: Microsoft Windows Server 2022 Standard [2023-08-25T15:36:47.403] [Info] VM Version: 4.0.30319.42000 [2023-08-25T15:36:47.403] [Info] Message CustomerAS2_TEST-20230825-153646575-eCIr is finalized. Name: CUSDEC325-0000000000062014, Type: Input, Status: Success, Message: , Processing Time: 16ms.

 

 

Some additional info in the files/messages that we receive:

The message format is EDIFACT, so I have to use the Filename selector.
The message has no file extension.

 

icon

Best answer by Ankit Singh 28 August 2023, 11:52

View original
At the end of each great post, there is a disappointing signature

5 replies

Ankit Singh
Userlevel 5
Badge +1

Hey @RichardG 

The New Branch connector should allow you to add multiple Branch logic with a single Branch connector. It looks like the challenge you are facing has more to do with configuration. Can you please share a screenshot of your workflow that explains the current logic you have created?

That Solutions Guy
RichardG
Userlevel 1
Badge

Hey @Ankit Singh,

This is the workflow:

Workflow

And these are the settings for the Branch connector:

Branch Connector Settings

And this is the Input(/output) page, where you can see the processed files:

Input tab

 

The files that start with CUSDEC325 should have been sent to the File_SHPP2ES_Test connector.
 

At the end of each great post, there is a disappointing signature
RichardG
Userlevel 1
Badge

PS.
I noticed this morning that another connection has the same issue.

In that case we check for the extension of the file. I've recently replaced the now discarded FileMatch connector with the new Branch connector, but all files are sent via the Else clause, instead of the case selector.

For that Branch connector i've used the same IF filename matches glob setting.

At the end of each great post, there is a disappointing signature
Ankit Singh
Userlevel 5
Badge +1

Hi @RichardG 

Can you replace the filter condition with ‘CUS*’ ?

I believe setting it to ‘CUS*.*’ is expecting the Branch connector to look for a ‘.’ in the filename which includes extensions.
So ideally, the Branch connector will only pass a file named CUSXXXX.XXX which is NOT matching the input files you are expecting it to pass.

That Solutions Guy
RichardG
Userlevel 1
Badge

@Ankit Singh 

That was the solution for the issue with this connector. By removing the ".*” the files without a file extension are checked as well.


Thank you very much

At the end of each great post, there is a disappointing signature

Reply


Virtual Event: Data Virtualization, Reimagined Ma”arch 14, 2024 style=
Terms and ConditionsCookie settings