some other information I
can provide.
If it's a configuration fix, then that'll be great - some pointers of where
to look as to which configuration parameters might overcome this issue will
also be good if you have them.
Kind regards
Simon Vicary
rajdavies wrote:
>
> Hopefully
27;fixed in
the 4.1…. Release'. We are using 4.1.1 so we should see the fix - this
sounds like another issue which has slipped though the net.
Any feedback on this would be much appreciated.
Kind regards
Simon Vicary
Integration and Technical Delivery Lead.
--
View this message in co