Topic
- Becoming familiar with new features
- Ensure the requirements for set up have been implemented
- Minimize the risk for production down time
- Integrate existing botflows into the new environment
- When changing the License configuration setup (local license set up to shared, split license merging)
Instructions
Moving from version 16.x to 17.x and up:
The current license key is the main key, a customer can upgrade or set up a test server prior to upgrading.
1. Upgrade:
- Confirm system requirements: Release Notes
- Back up Nintex RPA Central and associated botflows: Back up instructions
- Access latest release from either the Release Notes or the Customer Portal->Product Releases
- Download and run installer, beginning with server first for Nintex RPA Central
- Confirm that Nintex RPA Central opens and the users exist
- Download and run the installer for each of the client machines
2. Test Server:
- Request a trial key: Trial Key
- Review the system requirements in the: Release Notes
- Make sure everything is set up environmentally: Pre-installation Steps
- Our trial is the latest version of RPA: Download and install Nintex RPA Central on server
- Optional: Install a bot on the server to start adding existing botflows which will appear in Nintex RPA Central and test them
Moving from version 15.x to 17.x:
- Request a trial key: Trial Key
- Review the system requirements in the: Release Notes
- Make sure everything is set up environmentally: Pre-installation Steps
- Our trial is the latest version of RPA: Download and install Nintex RPA Central on server
- Optional: Install a bot on the server to start adding existing botflows which will appear in Nintex RPA Central to be accessed by the clients
- Remove License from old server in versions 15.x and lower
- Switch the trial to an actual license: https://u.nintex.com/self-rpa-central-administration-v2/626036/scorm/bzyw1lrnx8dy
Additional Information
Botflows ending in .rpa file extension will not need to be converted as our newer version uses the .rpa file extension. Of course, you will still need to test your botflows and make any changes if necessary in the newer version.
We highly recommend backing up your botflows. In version 15.x and below, the botflows are saved on the local machine (export option was built in a later version).
Related Links
License Keys (License Information for reference)
The customer should be able to find their new license keys and downloads in the Nintex Customer Portal<https://customer.nintex.com/>. They are listed on the left hand side of the page under “Licenses” and “Product Releases.”
The customer can also submit a request through licensing@nintex.com
The customer can also reach out to their Account Manager to assist.
License Editions
- Standard Edition - allows customers to move up to latest version (17.x+)
- Enterprise Edition - used in versions 16.x and later (not compatible for versions 15.x and below)
- Concurrent Edition - only used by RPA versions 15.x and below (grandfathered license)
- Bot Edition - used in versions 16.x+
--------