Skip to main content

When the third party generates the response file for an OUT file, an additional ‘.res’ file is also created, which they have no control over. This file is being read by the IFS application without any routing rule. Is there any way to ignore this in IFS Cloud? The file is not matching any available routing rule, and the application message fails as shown below.

 

 

Thanks & Regards,

C.patabendi

If the file reader sees it and creates an application message for it, it probably because the filename pattern matches the file reader configuration.

The routing rules and addresses come AFTER that point of the workflow, so they’re not really the cause or resolution to your situation here.

 

 

You need to specify that if you want to only read specific files matching a specific pattern to be read and grabbed by the file reader.

 

 


Reply