Define how Scroll Office should communicate with Confluence
When exporting images and loading other resources, HTTP(S) connections to the current Confluence instance may be opened.
The automatic resource loading URL detection that is currently used fails in several more complex scenarios and also in some standard scenarios depending on reverse proxy configuration.
To better help customers in such cases, we've made the manually specify a resource loading base URL for usage during exports. This URL should ideally point to a Tomcat HTTP connector.. Confluence Administrators can now
Improved export of alignment in table styles
The alignment defined in table styles is now applied to all paragraphs in tables.
Improved image handling
For image URLs where it is known in advance that the in-process loader can load them, Scroll Office now tries the in-process approach before the HTTP approach.
For example all images attached to pages where no image effects are applied are now loaded this way. Using this approach should avoid problems in environments with complicated network setups and should be faster than the current image loading.
Updates and Fixes in this Release
The Scroll Office 3.1 Team