In this version, we've added some security and functional enhancements and fixed a few bugs.
You can now create multiple-choice fields in the Terminology Manager
Previously, you could only add multiple domains to a term. Now, you can create multiple-choice custom fields that work in the same way as the domain field. For example, you could create the custom field "product" and associate multiple products with a term. We've updated all areas of the Terminology Manager so that you can search, sort, batch-edit, export and import multiple-choice fields. We hope this feature helps you organize your terms in new and better ways.
We made several changes to improve the overall security of our software:
You can now configure the core server and language servers to communicate over HTTPs
We now display the API key required for API-based monitoring
If you monitor the performance of your Acrolinx installation via API-based monitoring, we now display the required API key on the Monitor Performance page in the Dashboard.
Administrators can now use the POSIX installer for unattended installations
Previously, the POSIX installer always required user inputs. While this is still the default installation method, administrators can now also start the installer in unattended mode where the installer uses default options.
The term browser was originally intended to let anyone in your company look up terms without requiring an Acrolinx account and user license. However, if your Acrolinx server is exposed to the internet, you'll probably want to prevent the general public from being able to look up terms. You can now do this by setting a core server property
Once you've made this change, anyone who opens the term browser will be prompted to enter their Acrolinx login details. Additionally, they'll need a password and the privilege "Log on to the term browser" to successfully log on. This privilege is included in the built-in role "Term Browser User". Give anyone this role and they'll be able to log on to the term browser.
You can now secure access to Scorecards and reports by adding the line privacy.secureReportDownloads=true to the core server properties. When this feature is enabled, Scorecards and reports are protected with an API key that gives anyone access for one hour. After that, anyone who wants to open an expired Scorecard or report link must log in to Acrolinx and have the new privilege "View Scorecards and reports.
We've added a new privilege "View Scorecards and reports"
You can use this privilege in combination with the new Scorecard and report security feature. Even if you don't enable that feature, you can still use the privilege to control who has access to Scorecards in the Analytics section the Dashboard.
We've improved the installation process for Unix-based operating systems:
You can now install the server in non-interactive mode
You can now start the installation script in non-interactive mode with the
option like this
sh installer.sh -batch
. Additionally, you can use the option
to create a parameters file that the installation process can use. These improvements are designed to help you automate the installation process as much as possible.
You can now install init scripts on Red Hat Enterprise Linux (RHEL)
When you run the installation script on RHEL, you can use the option
to install init scripts. These scripts ensure that the Acrolinx server automatically starts when you reboot your system. You can also use the option
to remove them again. You can use these options after you have completed the main server installation procedure. You cannot use them during the server installation process. If you use RHEL, this improvement means that you no longer have to create init scripts yourself.
The installation script now creates a configuration directory for each server version
By default, the server installer now creates the configuration directory at the following location:
The installer always creates a configuration directory that's specific to your server version. The placeholder
indicates the version of the server that you're installing.
For example, if you're installing version 4.5 of the Acrolinx server, a configuration directory would be created at the following location:
If you upgrade from an older version, the installer copies the configuration directory from the previous version. That way, you can continue using your previous configurations in the new location. Additionally, you'll have an archive of your configurations from previous server versions.
We've added a script that you can use to start all servers at once
You can now run the command
to start all of your installed servers at once rather than having to run the individual startup commands.
Terminology administrators can now again define the size of text fields
When adding custom text fields to the term pages, administrators can now once again define the size of these text fields.
The scorecard inserted unnecessary line breaks
It was possible that the Scorecard contained unnecessary line breaks in the suggestions. When writers copied these suggestions back into the document, they also copied these incorrect line breaks. This issue has been resolved.
The cursor always jumped to the first position of term edit fields
When editing terminology on the term edit page, the cursor always jumped back to the first position of a field. This interrupted the workflow because users had to confirm where the cursor was. This issue mostly occurred in Internet Explorer. This issue has been resolved.
The file term_help_template.vm was encoded in ANSI
This caused issues with languages that used non-ANSI characters, for example, French. This issue has been resolved.
The scroll bars on the view configuration page in the Dashboard were missing
Administrators can view the configuration of their Acrolinx installation in the Dashboard (Maintenance > View Configuration). However, if a line was too long, the scrollbars were also missing. Administrators could therefore not see the entire content of the file. This issue has been resolved.
The UNIX installer failed if administrators ran it twice
When administrators tried to run the install.sh script twice in a row, the installation failed. This issue has been resolved.
The term filter showed incorrect results
It was possible that the terminology manager displayed the wrong terms or no terms when users filtered for terms. This issue has been resolved.
HTML markup in terminology databases was inconsistently encoded
This issue has been resolved.
Safari can become unstable when you view tables with many rows
We observed that Safari can crash or automatically log you out when you open the "View Scorecard" page in the "Analytics" section of the Dashboard. This occurs when you change the number of rows per page to 200 or more. If this happens to you, try opening the Dashboard in another browser.
Changes to the term edit layout configuration
We've changed the way we store changes to the term edit layout. Previously, we stored the changes in a file called "term_editor_configuration.json". You had to back up this file separately when you moved your installation. Now, we store the changes to your term edit layout directly in the terminology database. If you've customized your term edit layout, the changes are included in any terminology database backups.
If you've customized your term edit layout, make sure that your customized term edit layout configuration file exists in the default directory: %ACROLINX_CONFIGURATION_ROOT%\data\common\term_editor_configuration.json.
- If you're upgrading on the same computer, this file should already be there.
- If you're changing computers for the upgrade, make sure you move this file to the equivalent location.
Once you start the 4.5 server, your customized term edit layout is automatically migrated into the terminology database. After you've successfully started the server, we recommend that you open the Dashboard and create a backup of your terminology database . That way, you have a fresh backup of your terminology database that includes your term edit layout.
The new privilege for accessing Scorecards
Users now require the privilege "View Scorecards and reports" to view Scorecards in the "Analytics" section of the Dashboard. If you enable the new feature for Scorecard and report security, users will also need the privilege to open any older Scorecards regardless of how they open them.
Anyone who has the role "Author" or any other role that includes the privilege "Check documents" gets this privilege automatically after you upgrade. However, suppose that you have some users who don't have the privilege to check documents but still need to see older Scorecards. For example, the roles "Project manager" and "Terminologist" don't have the privilege "Check documents" by default. If you have users that only have these roles and you want them to be able to review older Scorecards, make sure you add this privilege to their roles.