As long as you're doing HMI stuff, wireless is probably fine. Wireless will have much higher latency (communication delay) and jitter (randomness in communication delay) than wired Ethernet, so you want to probably stick to programming or non-critical communications unless you take a serious look at it first.
IT guys will want to keep IP subnets as small as possible, and then have routers with firewalls between everything, to limit communication. This is probably fine, but is the opposite of how controls guys usually think, where we WANT everything to be able to talk as much as possible.
I'd say you should make sure you're familiar with whatever communication mechanism you're using between the Clicks and other devices (I'm not familiar with them).
If it is MAC address based (Layer 2), then you may have some interesting challenges communicating across the wireless bridge, unless the bridge especially supports that. You also won't be able to go across routers. This probably doesn't apply to you.
Odds are you are talking over IP. This means you probably need to make sure you know what IP addresses are involved. You ALSO should know if you're doing any sort of traffic it is: unicast, multicast, broadcast. If the majority of the traffic isn't unicast (1 device to 1 device), you may run into trouble on wireless, and performance may suffer.