Known Limitations and Workarounds

• Import and Export is not operational with the new Custom Metadata on Articles and Resources. The Import feature should not be used as it has too many problems.

Installation Requirements

Update Requirements

• Nodinite 6.x requires SQL Server 2012 or later. Support for older SQL Versions has been dropped.
• NET FW 4.8 or later.

Bug fixes

• #13264 - Fixed a problem with the RepositoryBinding, Note: Direction is no longer required on related Services
• #12983 - Fixed a problem with mathematical operators on vanilla installations
• #13202 - Fixed a problem editing search fields for a Log View using the IN
• #13145 - Fixed a problem to display Monitor Views for Resources managing a Monitoring Agent

Changes

• #13266 - Added some whitespace in the Audit Log, updating a Service
• #13202 - Improved the layout for search field values using the IN operator

Known Limitations and Workarounds

• Import and Export is not operational with the new Custom Metadata on Articles and Resources. The Import feature should not be used as it has too many problems.

Installation Requirements

Update Requirements

• Nodinite 6.x requires SQL Server 2012 or later. Support for older SQL Versions has been dropped.
• NET FW 4.8 or later.

Bug fixes

• #12973- Fixed a minor display problem for very long content in Custom Metadata fields ´

New features

• #12974 - During the processing of Log Events, the Logging Service sets the Application interchange ID if any of the following values are ending any Context Property:
  • x-ms-client-tracking-id
  • ´ExtendedProperties/1.0#SystemInterchangeId´ (if it also exists, it takes precedence over x-ms-client-tracking-id) This feature is helpful making it even easier to have end-to-end tracking in Azure Services and for example BizTalk Server

Known Limitations and Workarounds

• Import and Export is not operational with the new Custom Metadata on Articles and Resources. The Import feature should not be used as it has too many problems.

Installation Requirements

Update Requirements

• Nodinite 6.x requires SQL Server 2012 or later. Support for older SQL Versions has been dropped.
• NET FW 4.8 or later.

Bug fixes

• #12722- Fixed a problem in the Repair and Resend page if the Webhook has no matching entry in the System Parameter: ResendWebhookSettings
• #12789 - Fixed a problem with the link for a Custom Metadata entry

Known Limitations and Workarounds

• Import and Export is not operational with the new Custom Metadata on Articles and Resources. The Import feature should not be used as it has too many problems.

Installation Requirements

Update Requirements

• Nodinite 6.x requires SQL Server 2012 or later. Support for older SQL Versions has been dropped.
• NET FW 4.8 or later.

Bug fixes

• #12693- Fixed a problem sending a repaired message. This bug was introduced already with 6.1.0.66

Known Limitations and Workarounds

• Import and Export is not operational with the new Custom Metadata on Articles and Resources. The Import feature should not be used as it has too many problems.

Installation Requirements

Update Requirements

• Nodinite 6.x requires SQL Server 2012 or later. Support for older SQL Versions has been dropped.
• NET FW 4.8 or later.

Changes

• #12630 - Changed the Web API to deal with exceptions in the configuration using the Nodinite Logic Apps Logging and Monitoring Agent version 6.1.11 and later.

Bug fixes

• #12681 - Fixed a problem displaying Context Values in Log Views and Details page, Repair and Resubmit page. This problem was introduced with 6.1.0.82; hence, we chose to remove that version.
• #12429 - Fixed a problem for Administrators using renamed fields in Log Views
• #12535 - Improved the date-time display in Log Views to better cope with clients in different time zones.
• #12513 - Fixed a problem Viewing relations for Custom Metadata.

Changes

• Bump 3rd party libraries to latest to please OWASP, NuGet Scan and Gitbhub Advanced Security.

Known Limitations and Workarounds

• Import and Export is not operational with the new Custom Metadata on Articles and Resources. The Import feature should not be used as it has too many problems.
• #12513 - There is a problem Viewing relations for Custom Metadata. You can still edit, and use the metadata field as usual.

Installation Requirements

Update Requirements

• Nodinite 6.x requires SQL Server 2012 or later. Support for older SQL Versions has been dropped.
• NET FW 4.8 or later.

Bug fixes

• #12259 - Fixed a problem copying Log Events from the BizTalk DTA database with nStatus = 3 and 5
• #12298 - Fixed a problem to create and manage an Article for a non-admin user
• #12300 - Fixed a problem for non-admins to access Log Views when the user has no grant to access the Repository Model

Changes

This package version is larger than before due to changes for an even better product in the future.

Known Limitations and Workarounds

• Import and Export is not operational with the new Custom Metadata on Articles and Resources. The Import feature should not be used at all as it has too many problems.

Installation Requirements

Update Requirements

• Nodinite 6.x requires SQL Server 2012 or later. Support for older SQL Versions has been dropped.
• NET FW 4.8 or later.

Bug fixes

• #12041 - Fixed a problem updating a Resource without Category or Application

Known Limitations and Workarounds

• Import and Export is not operational with the new Custom Metadata on Articles and Resources. The Import feature should not be used at all as it has too many problems.

Installation Requirements

Update Requirements

• Nodinite 6.x requires SQL Server 2012 or later. Support for older SQL Versions has been dropped.
• NET FW 4.8 or later.

Changes

• #11991 - Changed the Logic sending a recurrent alert to avoid sending an alert with zero changed Resources
• #11931 - In Maintenance Mode, Nodinite no longer execute Remote Actions if an Auto-Healing is applied

New Features

• #12019 - Added Duplicate menu item to the Actions button in a Log View if you are an Administrator.
• #11941 - Anchor links in Markdown to the same page are now operational

Bug fixes

• #12017 - Fixed a problem updating a Log Agent
• #11940 - Markdown Articles were not properly rendered if opened from a Monitor View
• #11944 - Sort Resources on Auto-Healing column was broken

Known Limitations and Workarounds

• Import and Export is not operational with the new Custom Metadata on Articles and Resources. The Import feature should not be used at all as it has too many problems.

Installation Requirements

Update Requirements

• Nodinite 6.x requires SQL Server 2012 or later. Support for older SQL Versions has been dropped.
• NET FW 4.8 or later.

Changes

• #11796 - The Logging Service will use the server name of the Active Log Database when spawning a new Log Database.
• #11810 - The Monitoring Service is now more robust to some bad configuration data if an SQL DB admin changes to shortcut the Web API/Web Client. This fix also includes a robustness check in the Web API when creating/modifying a Monitoring Agent.
• 11831 - Changed the sort order on groups in a correlated Log View according to the two options available to control the output.

New Features

• #11818 - Added a new feature to check all available checkboxes in the Find Related modal.

Bug fixes

• #11814 - Fixed a problem searching for Processing User in a Log View.
• #11815 - Fixed a script console error in Find Related when including the Endpoint URI.
• #11816 - Fixed a Log View problem loading saved operator type in a post-group filter
• #11817 - Fixed a Log View problem using a date time-based search field
• #11795 - If there is an error from a Log Audit Search, the error page now fits the screen,
• #11830 - Fixed a problem resetting the date time in the Find Related modal

Installation Requirements

Update Requirements

• Nodinite 6.x requires SQL Server 2012 or later. Support for older SQL Versions has been dropped.
• NET FW 4.8 or later.

New features

• #11672 - Added support to preview .SVG files as attachments

Changes

• #11578 - Improved the performance of expanding a large grouped result in a Log View
• #11670 - When viewing an Article, the custom metadata accordion is not present on the screen if there is no data associated

Bug fixes

• #11746 - Fixed an issue using a Log View saved in 6.0 with an empty default search setup in 6.1.
• #11666 - Fixed a padding issue managing a Stylesheet
• #11702 - Fixed a problem displaying Contracts for a System
• #11671 - Fixed a padding issue viewing an Article
• #11673 - Removed logging of the base64 encoded content if there is a major flaw in the process of logging a Log Event in the Log API
• #11696 - The Logging Service now uses the same server name as configured by the current active Log Database when spawning a new