Top level languages from now on won’t have flags by default. Flag on top level may appear only for custom languages having country code. Normally flags will be shown on term level when Region is specified for it.
Dictionary history update
History of dictionary from now on will determine properly point in time to which is possible to revert changes. Modifications of labels, description, adding new fields or languages won’t block ability to see older history records. Only removal of fields or languages, and changing field type will block access to previous items in the past.
With this release cloud installations will check for viruses all uploaded files. Of course it also available for on-premise installations, see settings for configuration.
User lockdown after failed login
This release brings new protection feature which will lock user account for small amount of time after several failed login attempts as well as ip address after flooding server with login attempts to several users. You can check configuration
Speedup initial render
We improved speed 3x times faster of initial loading of application comparing to version 4.0.6. This improvement mostly visible to guest users which are accessing TermWeb without entering password, for normal users page refresh is working faster. To achieve better results we recommend enabling of http/2 protocol.
Dictionary REST API
This version provides new API endpoint to manage all Dictionaries in TermWeb, you may find documentation here.
More strict XML processing
TermWeb won’t process any external xml schemes or doctypes containing xml entities.
CDN is now disabled by default
We disabled from this version use of CDN servers (was in use for Bootstrap, jQuery, dojo and fontawesome). All required files included in distributive.
Configurable password recovery token expiration
Before this release it was impossible to modify recovery token expiration. See here for configuration.
Stronger passwords hashing
TermWeb will store all new passwords by using key derivation function. Check these settings.
Guest user no longer part of “All users” group
We’re removing ambiguity from our installations when Guest user sometimes was a part of “All users”, sometimes - no.
[TWC-1544, TWDESK-2805] - E-Mail notifications Enable TLS (SSL) We’ve added support of STARTTLS command to TermWeb for smtp connections:
If true, enables the use of the STARTTLS command (if supported by the server) to switch the connection to a TLS-protected connection before issuing any login commands. If the server does not support STARTTLS, the connection continues without the use of TLS; see the email.starttls.required property to fail if STARTTLS isn't supported. Note that an appropriate trust store must configured so that the client will trust the server's certificate.
If true, requires the use of the STARTTLS command. If the server doesn't support the STARTTLS command, or the command fails, the connect method will fail.
[TWC-1546, TWDESK-1749] - Add possibility to open images from preview in new tab. Allow to user play audio file.
For small audio files (less than 5MB) TermWeb will show element for playing audio file.
[TWC-1167] - Adding another term should make cursor focus on new set of term fields
[TWC-1171, TWDESK-1571] - Fixed problem with client mapping for external system administrators.
Makes it possible to enable "UniNE" (Light Stemming Approaches for the French, Portuguese, German and Hungarian Languages). This updates includes support of the following characters: 'ä','à','á','â','ö','ò','ó','ô','ï','ì','í','î','ü','ù','ú','û'.
api.stem.german.filter.factory.class termweb.properties key for configuration. By default configured to use org.apache.lucene.analysis.de.GermanLightStemFilterFactory
To restore TermWeb 3 behaviour use: org.apache.lucene.analysis.de.GermanMinimalStemFilterFactory
Two additional settings options to enable with: "org.apache.lucene.analysis.de.GermanStemFilterFactory" or "org.apache.lucene.analysis.snowball.SnowballPorterFilterFactory"
[TWC-1433] - Change default value for "api.new.user.is.admin" to false
[TWC-1071] - Norwegian & Vietnamese common regions updated
[TWC-1179] - Double relations show in result window in specific
[TWC-1193] - Workflows: E-mail notifications to "HTML Reports" do not show columns when reopening
[TWC-1392] - Issues opening concept history when it contains changes to a deleted language.
[TWC-1388] - After failed login user might see incorrect login pages.
[TWC-1395] - TermWeb Integrator synchronization failing due to incorrect indexes.
[TWC-1396] - TermWeb Integrator cannot export concepts because permission check for sync settings.
[TWC-1158] - Incorrect symbols in specific language names and variants (Provençal, Gwich'in, Wolapük).
[TWC-1231] - Domains are duplicated in display for subsets of sub-domains.
[TWC-1383] - Issues with term decoration when API template is sharing Dictionary and Sections within same Dictionary.
[TWC-1398] - Terminology in XTM not displaying correctly due to error in OpenId login.
[TWC-1403] - Automatically create API group when it does not exists and is specified in termweb.properties.
[TWC-1404] - Show proper message on API login when user is missing.
[TWC-1405] - API login made configurable to login API user as guest (ex via XTM terminology window).
[TWC-1406] - Make users created via API login part of “All users” group automatically.
[TWC-1410] - “Owner” visibility for Filters missing.
[TWC-1411] - Restore concept not available for concept history.
[TWC-1413] - Issues with cross-references not working.
[TWC-1414] - Search for Empty/Non empty Domain condition in Filter.
[TWC-1416] - Quick Filters list shown alphabetically
[TWC-1417] - Term decoration may work incorrectly for multitenant installation.
[TWC-1418] - Issues with restoring concept history.
[TWC-1419] - Cannot save Quick Filter as a normal filter.
[TWC-1421] - Staging Areas: User settings for Term- or Concept-level fields in Staging Areas not stored
[TWC-1422] - Workflows - Empty list of Permissions Schemes
[TWC-1440] - Concept drafts inaccessible in StagingArea after Dictionary structure change
Update actions for hotfix-9
If you’re upgrading from version less than 4.0.5-2 you need to do next actions:
Prior to start tomcat with new version update your database with next script:
ALTER DATABASE `<scheme_name>` CHARACTER SET = utf8mb4 COLLATE = utf8mb4_general_ci;
ALTER TABLE `schema_version` CONVERT TO CHARACTER SET utf8mb4 COLLATE utf8mb4_general_ci;
ALTER TABLE `schema_version` CHANGE `description` `description` varchar(200) CHARACTER SET utf8mb4 COLLATE utf8mb4_general_ci NOT NULL;
ALTER TABLE `schema_version` CHANGE `installed_by` `installed_by` varchar(100) CHARACTER SET utf8mb4 COLLATE utf8mb4_general_ci NOT NULL;
ALTER TABLE `schema_version` CHANGE `script` `script` varchar(1000) CHARACTER SET utf8mb4 COLLATE utf8mb4_general_ci NOT NULL;
ALTER TABLE `schema_version` CHANGE `type` `type` varchar(20) CHARACTER SET utf8mb4 COLLATE utf8mb4_general_ci NOT NULL;
ALTER TABLE `schema_version` CHANGE `version` `version` varchar(50) CHARACTER SET utf8mb4 COLLATE utf8mb4_general_ci NULL;
Modify database connection string by replacing characterEncoding=UTF8 with character_set_server=utf8mb4&connectionCollation=utf8mb4_general_ci in termweb.properties file.
[TWC-1375] - Certain metadata (dictionary, section, language) from TermWeb entries are not displayed in XTM term recognition
[TWC-1376] - Impossible to export dictionary with old attachments when file type is unsupported.
If you’re upgrading from previous version and using OpenId integration with XTM (Terminology window) installed on domain different than https://www.xtm-cloud.com you need to do next actions:
In termweb.properties file check that property allow.inside.iframe has value true. Add new property allow.inside.iframe.frameancestors with value like this: 'self' https://*.xtm-cloud.com Replace xtml-cloud.com with your XTM installation url. This value will be included to response for OpenId authentication callback as CSP: frame-ancestors header (check docs on MDN).
[TWC-1221] - Filters - Implement Empty / Not Empty for multiselect, picklist, date, number fields
[TWC-1313] - SSO login using SAML2 Identity provider
[TWC-1317] - After dictionary structure change or reindex staging areas remains locked
[TWC-1319] - Impossible to enter new license before license expiration.
TermWeb 4.0.3-hotfix2 (11 July 2020)
Improvements / Feature requests
[TWC-1264] - Feature request: Error message when using incorrect values for Picklists or Multivalue fields
[TWC-1286] - Unify icons and actions in Staging area
[TWC-1311] - Speedup bulk operations in Staging operation (publish, update field values, clear)
[TWC-1147] - Guest users settings stored in browser cache (it allows to work them concurrently) Now administrators can disable Quick Filters, Filters, Search modes (domains, multifield search), Staging areas, Commenting for guest users
[TWC-1264] - Feature request: Don't allow to use incorrect values for Picklists or Multivalue fields
[TWC-1190] - Migrated Filters referring to username are switched with id
TermWeb 4.0.2-hotfix8 (12 June 2020)
[TWC-1107] - Termweb UI client loads history four times for Concept instead of one (performance issue)
[TWC-1160] - Export throws to blank page when attachments included to it.
[TWC-1187] - Editing concept. Text written before Save is truncated (Firefox issue)
[TWC-1204] - Bugs in workflows related to date fields
TermWeb 4.0.2-hotfix7 (8 May 2020)
[TWC-994] - Impossible to delete ConceptDrafts from old staging area created in previous version of TermWeb
Some Concepts that were still in a Staging Area after a hotfix update couldn't be removed.
[TWC-1177] - TBX data category values shown in camelCase
TBX-values will now display values as determined in Dictionary structure when viewing Concepts in the SearchView. Replaced TBX-values, those with a "(TBX)" tag, will still export their TBX-data value in exported files.
[TWC-1202] - Publishing a new concept from Staging area does´not publish concept
Concepts created in Staging Areas would not publish, and therefore create, new concepts.