What's new
What’s new in Inflow 4.1
Operational features
- Environment variables to configure logging and Access logging in
JSON format
Technical changes
- Removed legacy CMIS properties
- Removed legacy Rest API
- Building with Spring Boot Gradle Plugin
- Use the
server.servlet.context-path to set the application
context-path
Bug fixes
- Validation and warning for DNS Cache TTL
- Fixed Flux map null handling in input package pipeline
transformation
- Fixed moving the file attempts reading non-existing target file
before move
- Fixed broken job configuration file upload
- Fixed cycles history: number od uploaded files and JobModel table
name
What’s new in Inflow 4.0
In this major release we implemented some UI, parser and operational
features to improve the everyday experience of working with Inflow.
Apart from that we updated the dependencies and cleaned up a lot of
leftovers. Most importantly, Inflow is now a Spring Boot application,
bundling it’s own application server.
These changes require some configuration updates from our clients that
are documented on https://docs.xenit.eu/alfred-inflow .
UI improvements
- Filter job history by period
- Order job list by destination server
- Filter in report UI e.g. filter on status
- Search in report UI e.g. search on file name
Parser features
- Set content type if available: It is now possible to specify the
content type (mimetype) in the parser and avoid guessing.
Operational features
- Implement Actuators health & info: Monitoring endpoints for Inflow.
Technical changes
- Move to Spring Boot and Java 17: Inflow is now a Spring Boot
application. No need to install a Tomcat anymore. We also updated
the Java version.
- Update packages from move2alf to inflow: Completing the renaming
from the old Move2alf to Inflow in the source code.
Bug fixes
- UI allows duplicate keys on metadata object.
- Export csv export fails for big reports at DB level (unbound,
nonpaged query)