Content Quality 7.8.0
The HttpApiAnnotator can now be configured with an experimental flag that appends to documentId to the endpoint as a query string parameter.
Allow Content Quality to be disabled on bootstrap for a specific session using `
configuration`. Disabling Content Quality will hide the sidebar and makes sure Content Quality cannot be re-enabled during that session.
The response of the health endpoint has been amended with product and version information. For details, please refer to the monitoring section.
Self-contained builds for Windows can now run as Windows Service by specifying the
--as-windows-servicecommand line argument.
NLog configuration files are now supported. See configure the backend for more details.
AP I changes
Hosting__property in the backend configuration has been discontinued. From now on use ASPNETCORE_URLS to set the protocol, host and port to listen on. This means that port 6000 is no longer the default hosting port when running without FDT. FDT still defaults to port 6000 for Content Quality.
Content Quality now works with the IFrame connector when adding the fontoxml-connectors-iframe dependency.
The Content Quality backend will now log its name and version during startup.
We introduced a new operation called `
content-quality-show-annotation-details` that can be used to open up the details of a given annotation id.