7.14.1
Clarive 7.14.1 Release Notes¶
Release date: 11 December 2024
We're pleased to present our new patch release of Clarive 7.14.1 with some important new features and bugfixes:
Highlights¶
- Stream temp files location
- Limit file size of topic attachments
Stream temp files location¶
In fault tolerance implementations of Clarive where there are several servers running either web or dispatcher
it was not possible to open live streams in job logs unless the web server connected was in the same machine
in which the job was running. That was caused because the temp file for the log stream was created in the CLARIVE_TEMP
directory that most of the times is not shared among servers.
Now the temp stream files are created in CLARIVE_LOGS/streams
directory that is normally shared. There's also a
config variable for this location named log_stream_dir
that can be configured to point to any shared fs in the servers.
Limit file size of topic attachments¶
Until this version it was not possible to limit the size of the files uploaded as attachments to topics. Now you can
configure a global limit in the config file with the variable attachment_max_size
(number of MB) and you can also specify
a Max Size in the upload files fieldlet configuration in the form rule.
More improvements and issues resolved¶
- [ENH] #2092 Sort in Kanban boards
- [ENH] #2957 Bulk assign labels from topics grid
- [ENH] #3126 Create release from topics grid
- [ENH] #3146 UI restyle of topic grid
- [ENH] #3163 Topic grid UI ago and icons
- [ENH] #3181 uid in CIs can be an array
-
[ENH] #3199 Limit file size of topic attachments
-
[FIX] #3112 MongoC failure in job report
- [FIX] #3136 Role scopes for field permissions show "Any" when field does not exist
- [FIX] #3145 Failed services become a dispatcher
- [FIX] #3168 Create resource throws server error of undefined mid
- [FIX] #3198 Stream temp files should be located in logs dir
Ready to upgrade?¶
Just follow the standard procedure for installing the new version. Click here to get it from our Install page.
Acknowledgements¶
Join us in our Community to make suggestions and report bugs.
Thanks to everyone who participated there.