Brand New Features

• The Repository now has role-based security (this is a major feature and impacts many forms in the Web Client, and the look is different depending on privileges set)
  Possibility to allow users to have read-only rights, Create / Modify allows users to create new entities and globally having modified rights. The structure of this is to allow further support to give specific roles access to modify their Integrations.
  
  
  
• Two new Custom Meta Data types!
  - Markdown (with integrated Mermaid diagram support)
  - Mermaid diagrams
  
  
  
  
  
• Message Types (Log Event data), Allow users to set a different number of days to keep bodies than context.
  
  Changed the name for the property DaysToKeepMessages and split up to DaysToKeepBodies and DaysToKeepContext, DaysToKeepContext will get the same values as bodies on update.
  - New system parameter: DaysToKeepMessageContextDefault
  
  
• Add support to set SQL Server - Recovery Mode for the Log Database to be deployed. Some times you prefer to use the full recovery mode rather than the simple recovery mode that is the default.
  - New system parameter: LogDatabaseRecovery
  
  This is right now applied during deploy with two different dacpac files, Depending on your choices.
  Nodinite.LogDatabase.dacpac - Default Simple Recovery
  Nodinite.LogDatabase.Full.dacpac - Full Recovery

Enhancements

• Improved filter support in Repository
  Only showing Systems that is actually set on any Services
  /api/services/systems
  
  Also added for End Point Types set on any End Points
  /api/endpoints/endpointtypes
  
  (Only if using Contracts) Also added for Systems and Services set on any Contracts
  /api/contracts/services
  /api/contracts/systems
  
  
• Refactor and Optimize the JavaScript code used in Web Client, less code higher speed. Also using JSLint, as a Code Quality Tool a try to avoid different behaviours in different browsers by following the standard strictly.
  
  
• Timeline for Nodinite under About
  
  
  
• Improved exception handling in on errors in WebAPI
  
  

Changes

• Move some calls in the WebAPI to have the same structure, api/{type}/{id of the type}/{sub type}
  for example
  /api/monitorevents/resource/{resourceid} -> /api/resources/{id}/monitorevents
  

Known Limitations and Workarounds

• Swagger and Mermaid IS NOT possible to use or render in Internet Explorer. Internet Explorer support will be removed in the next major version of Nodinite

Fixed Issues (Bugs)

• #4343 - Deadlock in LogAPI during many queries, Move the get or create Log Agent, End Point and Message Type out from the transaction scope and improved caching.
• #4363 -  Windows AD Groups display / selector was not shown under a given role, Could be connected to a Role from Windows AD Group.

Upgrade Requirements

• Nodinite Update 5.3 or later must be used.

System Requirements

• WebAPI, Web Client is now requiring .NET Framwork v4.5.2 before v4.5

Fixed Issues (Bugs)

• The wrong version of Core and DAL was used during the build of 5.2.0.45.
  The new build is with and the correct ones.
  Extra script to verify version is added to the build to eliminate it from happening again.

Version revoked

• Wrong version of Core and DAL was used during the build of this version, fixed in 5.2.0.47

-----

Enhancements

• #4340 - Improved performance with a new index for Log Databases when processing events without body or context (they will get processing state counted),
  The dacpac version NOT stepped at this point since that would require an update of all Nodinite Log Databases. The index will be applied to all new databases created from this version.

Enhancements

• #4274 - Search Field Link - Support to find and view a body using the Message Id without the need to provide log database id. Documentation

Enhancements

• Update the delete threading for logging service and split to separate for active and archive databases, This will improve the performance for processing events.

Fixed Issues (Bugs)

• Name of Resources and other entities were limited to 48 characters in some modals. Therefore it was hard to distinguish an entity. Now, this is changed to allow word-break and multiple lines.

Fixed Issues (Bugs)

• #4150 - Fix bug in stored procedure for insert of Monitor Events if the setting Whether the database is located on a remote server is enabled the SP failed

Fixed Issues (Bugs)

• #4147 - Cleanup could take long time if many Log Points (Endpoint + Message Type) existed in config database.

Enhancements

• Improved example in LogAPI for api/logevent with actual data and example body,
  
  
  

Fixed Issues (Bugs)

• #4107 - LogAPI failed to create new Message Type for events without Body/Context, (Object reference not set to an instance of an object.)
• #4103 - Fix link to Log Agent in edit modal of Log Views.

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