Changelog 6.5 PATCH 1

From Sense/Net Wiki
Jump to: navigation, search
  • 100%
  • 6.5.0
  • 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: 4 November, 2015

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.

This package contains a long-running SQL script. Please make sure that SQL and other timeout values are set to a high value in SnAdminRuntime.exe.config.

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 on agent machines manually. Sense/Net ECM deploys the new versions of these tools into the web\TaskManagement\TaskExecutors folder.

Check the results

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

Patch contents

In this article 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:


Binary handling

We made a significant change in the way we handle binaries in the database. Previously every file version (e.g. 1.0 Approved, 1.1 Draft, etc.) had their own binary. That meant duplicate rows in the db even if only the metadata have changed. From now on when it is not necessary to copy the actual binary content in the database (for example the user simply wants to check out the file), we won't make duplicates. We can do this because from now on we store binary content in a separate, standalone table called Files. This saves some storage space and makes some operations faster, but the most important reason for this feature is that it is the foundation of future speedup and architectural changes: for example we will be able to make text extraction only once instead of loading and parsing the same files over and over again. And we will be able to implement that file system storage feature that our clients are waiting for.

For developers

  • Security component integration
    • The Permission API became simpler and more intuitive.
    • Membership handling (adding/removing users and groups to/from a group) is faster and more robust.
  • OData
    • Finally it is possible to create content from a template via an OData request.
    • A new action has been added for making sure that all preview images are available: CheckPreviews.
    • Working with allowed child types got a lot easier: the new EffectiveAllowedChildTypes field gives you the aggregated, effective list of types that can be used to create new content there. Two new actions (AddAllowedChildTypes, RemoveAllowedChildTypes) were added to let you manage these values from the client side.
  • A new SnAdmin conditional step was added for querying the database for a scalar value and making a decision based on it: IfDatabaseValue.
  • A new workflow activity added for monitoring content changes in a folder or library: WaitForContainerChanged.
  • We started to refactor our code base to remove compile warnings from the solution. These changes will not likely to introduce any breaking changes, in most cases this is about not calling obsolete methods internally, or making the code more clean and robust.

For portal builders

  • The workspace wall is able to display pasted links as clickable links or embeded images or videos.
  • Reference Field values (e.g. related documents) are displayed as a link in the grid in content list views.
  • Notification: sender address can be set in the NotificationConfig content. If not set, the default value from the web.config file is used.
  • moment.js is upgraded from version 2.7 to 2.10.6 ([| changelog])

Breaking changes

  • We made our Permission API simpler and easier to use. From now on we have a single entry point: the SecurityHandler class that contains both an instance and a static API for accessing and modifying content permissions. The SecurityManager class has been removed, please redirect all your method calls to that class to the SecurityHandler class.

A detailed article about the security component and how to use the permission API is on the way.

Resolved bugs

  • Document viewer
    • Document viewer reloads correctly after uploading a new document if it contains fewer than 5 pages.
  • Workflow
    • When a workflow must be aborted (e.g. because of a related content change), the state becomes Aborted correctly, instead of Completed. This lets us preserve aborted workflow instances instead of deleting them.
    • WfContent class tries to save the content again if setting a property causes NodeIsOutOfDateException. This makes workflow execution more robust.
  • Back url provided for actions is not encoded on the server to prevent double or incorrect encoding (e.g. spaces).
  • Binary export: Binary Field skips stream writing to the file system if the CurrentDirectory of the export context is null or empty.
  • The built-in calendar list view handles UTC times correctly.
  • A schema relative url (that works with both the http and https protocols) can be used in a css import statement with bundling switched on.
  • A YesNo Field can be used in a CTD, not only on content lists.
  • Lucene manager lock file notification mechanism is able to handle several recipient e-mail addresses separated by ',' or ';'.
  • OData $filter query requests that contain the enableautofilters or enablelifespanfilter parameters will honor these values.

Known issues

  • For the Task Management component to work, you need to open the task management website url to the internet, because the task monitor UI connects to the task management web application directly through SignalR.

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 Community and Enterprise editions in this release, please visit the following article:

Related links