NOTE: If you are using any of the versions between 5.2.0.8 and 5.2.0.14, then you should update to this version or later if one exists. This ensures that data is logged correctly by the pickup service. The problem could happen during transfer of Log Events to Nodinite, Pickup service retries the operation if the Log API fails.

Brand New Features

• New Endpoint Types IBM Cloud Functions (47) and Microsoft Azure Functions (75) See documentation

Enhancements

• Improvements of descriptive texts on several places for a better user experience
• The Log API now correctly sets the number of bodies for the Log Event if more than one is being sent (multi-part support, think about an email with attachments).

Changes

• A POST of Log Events to the Nodinite Log API should now be performed using /api/logevent, For backwards compatibility, the /api/logevent/logevent will continue to work for some time.
  
  

Fixed Issues (Bugs)

• #4100 - Solved a problem with a deadlock situation that happened if two events arrived to the Log API at the same time, This is a problem that can happen in versions between 5.2.0.8 and 5.2.0.14.
• #4066 - Summernote used for Knowledgebase Articles was buggy in fullscreen and did contain the wrong button colours (bad update in version 5.2.0.14 of Nodinite)

Brand New Features

• Events from BizTalk and other Log Agents which is not using the LogAPI is now counted. The processing state will be set to counted.
  - Message Type will be resolved from BizTalk / Nodinite, If the Message Type is unable to be located in BizTalk the Unparsed Interchange/Serialized Interchange will be used.
  - Event direction will be set for one way ports in BizTalk
  
  To set default Message Type in Nodinite for BizTalk ports
  
  

Enhancements

• #3954 - The backup time is now shown in the confirm modal on restore.
  
  
• #4030 - View History is added to the action menu for resources.
  
  
• #4077 - The Monitoring Agent can be synced from the remote configuration modal.
  
  
• New index in Log database to improve log audit search, will be used for new databases, ( can manually be updated for existing databases )
  
  

Fixed Issues (Bugs)

• #4049 - Recurrence did not use the specific settings, when triggered from the alarm in the Monitor View
• #4066 - Duplicates of images as a result of paste operations (CTRL + V) to Articles
• #3955 - Remove export of the default End Point Unknown, also disable change of the values that make den End Point unique (Name, URI, Direction, End Point Type and Log Agent)
• Preview of a stylesheet with output as XML, was not working. The XML was identified as HTML before.
• Export of event did not set the Event Direction
• The LogAPI, Service API did report wrong installation path in Nodinite overview
• Update email plugins with a fix that auto adds the ending slash for Web Client URL, make the links path correct

Brand New Features

• #4042 - Stylesheets can now set the content-type header to see the correct output see more in the documentation
  Nodinite use the attributes media-type or method on the element xsl:output to get the correct MIME type
  1. If set use the value set on media-type
  2. Else use the method html -> text/html, xml -> text/xml or text -> text/plain
  
  
  
  

Enhancements

• Update text for cleanup of Message Types

Fixed Issues (Bugs)

• Fix control center action slow to render the correct text in modal confirm (for operations like delete yes/no)

Same as 5.2.0.8 but with the plugins in the folder for Logging Service

IF you are using a previous 5.2.0.x version, then you SHOULD update to this or a later version of Nodinite due to the bugs resolved with this version

Brand New Features

• Updated Search Field Plugin Formula with support for XPath 2.0  (for all expressions as, look behind, ...)
  NOTE 1: If you are using expressions today where single quote character is used, you must rewrite them to escape using another single quote. That is FROM: ' to '' example xpath('//*[local-name()='a']') to xpath('//*[local-name()=''a'']')
  NOTE 2: Use XPath2 only for "small" messages since these will be loaded into RAM and by doing so, you can crasch Nodinite, delay processing and stress your system beyond what it was designed for.  Do not apply XPath2 expression on messages larger than a few MB. For large messages, make sure to use XPath.
  

• New parameter for the stored procedure copying data from BizTalk to Nodinite. This parameter is default 60 seconds and delays the data due to the fact that BizTalk during high load may write the events out of sequence. This new feature makes logging more robust and reliable but delays the time until data is visible in Nodinite.
  NOTE: You can tune this parameter as you feel fit and a future version of Nodinite will have a System Parameter to fa
  
  
• New Processing state Counted
  
  

Enhancements

• Statistics now counts all events even if they have no body/context. 
  
  

Changes

• Manage Message Type has new layout with correct handling of the special case when user opt to keep the data forever
  
  

Fixed Issues (Bugs)

• DaysToKeepMessages and DaysToKeepData is nullable in 5.2 to represent that messages should never be removed. Customers who set MessageType to 0 for these the ones that should be stored forever (NULL) and data was therefor removed instantly instead of being stored. Web Client GUI error, correct in the backend and conversion scripts.
• Link in managing Log Views  for Search Fields had invalid URL
• #4006 Description for custom values was missing in various places
• #4001 Fix buttons in modal footer when using Internet Explorer (which by the way is a browser you should not be using anymore...)

Upgrade Requirements

• As always, make sure to use the latest version of the install and update tool

IF you are using a previous 5.2.0.x version, then you SHOULD update to this or a later version of Nodinite due to the bugs resolved with this version

Brand New Features

• Updated Search Field Plugin Formula with support for XPath 2.0  (for all expressions as, look behind, ...)
  NOTE 1: If you are using expressions today where single quote character is used, you must rewrite them to escape using another single quote. That is FROM: ' to '' example xpath('//*[local-name()='a']') to xpath('//*[local-name()=''a'']')
  NOTE 2: Use XPath2 only for "small" messages since these will be loaded into RAM and by doing so, you can crasch Nodinite, delay processing and stress your system beyond what it was designed for.  Do not apply XPath2 expression on messages larger than a few MB. For large messages, make sure to use XPath.
  

• New parameter for the stored procedure copying data from BizTalk to Nodinite. This parameter is default 60 seconds and delays the data due to the fact that BizTalk during high load may write the events out of sequence. This new feature makes logging more robust and reliable but delays the time until data is visible in Nodinite.
  NOTE: You can tune this parameter as you feel fit and a future version of Nodinite will have a System Parameter to fa
  
  
• New Processing state Counted
  
  

Enhancements

• Statistics now counts all events even if they have no body/context. 
  
  

Changes

• Manage Message Type has new layout with correct handling of the special case when user opt to keep the data forever
  
  

Fixed Issues (Bugs)

• DaysToKeepMessages and DaysToKeepData is nullable in 5.2 to represent that messages should never be removed. Customers who set MessageType to 0 for these the ones that should be stored forever (NULL) and data was therefor removed instantly instead of being stored. Web Client GUI error, correct in the backend and conversion scripts.
• Link in managing Log Views  for Search Fields had invalid URL
• #4006 Description for custom values was missing in various places
• #4001 Fix buttons in modal footer when using Internet Explorer (which by the way is a browser you should not be using anymore...)

Upgrade Requirements

• As always, make sure to use the latest version of the install and update tool

Enhancements

• Resend of messages
  #3856 - Add support to allow resend of events to the receive port and use the strength of the Nodinite's BizTalk Null Adapter, To do this we use the context values to resolve the inbound location.
  First hand control message/payload context values and secondary for BizTalk Log Agents use context values
  - http://schemas.microsoft.com/BizTalk/2003/file-properties#FileName
  - http://schemas.microsoft.com/BizTalk/2003/file-properties#ReceivedFileName
  
  

Fixed Issues (Bugs)

• #3959 -  Some warning/error icons was shown in black instead of the correct colors for warning and error
• #3998 - Missing DotLiquid.dll in the package of latest releases this caused the Alarm plugin for Event Log to fail since it uses Liquid stylesheets, This was only a problem for new installations.
• #3999 - Using the print button of a log search failed if the result was grouped by
• #4000 - Fix an error listing the roles permissions did not show any permissions. In the Web Client a javascript error.
• Minor fix of icons in Import / Export to use the same style as in repository, Light / Bold, and the color green for items, folders is still black.

Fixed Issues (Bugs)

• #3979 - LogAPI WCF Services stopped to work since the web.config file points out the wrong version of IM.Libraries.Contracts, If the LogAPI shows up as offline, then to allow updates from 5.2.0.4 to a later version, open web.config and update the text IM.Libraries.Contracts, Version=5.0.0.2 to IM.Libraries.Contracts, Version=5.0.0.3 
• #3727 - If a communication error occurred between Web Client and Web API, the error page could not be shown due to a null error.
• #3980 - The Name property of all repository items in the Repository Model tab was hidden for logged events. 
  

This version for Nodinite brings new features, usability improvements and much more.

Brand New Features

• User Notifications (#3649)
• ConCat method for Formula Search Field Expression
• Search field links can now be sorted for the end-user (either automatic or specific by design) (#3591)
• Backup and restore functionality now part of the GUI. Backups have for a long time been performed in the background. These will now be readily available for end-users (#3817)
• Validate LogEvent method in LogAPI

Features

• Import/Export re-activated with improved GUI and now supports relations between Services

Enhancements

• Tons of minor fixes like typos, alignment, word wrap, reuse the same word for the same thing among different pages.  Strong emphasis on consistency, quality, look and feel (#3602, #3596, #3614, #3609, #3612, #3655, #3684, #3683, #3039, #3675, #3815)
  • Alarm plugins have been restyled
    
• Name of Log Database is now in title of database report (#3599)
• Re-styled Repository when viewing them in Monitor Views (#3604)
• The state of Resources is now displayed when managing the list of Resources to include in Monitor View (#3685)
• Nodinite version number is now displayed within error modals which facilitates our support work (#3073)
• Download errors (typically) now has a new landing page (#3173)
• Icon for Event Direction is now displayed in Log View Restrictions and Search Fields (#3767)
• Multiple messagetypes can now be assigned to a single search field expression (this functionality was also available in the search field wizard)
• Filter on historical events in Monitor Views
• List associated Monitor Views for selected Resource

Changes

• RegEx with Capturing groups now trims the end result (3768)
• Days to keep events can now be set to 0 (infinite) and still have a value for Days to Keep Body and Context. This was not allowed in the past (#3809)
• Adding a new MessageType manually was previously hardcoded with 14 days. Now the value comes from the two system parameters (DaysToKeepMessagesEventsDefault) and (DaysToKeepMessageDataDefault) (#3835)
• URL to Web Client for Alarm Plugins was previously default set without trailing slash "/". There must be a trailing slash and an administrator performing an installation should always change default values with localhost to the proper URL with HTTPS and machine/DNS name. All 4 default alarm plugins now return a trailing / even if the admin did not provide one (#3075)

Known Limitations and Workarounds

Fixed Issues (Bugs)

• Deleted search fields are no longer displayed in Log Views (#3097)
• Description for Display fields (columns) managing Monitor Views now has data (#3601)
• Notification area and information about a user failed for some AD group configurations (#3713)
• Number of Errors this week widget in Log Audits count was incorrect (#3712)
• Search field wizard could remove other expressions for existing search field (#3711) - Critical bug that was already published with previous minor releases
• Fix for Alarm plugins utilizing logic for "ngShow" (#3386)
• Days until split was incorrect for databases with an end date (#2541)
• Metrics also required Actions access right. (#3807)
• The name of the Monitoring Agent was also presented in the Applications column when managing resources for Monitor Views (#3853)
  
  

Upgrade Requirements

• As always, make sure to perform the update using the latest version of the Nodinite update tool.
  
  NOTE: Package manager has moved to the Instances menu!

Please feel free to contact our support team (support@nodinite.com) for additional guidance, if you fail to install or update this version.

If this release does not meet your standards or requirements; Please send bugs, feature requests, and input for improvements to our development team (featurerequests@nodinite.com).

Make sure to download the latest version from the Nodinite Customer Portal

Include all fixes from previous beta releases

Download from new portal: (requires registration)