BREAKING CHANGES in version 2.3

•The GN4 2.3 clients and browser require the .Net Framework 4.6.1 on Windows 7, 8 , 8.1 or 10 and the Redistributables VS 2015. Moreover, install also redistributables VS 2010 as some spell checker libraries are not compiled with VS 2015.

•The GN4 2.3 servers require require the .Net Framework 4.6.1 on Windows 2008 R2 or newer and the Redistributables VS 2015. Moreover, to register XMPHandler, it needs also Redistributables VS 2013.

•To be able to recompile add-ins, the appropriate version of the Visual Studio is required. See Visual Studio Community or Express Edition.

In the Enhancement GN4-3195 - Fred4: moved image refresh parameters to typography, moved three config parameters from user preferences to the typography. The parameters are used in image refresh processing: -imgRefreshTolerance: 1..100 value, Image ResizeLimit (in %) when automatically updating -imgRefreshIsotropic: boolean, When updating automatically choose if isotropic or not -imgRefreshSize: Boolean, if true ResizeLimit refers to image size

These attribute are editable only by editing the typography. By default, they have the same default values of the old user preferences values. In case of user editing is necessary re-set the values into typography.

To apply this change: update the schema (//depot/GN4/Main/Config/Schemas/GN4Base.xsd and //depot/GN4/Main/Config/Schemas/GN4Editorial.xsd), update the configuration(//depot/GN4/Main/Config/Global/GN4/edAdmin4_Config.xml and //depot/GN4/Main/Config/Strings/EditorialStrings.en.xml)

Check also the custom vb files: the config properties of these attributes are no more available, replaced by typography properties.

Fred4: images, boxes and ellipses shadows are now always soft-shadowed. Removed feathered (slices) and rounded transparent shape old effects. Please visually verify any object that was stored with a old shadow enabled. Forum topic: http://forum.teradp.com/topic.asp?whichpage=-1&TOPIC_ID=437

In the version 2.3, the box presets have 4 parameters more, so if you are using the custom ones in the EditorialConfig, you will need to modify them before use. See Box presets.

GetFormat didn't work as it should: the method returned an empty object (that can be filled setting the id) and this could cause exceptions and crashes. The method is now changed in 'GetFormat(int formatId) that selects and initializes the format object.
An example of getting the current format:

if (Fred.GetActiveTxt isnot Nothing) then
 dim oformat=fred.getformat(Fred.GetActiveTxt.FormatId)
end if

Replaced the old code in all the system scripts. You may need to do the same in the custom scripts.

From the version 2.3.2711, all the ExaleadXXX templates have been renamed to FullTextXXX, except the ExaleadFullText (simply renamed to FullText). Please update your configurations replacing the old names with the new ones. Saved searches with invalid opCodes will fail to load. You have to fix the saved searches by running the workflow Global\GN4_Tark4_Common\wf_FixSavedSearchesNoExalead.xml. Run the workflow right after the upgrade to 2.3, in order to replace the ExaleadXXX operators in the saved searches with the new FullTextXXX ones.

The steps:

1.Import the workflow in the database:

srv4 config -in ..\Config\Global\GN4_Tark4_Common\wf_FixSavedSearchesNoExalead.xml

2.Run the workflow on the server using:

srv4 wf FixSavedSearchesNoExalead

The process can take any time from few seconds to a couple of minutes, depending on the number of saved searches.

The workflow creates a backup of the existing saved searches in C:\Temp\Data\UserConfig.xml, referencing the data files in C:\Temp\UserConfig.

If anything goes wrong with the workflow, reimport the c:\temp\data\userconfig.xml using the srv4 import command.

A random error occured under certain conditions in the client: there is no login to execute this request. This could happen after an IIS reset (or an IIS crash) done while the application was open if the first connection to IIS was done using an url different from the one used by the client. The problem was in the cookie name used to do calls without the ticket in the url, it contained the client url that now has been removed. Now the cookie name is simply: GN4_[ServerAppName]. This is a breaking change: in case an external application do calls to the web service without the ticket in the url - so using the ticket - it will be necessary to amend the cookie name.

Breaking change with moving REST interface URL from publishing destination to publishing template. If you need two different sites, you need to create two different templates.

In the version 2.3, when a script is disabled for Shell4_TabItems.xml, it gets automatically disabled for any application. Please note that the permission change appears only when looking at the Shell4_TabItems.xml and in FRED4_TabItems.xml or TED4_TabItems.xml it appears unrestricted - but effectively it is unavailable. To keep the same functionality in previous builds, please set "*" as app name in the URL access restrictions on the Permissions tab when editing users or groups.

The new library objects, created with the logical groups enabled, would not allow anymore to use F6, because the Page.SelElement.LG_LibObjName in 2.3 returns either the library object name or LG name, therefore, it would always return the LG name, and the F6 would not know which is the "next" objects. This is fixed in BrowseLib since build 2826, but it will not work in 2.3 builds previous to 2826.

ObjBox system script changed the number of parameters. Now it has 15 instead of 9 parameters. You will need to update your custom scripts that call ObjBox. See ObjBox Script for details.