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

Brand New Features

• #2277—Support for nested search filter groups. This feature is a game changer for using the Log Views in Nodinite. A simple example is that a previous statement, 'A and B or C', can now be set as 'A and (B or C)'.
• #3027, #10018 - New option to display groups in Log Views with the specified sort order and first or last event in the group header
• #1740, #1831, #9922 - New statistics for Monitor Views. Duration in the current state (for how long has the Monitor View been in its current state) New timeline graph for Monitor Views and Resources Rewritten the Logic for Monitor Views to push alerts if you add a resource in the non-OK state to a view with only resources in the OK state
• #2281, #9952 / #9953 - Custom Metadata filter on Integrations: The User can now search for entries with a given input, not equals and exists are excellent features to help you better understand and manage the content of the current configuration
• #9855 —The system Administrator has direct access to all Services and associated Integrations on the Resource page. This feature helps you understand where a resource is in use.
• #9870 - Using a Log View; the User can paste a ´CRLF´ character into a search field using the ´IN´ and the ´NOT IN´ operator.
• #8898 - Manage Tags
• #9640 - Introduced a new feature to allow the hard deletion of Tags
• #3037 - Custom Meta Data is now featured in Resources. The information is present in Alerts. Use this feature to build advanced scenarios using the Webhook Plugin
• #6863 - New ´isnull´ expression to the Formula plugin
• #9495 - Added field as new Content to Formula plugin
• #2579, #9747 - A new feature was added to allow Resources with Auto Healing to postpone alerts during retries. Alert is sent once all attempts are exhausted.
• #7464 - Added Markdown support to Articles
• #9741 / #10290 - Custom Meta Data Filter for Resources Overview
• #10291 - Custom Meta Data Filter for Resources editing a Monitor View
• #10302 - Custom Meta Data Filter for Resources in a Monitor View
• #9737 - Custom Meta Data Filter for Services
• #9738 - Custom Meta Data Filter for Contracts
• #9739 - Custom Meta Data Filter for Message Types
• #9740 - Custom Meta Data Filter for Endpoints
• #10340 - Filter on Auto Healing configuration editing a Monitor View
• #10191- When managing Custom Metadata, the Repository Admin now see all associations directly, and there are multiple filter features available to narrow down the list
• #10384 - An Article can now have Custom Metadata Attributes
• #10385 - Managing a Resource: The end-user can now manage the associated Articles. Cute filters help narrow down large sets.
• #10532 - Custom Meta Data Values for Checkbox and Select (dropdown) can now be permanently deleted, and also, with this feature, a problem with possible duplicates was removed.
• #10943 - Webhook to repair and resend Log Events now support OAuth and basic authentication
• #11321 - The with selected button in Log View search result now sports a permanently delete selected Log Events feature
• #11433 - The System Parameter StylesheetScriptsEnabled now affects Liquid Stylesheets in addition to XSLT.
• #11445 - Resources and all its associations in the Deleted state will now be removed after 90 days.
• #11591 - Mermaid support for ZenUML (now using Mermaid 10.9.0)
• #4703 - Support for SQL Managed instance

Enhancements

• #11391 - Search field wizard body panel is now resizable to fit more content on the screen
• #9879 - The badge with Event Direction now fits on-screen even if these have large content
• #10275 - As Admin, in all repository overviews, there is now a quick edit icon; this feature saves a few clicks and a few seconds to edit the entry
• #10276 - When managing Custom Metadata (Select, Checkbox), the Edit modal has been refurbished
• #10327—The Monitor Agent overview now has a new clickable icon and an Action entry to open the Remote Configuration; this feature saves a few clicks and a few seconds to edit the entry.
• #10330—When editing a Monitor View with Deleted Resources, an informative banner with links to the missing entries is now present. This feature helps you understand a change in the configuration.
• #10361 - Integration doc now has accordions to minimize/expand content
• #10449 - The Resources Overview has a new layout, including additional data
• #10756 - Added time to read and last updated viewing Articles
• #10924 - Added the display of Custom Meta Data in Articles from Resources in a Monitor View
• #11053 - Updated Mermaid to 10.7.0 to support new diagram types
• #11039 - Added sort on artifact renamed search field in the list of Search Fields for a Log View
• #10581 - The Monitoring Service no longer synchronizes with each agent on startup; agents will synchronize as scheduled
• #7456 - Alarm plugins now shows the association with Monitor Views.
• #11028 - Integrations and Custom Metadata now shows Created/Updated and is also sortable on these two new properties
• #11418 - The With selected button for Message Types now sports a Delete / Restore feature.
• #11481 - Most related information is now displayed in the Repository Entities View pages.

Major Change

• #10407 - We changed the logic copying Events from DTA → Nodinite Log databases for BizTalk Server. Earlier, if a port had any tracking enabled, all events would be copied. Now, we try to narrow on before or after port. For one-way ports this matches perfectly, for two-way ports, all before or after events are copied regardless of which before or after checkbox is checked.

Breaking Changes

• #10266, 10417 - Changed the presentation of the date-time result in CSV download (time is now in UTC).

Changes

• #11128 - Changed the display order for Transport Contracts in Services
• #11149—We changed the fill factor for tables in the Log Database with non-sequential unique identifiers. Please update the schema manually to improve performance. This is a non-mandatory update and will affect all new Log Databases automatically.
• #10432 - The Admin Log View is now on top and also loads faster as less data is loaded
• #10328 - Tons of icons have been replaced in many places
• #10266 - Changed the presentation of the date-time result in Log Views (always in the browser's local time).
• #10268 - In 6.0 (#7420), we added date time offset to the Copy API URI and Share query buttons. With 6.1, we changed from a local offset to UTC. We urge you to update your non-events Monitoring using the URIs.
• #9886 - Nodinite resets the modal state if a User is very quickly switching between screens before the previous screen loaded to completion
• #9888 - When the User pastes a search (Share query) in a new tab or uses a bookmark, the auto-start search feature is honoured
• #9709 - Editing a deleted Item now usually displays a banner to help the User understand that the item is in the deleted state.
• #9710 - The view Source in Articles has been reintroduced as we now support Markdown (#7464)
• #9875 - Changed the alert for the expiring product key. It is now visible on all pages.
• #10154 - A repository User without access to a Resource no longer sees it in Services; hence, custom metadata is not present if set on the Resource level. In version 6.0, the User saw the Resource.
• #10034 - Removed clipboard.js and ngclipboard.js
• #10035 - Removed snap.js
• #10047 / #11289 - Bump Font Awesome to 6.5.1
• #10017 - Keep diagnostics files for four days instead of 6 files for the Logging Service
• #10841 - Changed the interaction with accordions in the Admin Log View
• #10535 - Changed the Edit Monitoring Agent icon from Resource in a Monitor View
• #10877—If the connection is lost, an Alert is displayed on the screen; when the network connection is re-established, the alert does not disappear.
• #10878 - The auto-healing filter on Resources showed the column without the ambulance icon even though all entries were disabled.
• #10883 - The number of Monitor Views was lost; it has now been reintroduced in the pie chart on the Dashboard available for Administrators.
• #11050 - Changed the toaster text synchronizing with Agents.
• #11095 - Changed the display order of content for Contracts.
• #11102 - If a User navigates to Deleted Log- and Monitor-View, a Forbidden message is presented.
• #11007 - The dotnetzip Nuget package has been replaced and discontinued.
• #11383 - The Monitor Views now include Integrations as a column with an Edit and Landscape button for quick navigation according to user allowance. Also, remove the Integrations filter if the User does not have the proper Repository grants.
• #11414 - Changed the layout editing Custom Fields.
• #11757 - Changed the behaviour when adding an hour to a not active Maintenance User Notification

Known Limitations and Workarounds

• #10934 - The connection string for Web API, Monitoring Service, and Logging Service must have a proper Encrypt=true;TrustServerCertificate=true part. Otherwise, clients may receive SSL Handshake problems when performing various operations.
• 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.
• #11578—Expanding large groups in a Log View can take a long time to load. This issue has been resolved in a later 6.1 build, but the fix is not part of the official release (6.1.0.66).

Fixed Issues (Bugs)

• #10407, 10729 - Another fix applied for this problem with a patch to a stored procedure to get late data from BizTalk (also in 6.0.1.16).
• #10738 - In some SQL Server environments, a call to determine if the target is AOAG or not raised an unexpected exception, terminating the maintenance job without doing its intended job. ( also in 6.0.1.16)
• #10453 - Fixed a problem in the Integration Landscape with Services and Contracts including Resources that are Deleted or Missing in Monitor Views.
• #10418 - Fixed a problem when a Role was Restored; earlier, the administrator had to update the Role again to make it operational.
• #10133 - Fixed a problem when a recurring maintenance mode spans less than 24 hours.
• #9892 - Service Instance Activity Id was set to an empty guide on message processing. This was also fixed in 6.0.1.11
• #9930 - The message details page has an operational find-related feature.
• #9824 - If the User has a Resource that is not part of any Monitor View with Remote Actions allowance, the User is now informed that there is no permission.
• #10342 - The Agent Overview closed the Action button on the automatic refresh interval, causing the User to lose the open Action button entries on the screen.
• #10348 - Removing the Repo access rights rendered the administrator's role useless.
• #7420 - Fixed multiple problems with the time zone searching and sharing data from Log Views. A User in some time zone can now share the result with another User in another time zone and still get the same data on screen.
• #10400 - Fixed a problem if a User grouped by the "Text" field without any other search field
• #10363 - Changed the error handling inserting Logs through the Log API
• #10559 - Alert emails always had Customer Name 'IBSS'; this has been resolved with the following XSLT match. <xsl:value-of select="Customer" />
• #10594 - None of the 'Add' buttons in the Repository Overview were operational; this issue has now been resolved
• #10843 - Fixed a problem navigating back in the browser after duplicating entities
• #10852 - Fixed a problem with the Filter of Context Properties in Log Views
• #10303 - Removed the link on Monitor Views Health Chart (Overview) as it has no target
• #10881 - The blinking bell in Web Client showed an incorrect number of alerts; also, the blinking type has changed
• #10993 - The input field for the Between mathematical operator was not operational for date times
• #10867 - Fixed a problem editing retention for a single message type
• #11091 - Quick add matches also on description fields, which breaks the option
• #10898 - Changed the Logic in SQL, inserting new MessageTypes to avoid duplicates during high-load
• #10730 - Prevent shapes in the Landscape from moving around on load after a save operation
• #11312 - Fixed a console error in the Import/Export pages
• #11378 - Fixed the sort order of custom metadata values in filters
• #11417 - Fixed a pristine check editing a placeholder value for a Search Field in use with a Log View
• #11482 - Fixed a problem with Include Deleted Contracts in Services
• #11527 - Users with Repository read rights cannot interact with the Actions button in the view pages. This has been resolved. Also, a problem displaying the Transport Contracts icon in the Services and Contracts overview pages has been fixed.
• #11534 - IBM Db2 as an Endpoint Type was not adequately managed. This fix also adds support for IBM Sterling.
• #11577 - Fixed a problem displaying the figures to count auto-healing retry attempts.
• #11560 - Fixed a caching problem Deleting/Restoring Log- and Monitor-Views

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.

Fixed Issues (Bugs)

• #10407 - Changes on the logic to process and delete events from BizTalk. If the payload and/or context was late from BizTalk to Nodinite, the Log Event in Nodinite could incorrectly lose the reference to the payload and context.

System Requirements

• If you use the Azure Logic Apps agent, install/update 6.0.15.0 or later
• You should use the latest Nodinite install and update tool (6.0.0.65 or later)
• You must update all Monitoring Agents to v6
• You must use the latest DacFX (161 or later)
• Please review and adjust the SqlPackageExecutable system parameter accordingly BEFORE you perform the update.

Update Requirements

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