Typically three or four times each year, NetDocuments provides an Update to its Service. These regular updates include user interface (UI) changes, bug fixes, new features or enhancements, and updated client add-on software. To help customers who may be new to NetDocuments and as a reference for all customers, this article describes what the regular Update process entails and the recommended steps you can take to prepare for an Update.
General Update Process
NetDocuments Updates are numbered after the order in which they take place during a given year. For example, the first update of 2018 is referred to as 18.1, the second update is 18.2, etc. (the last quarter of the year usually does not have an Update.) The first Update of each year is usually the most significant because it has a longer iteration time for development, and so includes more changes. These Updates usually occur on a Thursday night just before midnight, so when users log in Friday morning, they will have the Update. This timing allows customers to experience the Update at the end of the week and allows a full weekend for subsequent testing, or training by a customer. Customers are not impacted during this Update process. A customer can continue to work through this process and the next time they login following the Update, they will see the new updated software.
About three weeks prior to an Update, NetDocuments will post on the Support Site an Announcement that includes details about the Update. These Update Notes contain information related to the new features, updated client software, and major bug fixes included in the Update.
Beginning with the release of 17.2 in September 2017, we have implemented a flexible update model. Your organization will have the flexibility to choose your go-live date for any given release, within a pre-determined window. Our new flexible update model allows each customer more control over timing when transitioning to new releases. This process accommodates customers with policies that prohibit changes to vital systems during critical times of the year (such as year-end or tax season).
Unless you have some users who are testing the beta, there is no need to adjust your Hosts file or DNS server in order to make the transition to the Update.
If you wish to transition to 18.2 on 12 July 2018
On 12 July 2018, all customers will be switched to the new Update.
No action is required on your part. As with previous NetDocuments Updates, your users will automatically see the new Update on that date without any changes on your part.
Only the latest version, 18.2, will receive continuous updates. After the official release of 18.2, the 18.1 version will only receive fixes related to critical defects and security issues.
Delaying the Update
A NetDocuments customer can choose to delay the upgrade to 18.2 until 9 August.
To do this, contact NetDocuments Support prior to 10 July and they will assist you in converting your repository to remain on the current Update. All users in the repository will then remain on 18.1.
If you wish to transition to 18.2 between 12 July and 9 August
Customers will also have the option to upgrade to the new release at any time of their choosing after 12 July 2018 through 9 August 2018.
Similar to the option above, contact NetDocuments Support prior to 10 July and they will work with you to schedule a date and time when you want to switch your organization to the new Update.
How can I prepare for a NetDocuments Update?
- Test the beta. We recommend that you include as many testers as you feel you can manage. These testers should be individuals who use the product each day and who would recognize a defect in the product and report the steps to reproduce it. We ask testers to actively review the new features and report bugs they discover.
- Train your users. NetDocuments provides several resources to help you. Our Help articles are updated during the week prior to the Update. We also provide tutorial videos that demonstrate the key features and changes.
- Update client software. You may also want to install software as soon as one week prior to the update, although it is not required (except the ActiveX). To do this, you will need to access the beta to download the new versions of the software. These can then be tested in your local environment, after which they can be pushed out to all of your users. As NetDocuments only supports the most recent version of each of its client software, we recommend installing the latest version(s) as soon as possible after an Update (if not before).
Beyond this, nothing needs to be done. NetDocuments is a web-based application, so users will always see the latest updates when they log in.