[BUG] Set "Response Timeout" to a channelMap in a TCP Sender

[mpapini64]

Hello, why is it possible to assign a timeout value assigned by a channelMap/cfgMap to the Send Timeout box of an HTTP Sender, while the same channelMap/cfgMap cannot be assigned to the "Response Timeout" box of a TCP Sender?
Is it an oversight or is this behavior intentional, in the latter case could we know the reason?

Mirth Version 4.4.1

[mpapini64]

I haven't heard back in two weeks... :|

[pacmano1]

Haha, like your stuff gets prioritized over all the other stuff here?

All kidding aside, if you pay for mirth, open a ticket. If you don't, your "bug" is probably a feature request. Even then though, there is no guarantee of a response from Nexgen.