NetX is continually improving our software through new version releases, and we refine our internal product roadmap using a variety of input, including:
NetX Ideas Portal — customers can submit ideas for features and functions they would like to see in the NetX product; they can also help us prioritize these ideas by voting.
Customer Support — our support team provides clear insights into the issues that are challenging for customers, and which are generating the most calls to support.
Customer Interviews — before embarking on a major new feature, NetX typically performs interviews with customers to help gather use cases and define product requirements.
Beta Previews — NetX will occasionally demo beta versions of new features to customers in order to validate their usability.
Industry Trends — NetX is vigilant, ensuring we stay ahead of the curve in terms of industry trends.
Product Strategy — our long-term strategic vision for the product.
We have a strong track record of providing regular releases over the last 15 years. Each of these releases contain a variety of improvements, including bug fixes and new features. Historically, the time between new versions can vary from one month to a year — but on average, new versions are released every quarter.
Between new version releases, NetX often provide “Service Packs”. These upgrades explicitly only contain bug fixes, and will not include new features. Typically, NetX will release one Service Pack between each new release. However, if the new version schedule is too short, then the Service Pack may not be released; and conversely, longer version release schedules may warrant more than one Service Pack release.
NetX does not publish our roadmap publicly. We don’t provide definitive dates for future releases, nor can we promise that specific features and functions will be included in a particular release. Please appreciate that while we may plan a feature for a release, many factors affect it’s final inclusion in an officially released new version. The scope of requirements may increase during development, and/or unforeseen technical challenges may force the function to be delayed until a subsequent release. Additionally, QA and/or user acceptance may find critical issues with the usability of the function; this can lead to a delay in the current release, or its removal from that release. In some cases, we may be forced to remove a function and/or entire feature just before release.
User Research Program
We can and do occasionally share future plans with certain customers. If you would like to help shape the future of NetX beyond just submitting ideas, we would love to hear from you! Participation in our user research program typically involves:
Non-disclosure and confidentiality
If you are interested in pursuing a deeper level of participation in NetX, please contact your Account Manager.
If you are a SaaS customer, upgrade requests can be submitted via a support ticket. When an upgrade is requested, NetX will provide the latest version for installation. We require all upgrades to be scheduled 48 hours in advance. On-premise (self-hosted) customers can download the latest version here: Product Downloads.
All NetX upgrade releases undergo extensive quality assurance testing. Individual unit tests are performed for each new feature and/or bugfix, which are then tested against the entire application via automated and manual test scripts in various environments. Once the release successfully passes NetX's internal QA process, it can then be applied to the customer’s staging/dev/test instances for additional integration testing.
Upgrade Best Practices
We recommend that customers prepare for upgrades by following these best practices.
- Review Release Notes: You can find the release notes for each Major, minor and patch release here. If you have a particular question about something you find in the release notes, please create a support ticket and we can give you more details. Also, the Product Downloads article often includes special instructions for customers who host their own NetX instances.
- Deploy to a Test Environment: We strongly recommend that you first deploy each upgrade to a test environment that is a exact mirror of production. If you host your own NetX, please see How to Create an On-Premise Test Environment in Windows for assistance on setting up a test environment. If you are a SaaS (hosted) customer, you can request a test site by contacting Support.
- Create and Execute a Test Plan: A Test Plan is a written script of steps that includes all of the common tasks and workflows that your users carry out on the system. By running through the Test Plan on your test environment before you upgrade, you can verify that the release successfully supports all of your workflows without issue.
- Verify Server Health (on-premise customers): Before upgrading, have an experienced System Administrator check your server(s). Is disk space full? How does memory usage look?
- Perform a full backup (on-premise customers): Always make sure you have a valid backup before upgrading your production site. For more information, see Backing Up NetX.