For outbound files you should be able to just route it via the FILE_SENDER to a non-existing folder. The Application Message will then fail but you should be able to see the final file (after transformers have been applied etc.) in the Application Messages.

Thanks Jonas, 
If I remember correctly, this will create an xml file in Application Messages even if we specify a csv file in Routing Address> output file. 
However this is not a problem as it has the correct data structure.

Any reason why IFS Documentation says we can test text files using IFS Developer Studio?
I could not find such an option in IFS Developer Studio.

That is a very good question that I unfortunately can’t answer either :(

I’m also exactly not sure what it meant in the documentation and my interpretation is as follows:

To create a test file output using IFS Connect, you should develop a transformer. Transformer development can be done using the developer studio and you can test the output locally.

read more about transformer development here: About Transformer Development - Technical Documentation For IFS Cloud

Hope it helps!

Damith

@dsj ,

Thanks Damith. 
Yes, I do have experience in Transformer development.
However, what I would like here to is to test a Text file without touching a Transformer.
As @Jonas Feigl suggested, checking the Application Message is the best option here for the time being.

Best regards
GaSoGB