Batch server — Java Bridge fallback for HTTP calls
Issue
An HTTP call could work interactively but fail when inbound or outbound flows ran on the batch server.
Impact
Scheduled tasks could fail to retrieve or transmit invoices even though interactive processing worked.
Fix
A Java Bridge fallback mechanism has been added for the relevant calls when the standard Sage X3 call cannot be used in batch mode. The standard call retains priority, and interactive operation is preserved. Fallback requires a Java Bridge accessible from the batch server.
Expected result
e-InvoiceLink processing remains compatible with the batch server without requiring Java Bridge when the standard HTTP call works, while providing an explicit, traceable fallback mechanism.