- 4 minutes to read

Version – System Parameter

The Version system parameter displays the currently installed version of Nodinite. This read-only parameter is automatically set during installation and update operations.

What you need to know about this parameter:

  • Read-only parameter - Cannot be manually modified
  • Shows current Nodinite version (e.g., 7.1.0.0)
  • Automatically updated during installation and upgrades
  • Used for version verification and compatibility checks

The Version System Parameter stores the current installed version of Nodinite in your Environment. This value is automatically set and updated by the installation and update processes, providing a reliable reference for the platform version running in your integration landscape.

System Parameter Name Data Type Values/Example Comment
Version string 7.1.0.0 Read-only. Automatically set by installation/update processes. Format: Major.Minor.Build.Revision

This parameter is maintained by:

Important

This parameter is read-only. You cannot and should not modify this value manually. It is automatically maintained by the installation and update processes.


How the Version Parameter Works

The Version parameter serves several important purposes in the Nodinite platform:

Automatic Version Tracking

During installation or update operations:

  1. Installation Process Begins - PowerShell 7 scripts or legacy Install and Update Tool starts
  2. Database Updates Applied - Schema changes and updates are deployed to Configuration Database
  3. Version Updated - The Version parameter is automatically set to match the deployed version
  4. Verification - System uses this value to verify successful deployment

Version Format

The version follows the standard .NET versioning format:

Major.Minor.Build.Revision

Example: 7.1.0.0

  • Major: 7 - Major version (significant changes, new features)
  • Minor: 1 - Minor version (incremental improvements)
  • Build: 0 - Build number
  • Revision: 0 - Revision number

Usage in the Platform

The Version parameter is used throughout Nodinite for:

  • Compatibility Checks - Ensuring components are compatible with the installed version
  • Upgrade Validation - Verifying successful completion of upgrade operations
  • Support Diagnostics - Providing version information for troubleshooting
  • Feature Detection - Determining available features based on version
  • Web Client Display - Showing version information in the Web Client Menu - Version

Frequently Asked Questions

Find more solutions and answers in the Nodinite System Parameters FAQ, as well as the Troubleshooting user guide.

How do I check my Nodinite version?

You can check your Nodinite version in several ways:

  1. Web Client: Navigate to Menu - Version in the Web Client
  2. Database Query: Query the SystemParameters table:
    SELECT Value FROM SystemParameters WHERE Name = 'Version'
    
  3. Install and Update Tool (v6): View the version on the Overview page
  4. PowerShell Script (v7): Check the version during installation/update output

Can I manually change this value?

No! The Version parameter is read-only and maintained by the system. Manually changing this value:

  • Will cause version mismatch errors
  • May break upgrade processes
  • Can lead to compatibility issues
  • Is not supported and may void support agreements

What if my version appears incorrect?

If the Version parameter shows an incorrect value:

  1. After Failed Update: The version may not have been updated due to an error during the update process
  2. Manual Database Modification: Someone may have incorrectly modified the value
  3. Incomplete Installation: The installation process may not have completed successfully

Resolution: Run the appropriate update process to ensure the version is correctly set.

How is this different from the product key?

  • Version Parameter: Shows the currently installed version of Nodinite software using semantic versioning
  • Product Key: Determines which major version of Nodinite you're licensed to run

Key Licensing Requirements:

  • Nodinite 7: Requires a Nodinite 7 product key
  • Nodinite 6: Requires a Nodinite 6 product key

Version Updates:

Nodinite 7 uses semantic versioning and typically releases monthly patched versions following .NET standards:

  • Major version (7.x.x) - Requires corresponding product key
  • Minor/Patch versions (7.1.x, 7.1.1) - Monthly updates within licensed major version
  • All updates within the same major version are covered by your product key

What happens during version upgrades?

When upgrading Nodinite:

  1. Services are stopped
  2. Database schema is updated
  3. Version parameter is updated to the new version
  4. Components are updated
  5. Services are restarted

The Version parameter automatically reflects the new version after a successful upgrade.

Can different environments have different versions?

Yes! Each Nodinite Environment (Development, Test, Production) has its own Version parameter. This allows you to:

  • Test new versions in non-production environments first
  • Run different versions across environments during phased rollouts
  • Maintain production stability while testing upgrades

Next Step

Install Nodinite v7 - Installation guide
Updating Nodinite v7 - Upgrade guide
Menu - Version - View version in Web Client
<i class="fas fa="fas fa-leaf" aria-hidden="true"> Environment - Understand environments