Releases: redlink-gmbh/smarti
smarti-0.7.6
Smarti v0.7.6 contains bug fixes for the Samrti Widget the Conversation Search and the synchronization of the Conversation Index
New in Smarti 0.7.6
smarti-0.7.5
Smarti 0.7.5 contains a bug fix for the Smarti Widget
New in Smarti 0.7.5
Smarti v0.7.4
Smarti 0.7.4 contains bug fixes to Smarti and the Samrti Widget
New in Smarti 0.7.4
- #225 - Automatic reloading of results does not work as expected
- #249 - CloudSync does not work for deleted Conversations
- #252 - The ConversationWidget is not refreshed correctly
- #255 - Smarti Widget fails to render messages containing code
- #258 - Loading Smarti fails for empty conversations
- #259 - Rocket.Chat legacy endpoint does not filter for conversations marked as deleted
Smarti 0.7.3
Smarti 0.7.3 contains a fix for the Chatpal Backend
New in Smarti 0.7.3
Smarti 0.7.2
Smarti 0.7.1
Smarti 0.7.1 is contains several improvements for analysis quality and some bugfixes.
New in Smarti 0.7.1
- #203 - Preamble of posted conversation / message must not be analyzed
- #208 - Ignore code-blocks in analysis
- #217 - Indicator for Queries that they are not valid without user added tokens
- #227 - Make i18n messages (preamble of posted conversation) configurable
- #228 - Allow to disable Filters for related Conversations
- #236 - "Context" does not provide enough context
- #220 - Improve UI message if no results are found
- #230 - Improve toggle conversation context in the Smarti widget
- #239 - Posting a result from the Smarti-Widget
- #242 - Clicking the include Message checkbox expands the Result
- #243 - Change "Konversation Posten" to "Nachricht Posten"
- #225 - Bug: Automatic reloading of results does not work as expected
- #232 - Bug: Put a message which does not exist results in error 500
- #237 - Bug: Widget: "Post selected messages" button is not shown when room is closed
- #238 - Bug: Widget does not render Results
- #240 - Bug: Conversation Context broken
- #241 - Bug: Posts of SolrSearch DataSources does not work
Upgrading
To ensure that the improved analysis result is available for all users, you should clear the collection caching analysis results.
A migration script is available. If you are not using one of the provided installation packages (deb, rpm) or docker, you must apply it manually:
db.getCollection('analysis').drop();
db.getCollection('smarti')
.update({_id: 'db-version'}, {
$set: {
version: 6
}
});smarti-0.7.1-RC3
[maven-release-plugin] copy for tag smarti-0.7.1-RC3
smarti-0.7.1-RC2
RC2 for 0.7.1
smarti-0.7.1-BETA
Known Issues:
- The upgrade script for the Smarti MongoDB is not part of this release. Because of this one needs to manually clear the
analysiscollection (clean the analysis cache)
Smarti 0.7.0
Smarti 0.7.0 is a refactoring release, and introduces an improved webservice API.
New in Smarti 0.7.0
- #86 - New Conversation API
- #148 - Improved Smarti-Widget
- #183 - Chatpal-Search support
- #184 - Admin UI - Default configuration is not loaded
- #185 - Admin UI - Change Client deletion dialog
- #189 - Token based Related Conversation
- #191 - Support indexing/search of ongoing Conversations
- #192 - Conversation MLT-Query-Builder should only use recent messages
- #193 - Special characters in configuration keys cause MongoDB-Exceptions
- #196 - Admin UI - Rename button "Clone" to "Clone Configuration"
- #200 - Tempaltes and Queries need always be built
- #201 - The conversationsearch query builder shall consider Tokens
- #205 - Smarti-Widget - Analysis result cleared on post message
- #206 - Smarti-Widget - No results without keywords
- #207 - Smarti-Widget - No releated conversations found/displayed
- #209 - Chatpal-Integration: No client support
- #210 - Smarti-Widget - Paging/Endless-Scroll
- #211 - Smarti-Widget - highlight pinned tags
- #216 - Admin UI - Copying the default configuration => new default
- #218 - Basic Context Analysis
Upgrading
With 0.7.0, the datamodel has changed so data from older installations
must be migrated to the new model.
A migration script is available. If you are not using one of the provided installation packages (deb, rpm) or docker, you must apply it manually:
var conversations = db.getCollection('conversations');
conversations.update({tokens: {$exists: true}}, {
$unset: {
channelId: true,
tokens: true,
queryTemplates: true,
'meta.lastMessageAnalyzed': true
}
}, {multi: true});