The version 2.2 is the previous version of the GN4.

This chapter lists the new and improved features, added capabilities, performance improvements, and bug fixes in the version 2.2.

For the full list of all changes and bug fixes, go here: http://tech.teradp.com/tech/html/GNPortal/default.asp?link=relnotes2.3.html.

Breaking changes in version 2.2

•From the build 2.2.2392.0, the .NET Framework 4.5.2 is required on GN4 clients and servers, and the reference to the .NET Framework 4.5.2 is required in all your custom add-ins.

•Windows XP,  Windows Vista, Windows Server 2003, and IIS 5 are no longer supported due to Microsoft Framework 4.5.2 compatibility restrictions. This applies also on Tera daily servers and Tera demo sites featuring the version 2.2.

•To be able to compile the 2.2 add-ins, do the following:

oDownload and install the .NET Framework 4.5.2 multi-targetting pack (382Mb). Visual Studio Express 2013 will prompt you on the first access to download the .NET Framework 4.5.2 multi-targetting pack. The link is https://www.microsoft.com/en-us/download/details.aspx?id=42637

oIn all your custom add-ins change the version of the .NET Framework to 4.5.2. To do it, right click a project, click Properties, and on the Application tab, under Target framework, select the .NET Framework 4.5.2. Repeat the same for all custom projects.

oIn all VB files of your custom add-ins, make sure that the list of imports on the beginning of the file corresponds to the list of imports in the relative system add-in, e.g.

•In versions prior to 2.2, I4 allowed by default empty searches that could generate a huge result set. The searchContext configuration elements now has a Boolean property allowEmptySearches that if True will allow a search to be performed without the associated search form specifying any extra criteria. The default value is now False, where you must specify some value in the associated search form before results are retrieved from the database. If a search form is not specified, this value is ignored and is assumed to be True otherwise no results would be retrieved. Therefore, revise all your search settings, and add allowEmptySearches="true" where required.

•In previous versions of i4, the configurable dialog boxes behave differently than in 2.2. Now, the attributes without specified ui mode won't appear on the dialog. On the following example, the title attribute won't appear, as the mode is missing. So, the right approach is to add the <ui mode="Normal"> statement also to the title attribute.

<objectUI name="General" objectTypeName="img" xmlns="http://www.teradp.com/schemas/GN4/1/GNPortalConfiguration.xsd">

       <attribute name="title" />

       <attribute name="summary">

         <ui mode="Normal">

           <template kind="MultiLineString" xmlns="http://www.teradp.com/schemas/GN4/1/XmlSchemaExt.xsd">

             <objectUI>

               <web maxRows="6"/>

             </objectUI>

           </template>

         </ui>

       </attribute>

     </objectUI>

If you specify the <default mode="Normal" />, all the attributes of the object will be shown - and you probably do not want this. The following code will show all the attributes of the img object:

<objectUI name="General" objectTypeName="img" xmlns="http://www.teradp.com/schemas/GN4/1/GNPortalConfiguration.xsd">

<default mode="Normal" />

       <attribute name="title" />

       <attribute name="summary">

         <ui mode="Normal">

           <template kind="MultiLineString" xmlns="http://www.teradp.com/schemas/GN4/1/XmlSchemaExt.xsd">

             <objectUI>

               <web maxRows="6"/>

             </objectUI>

           </template>

         </ui>

       </attribute>

     </objectUI>

 

•If in the Ted / Fred preferences a default measure was set to Pica it is necessary to enter the dialog and apply the setting again.

•Import new config file config\Global\PermissionsSets.xml. It contains configurable permissions sets. Example:

<permissions name="Read Only" description="Grant reading permissions, and deny all the other ones.">

    <deny>all</deny>

    <grant>ReadNormal</grant>

    <grant>ReadProtected</grant>

    <grant>ReadSpecial</grant>

    <grant>ReadContent</grant>

    <grant>RefReadNormal</grant>

    <grant>RefReadProtected</grant>

    <grant>RefReadSpecial</grant>

    <grant>RefReadContent</grant>

</permissions>

•From GN4 2.2.2529 a new mandatory library, called WFUtils.dll, is required to run the GN4 code workflows. The WFUtils.dll contains utility methods used by GN4 workflows; in fact, the aim of the dll is avoiding to duplicate common functions. The new library is written in VB.NET (4.5.2) and it is mandatory to run the GN4 workflows only in GN4 2.2 (the old GN4 versions 2.0, 2.1, etc... has not changed). WFUtils.dll depends by the standard GN4 libraries (Server.dll, Common.dll, etc...). Note that WFUtils.dll is a 'standard' library (it contains only standard methods). This means that you cannot add your custom methods to that library, because it could be modified at any GN4 release. If you need to create custom methods to use into the code workflow, then you have to create your own library and reference it into the code workflow. For now, WFUtils contains the methods that were exposed in the 'Context.WFUtils' object (LogError, HttpPostXml, etc...); more methods could be added in future. Note that the 'Context.WFUtils' object is not available anymore in code workflows: it has been replaced by the 'Utils' object, which is automatically created and exposes the methods written into the WFUtils.dll. For example: Utils.LogInfo("using WFUtils") The standard publishing workflows (pubTemplateGNWeb.xml and pubTemplateVirtualCom.xml) has been modified to use the new 'Utils' object, instead of the old 'Context.WFUtils' object, and they must be re-imported into GN4 database. If you have customized workflows that use the old 'Context.WFUtils' object, then you have to modify them as well (only in GN4 2.2). The source code of the WFUtils.dll is released into the GN4AddinsExpress.sln .NET solution (in GN4SystemAddIns.zip); so, the new library can be compiled using VisualStudio Express. This allows easy upgrades or fixes to customer workflows without core changes.

•The workflow wf_CropImg.xml (which crops an editorial image) has been removed from the configuration files. This is because the standard wf_Crop.xml workflow is now able to manage both gn4:image (wire image) and gn4:img (editorial image). In the standard addins and configuration files, the calls to the old wf_CropImg.xml workflow have been replaced by calls to wf_Crop.xml. So, if you have custom methods which calls the old wf_CropImg.xml workflow, you can replace them with wf_Crop.xml. The standard addins that have been modified are: TedSystemAddIn and FredSystemAddIn. The configuration files that have been modified are: shell4_tabItems.xml, fred4_tabItems.xml and ted4_tabItems.xml.

•If the user selected the image conversion to grayscale but the required color profile ISOnewspaper26v4_gr.icc is not installed, the printing will fail (before this fix the print have succeeded without conversion). For download, see http://forum.teradp.com/topic.asp?whichpage=0.58&TOPIC_ID=381&#3998.

•To enable paragraph copy fitting in i4 article editor, edit the custom EditorialConfig and add the node:

  <!-- I4 article editor paragraph fit (txttype=copyfit,....) -->

  <TxtTypeToCopyFit>

    head=head,body=body,*=body

  </TxtTypeToCopyFit>

•Changed the behavior of the internal timer of the Server.dll that now runs every X minutes, where X is the AlivePeriod parameter in ServerConfig.xml. The ServerConfig.xml file has to be reimported after being merged with your current one. Removed the 'CheckLoginTimer' parameter in ServerConfig.xml.