In this version, we've added some security and functional enhancements and fixed a few bugs.
Previously, you could only access the Acrolinx Dashboard with Safari version 6.1.2, but now we've added support for Safari 8.
We've tested Acrolinx with Oracle 12c and can verify that it works for terminology and analytics. We've now added Oracle 12c to our list of supported database versions
In most Acrolinx plug-ins, you can configure parenthetical elements on the Segmentation tab of the plug-in options. However, if you use server-side extraction, which doesn't have a user interface, you couldn't configure parenthetical elements at all. We've added support for parenthetical elements, and you can now configure them in a server-side CSD (Context Segmentation Definition) file. With this change, the text extraction options on the server-side are more consistent with the standard plug-ins (which use client-side text extraction).
If you need the maximum level of security for your Acrolinx server, you can now disable older SSL protocols. Attackers have found weaknesses in many of these older protocols, so disabling them will make your server more secure. You can now use the core server property sslDisabledProtocols to disable individual SSL protocols that are either no longer secure or might be insecure in certain configurations.
When you checked content in Adobe Experience Manager (AEM), content that was supposed to be excluded from the check didn't get excluded and Acrolinx found issues that weren't really genuine issues. For example, the text that you find in <script> tags is usually code and you wouldn't want to check it for style or grammar. However, due to an issue in the previous server, this text was checked regardless and Acrolinx incorrectly reported issues in content that was never meant to be checked. We've fixed this problem and Acrolinx should now ignore code and find issues in text only.
In the Acrolinx Dashboard, you can create system notifications that everyone sees when they connect to Acrolinx. Some server administrators like to reuse the same notifications, but these notifications disappeared after they installed Acrolinx updates. We've now resolved this issue in the latest server version. If you create server notifications in the newest server version, they'll be retained the next time you update Acrolinx.
If you work with terms that are "admitted" you might want to penalize writers for using them instead of the "preferred" terms. By default, the quality score was supposed to go down if Acrolinx found admitted terms in your content. This didn't work in reality and many people didn't want to penalize writers for using admitted terms anyway. The scoring for admitted terms is configured with the language configuration property terminology.scoreAdmittedTerms . We've changed the default value to "false" so that writers don't get penalized. However, if you do want to penalize writers for using admitted terms, we've also fixed the scoring issues so that the quality score gets worse if writers use admitted terms. You just have to set the terminology.scoreAdmittedTerms property to true .
Information on Upgrading
There's nothing special that you need to know for upgrading to this server version. You can upgrade the server according to the standard upgrade procedure.