Changelog 6.5 PATCH 3

From Sense/Net Wiki
Jump to: navigation, search
  • 100%
  • 6.5.2
  • Enterprise
  • Community
  • Planned

This page contains information about the following patch published for Sense/Net ECM Enterprise Edition:

  • version before the patch:
  • version after the patch:

Release date: 26th February, 2016

Please note that patches, upgrades and other packages are published only for the Enterprise Edition.

Community customers may perform the upgrade manually after the next community release.

Installing the patch

To install this patch, please follow the following steps.

SnAdmin folder and configuration

Make sure that you have a complete SnAdmin folder in your web folder and the configuration (connection string, paths of other web folders in NLB system) is correct (especially for the SnAdminRuntime.exe tool in the Tools folder). Please read that article carefully about executing a package - for example when to stop and start the web site, how to configure the tool.

Execute the package

This patch contains the following package. You should copy it to the SnAdmin folder and execute it (the SnAdmin tool is inside the Admin\bin folder):

SnAdmin snent-patch-

It is highly advisable to make a complete backup before executing a patch to make sure that no information gets lost.

Copy task executors

You will have to update task executor tools manually on agent machines. Sense/Net ECM deploys the new versions of these tools into the web\TaskManagement\TaskExecutors folder. Please copy over all files/libraries, except the configuration files.

Check the results

You can review the log files created for the execution or - after restarting the website - you may open the Version Info page accessible from the Root Console in Content Explorer.

Patch contents

In this section we list all the important new features, bug fixes and breaking changes that were made in the product since the release of the previous patch. To check previous change logs, please visit the following article:


  • User login name is stored in a separate field (LoginName) to let users have special characters in their login names that are not allowed in a content name.
  • Speedup: content indexing and security activities are executed in parallell if possible. This is a huge step forward as unrelated activities (e.g. indexing in different workspaces) will not block each other.
  • Enterprise customers will get a new Aspose licence file for the current year.
  • Settings content are searchable from now on.

For developers

  • The Content naming API has been opened up: the new ContentNamingProvider lets developers customize the 'displayname to name' converter algorithm. This is what determines how file (and basically all content) names are generated (e.g. handling special and forbidden characters). We provide two built-in implementations for the provider as a reference.
  • We upgraded the CodeMirror text highlighter plugin to version 5.11. The previous version (3.14) will be removed in the next patch, please upgrade your custom client-side code by then to use the new version.
  • We upgraded SignalR libraries to version 2.2.
  • Cross-origin requests work in case of ajax file download operations - not just for OData requests.
  • New OData actions: Login and Logout to let developers authenticate users through REST API calls.
  • SnAdmin
    • New step: CheckIndexIntegrity tool. Displays index-database inconsistencies.

Breaking changes

The introduction of the above mentioned new LoginName field (for users) may involve changes in your custom code if you are working with users or have a custom user interface for creating or editing users. The patch takes care of copying all existing user content name to the login name field, but you have to make sure that from now on your custom user interface and custom code also sets the new LoginName field if you want to change the name that users actually use for logging in. This is because when the user logs in, the system will look into the login name field from now on, and the content name is used only in the url (and content Path) as in case of any other content.

Resolved bugs

  • The time zone is preserved correctly when the user changes the date in a date field.
  • Event registration form item is able to check participant count correctly.
  • A compulsory Binary Field cannot be saved if the stream is empty or 0 length.
  • Reject reason text is cleared from a content when it gets approved.
  • Content search portlet has been fixed so that it can be used with any type of virtual search content.
  • Parametric search portlet is able to handle a parameter value that contains spaces (therefore multiple search words) correctly.
  • Reference field is able to recognize a comma separated id list as an import data.
  • When a user logs out, for security reasons we completely drop the session (with the Abandon method) instead of just clearing the session.
  • Header tools compares content modification date correctly (as a UTC value) to return the correct cache header.
  • Robustness
    • Deadlock elimination: based on concurrency tests several possible SQL deadlock scenarios were eliminated.
    • Changes around schema handling to make the system work correctly during concurrent schema modifications.
  • Workflow: if Lucene search engine is switched off (e.g. in case of an old-school command line tool), the workflow engine does not throw an exception.

Feature previews

We are workig on the next major version of Sense/Net ECM: SN7. We document the process on our blog. These are just a few examples of the changes that we are making under the hood to prepare for that:

  • a couple of controls and portlets are able to pick their UI templates from under the skin (instead of using a hardcoded global path)
    • ActionList controls
    • Action presenter portlet
  • All current odata actions and functions are added to ODataManager along with a few new helper methods
  • we are working on converting all our field controls to have a modern, Javascript-based UI in the new skins

3rd party plugins

For the list of 3rd party plugins used in this release, please visit the following article:

Differences between Community and Enterprise editions

For the list of the differences between the Community and the Enterprise editions in this release, please visit the following article:

Related links