CMS TEN Upgrade Plan
From NewHaven Software Wiki
(Difference between revisions)
Russ horton (Talk | contribs) (→Prep) |
Russ horton (Talk | contribs) (→Required) |
||
| (63 intermediate revisions not shown) | |||
| Line 1: | Line 1: | ||
=Prep= | =Prep= | ||
| - | *Review the [http://updates.newhavensoftware.com/ | + | ==Required== |
| - | * | + | *Whats New in CMS TEN - Review the CMS TEN Release Notes: |
| - | * | + | **[http://updates.newhavensoftware.com/whatsnew1001.htm v10.0.1] |
| - | *Database Connections - If you have any database connections to CMS that are using the dbo database user credentials, they must be switched to the cmsuser credentials. | + | **[https://updates.newhavensoftware.com/whatsnew1005.htm v10.0.5] |
| - | **The default password for cmsuser is case sensitive and is CMSUser. As part of your PA-DSS Implementation this password should have been changed long ago, but, if you are still using it, be sure that you have the case correct. | + | **[https://updates.newhavensoftware.com/whatsnew10014.htm v10.0.14 (current)] |
| + | *Encryption - The Encryption option in PCI Administration must be enabled before installing CMS TEN. Please log into CMS as PC Administrator and verify yours is turned on before proceeding. To do this, log into CMS as PCI Administrator and go PCI Administration>PCI. Your button for encryption should read 'Re-Encrypt' AND say "no further action is necessary" as seen in this [http://screencast.com/t/0qiBvCUQ7u screenshot]. If so, you're set and there's nothing more you need to do (no need to re-encrypt). If instead the button says "Encrypt" or you have a message that says "http://screencast.com/t/B8Q07gVur Your credit card holder data needs to be updated..." this means you'll need to run the Encrypt/Re-Encrypt. We recommend you run encryption overnight while everyone is out of the CMS. If you install the update and encryption has not been run, the install will warn you of this encryption issue and abort. | ||
| + | *If you worked with us on testing the UPS Worldship keyed imports performance solution in CMS 9.x, please contact NHS Support to have that removed before you update to CMS TEN (the latest version of this solution will be installed with CMS TEN but this is not designed to update the beta implementation of this feature from v9). | ||
| + | *Custom Reports and Forms - Please consider installing a test version of CMS TEN to confirm they will work with CMS TEN. If there are any issues, please contact NewHaven Software Support to contract any necessary fixes. | ||
| + | *Custom Integrations - NewHaven will keep all standard integrations current including those with UPS, FedEx, Endicia, Peachtree, and payment gateways. If you have developed any integrations of your own, please consider installing a test version of CMS TEN to confirm they will continue to work. Please contact NewHaven Support if you'd like assistance with setting up or updating your test environment. A list of the database and XML changes can be found in the [http://updates.newhavensoftware.com/v10release_notes.htm#db Release Notes]. | ||
| + | *Database Connections - If you have any database connections to CMS that are using the dbo database user credentials, they must be switched to the cmsuser credentials or your connections will fail. We recommend updating these before installing CMS TEN to ensure no connection errors. | ||
| + | **The default password for cmsuser is case sensitive and is CMSUser. As part of your PA-DSS Implementation this password should have been changed long ago, but, if you are still using it, be sure that you have the case correct. The most common use of an ODBC connection to your database is for keyed imports from UPS Worldship, it's ODBC connections named CMSPackages and CMSPackagesExport. | ||
=Install= | =Install= | ||
| - | Go [http://wiki.newhavensoftware.com/index.php/Test_Install HERE] for information on installing a test environment. | + | '''NOTE: You must be running CMS 8.0 or later before upgrading to CMS TEN''' |
| - | #Get everyone out of CMS (TIP: delete the file CMSNET.dat to confirm all users are logged out) | + | *Test Installs - Go [http://wiki.newhavensoftware.com/index.php/Test_Install HERE] for information on installing a test environment.<br> |
| - | #Update your server - This process | + | *All Installs |
| + | #Get everyone out of CMS (TIP: delete the file CMSNET.dat from the \NewHaven Software directory to confirm all users are logged out. If you are unable to delete the file, it means there are still users logged into CMS. They will need to log out or you can disconnect the open files on the server at the risk of their losing their work.) | ||
| + | #Update your server - This process may take up to twice as long as a typical server update. Upgrades from versions earlier than 8.x are not supported and, in such cases, an intermediate update to 8.0 will be necessary. NOTE - Your version 9 release code can be used to upgrade to CMS TEN, no new code required. | ||
##Verify you can log into CMS without error | ##Verify you can log into CMS without error | ||
| - | #Update workstations - Only necessary for Windows 8.x workstations | + | #Update workstations - Only necessary for Windows 8.x or 10 workstations |
=After Install= | =After Install= | ||
==Required== | ==Required== | ||
| + | Reiterating the above, if you have any workstations running Windows 8.x or Windows 10, you'll need to run a CMS workstation update on each to ensure the database drivers have been updated. This workstation update is run using the same installer software that was used to update your server. | ||
| - | + | There are otherwise no further post-update steps required. | |
| - | + | ||
| - | + | ||
| - | + | ||
| - | + | ||
| - | + | ||
| - | + | ||
| - | = | + | ==Recommended (optional)== |
| + | Changes or settings worth examining shortly after updating (if you've not already done so in a test environment): | ||
| + | #Last Card Used - If CMS is configured to recall the last credit card used, in such situations a new dialog message comes up asking if you want to use the card ending in XXXX (displaying last four digits.) If yes, the card will come over masked (cannot be unmasked) or, if you say no, you can proceed with entering a new payment. Previous versions would have just recalled the payment without telling you the last four and, if it was not the one you wanted, you would have had to delete the payment. Keep in mind card data is only retained per your PCI Data Retention Policy so no prompt to use the last card will be presented once the card data has been removed from the database. | ||
| + | #Manifest Changes - A few changes here worth reviewing before turning your shipping dept. loose on it for the first time. | ||
| + | ##We've changed the way shipping methods are selected in the Manifest and added features to allow the setting of carrier pickup dates. | ||
| + | ##Also, if you have multiple shipping stations using the Manifest, the default is now that each station will only show its own packages instead of a master list of all manifested packages. | ||
| + | ##See a full list of Manifest changes in our [https://updates.newhavensoftware.com/v1001release_notes.htm#link-1-21 Release Notes] | ||
| + | #CMS TEN supports 'Active' flags now which are on by default. Removing this flag will prevent inactive choices from being offered in Order Entry or other places where new transactions are created. Inactive choices are still viable though for orders that were created using those now inactive choices. The goal is not to remove these choices from your system entirely but instead to limit new transactions to using only current options. | ||
| + | ##Shipping Methods | ||
| + | ##Adcodes | ||
| + | ##Order Source | ||
| + | ##Price Catagories | ||
=Known Issues= | =Known Issues= | ||
| - | * | + | *CMS is attempting order status uploads for all eCMS order sources. If you've never uploaded order status before, you may experience an error since the resulting upload would be too large (potentially years worth of data.) There is an easy/quick fix to this which our Tech Support staff can assist you with if you run into it. Issues Dev-201 and 221 |
Current revision as of 19:58, 5 May 2020
Contents |
Prep
Required
- Whats New in CMS TEN - Review the CMS TEN Release Notes:
- Encryption - The Encryption option in PCI Administration must be enabled before installing CMS TEN. Please log into CMS as PC Administrator and verify yours is turned on before proceeding. To do this, log into CMS as PCI Administrator and go PCI Administration>PCI. Your button for encryption should read 'Re-Encrypt' AND say "no further action is necessary" as seen in this screenshot. If so, you're set and there's nothing more you need to do (no need to re-encrypt). If instead the button says "Encrypt" or you have a message that says "http://screencast.com/t/B8Q07gVur Your credit card holder data needs to be updated..." this means you'll need to run the Encrypt/Re-Encrypt. We recommend you run encryption overnight while everyone is out of the CMS. If you install the update and encryption has not been run, the install will warn you of this encryption issue and abort.
- If you worked with us on testing the UPS Worldship keyed imports performance solution in CMS 9.x, please contact NHS Support to have that removed before you update to CMS TEN (the latest version of this solution will be installed with CMS TEN but this is not designed to update the beta implementation of this feature from v9).
- Custom Reports and Forms - Please consider installing a test version of CMS TEN to confirm they will work with CMS TEN. If there are any issues, please contact NewHaven Software Support to contract any necessary fixes.
- Custom Integrations - NewHaven will keep all standard integrations current including those with UPS, FedEx, Endicia, Peachtree, and payment gateways. If you have developed any integrations of your own, please consider installing a test version of CMS TEN to confirm they will continue to work. Please contact NewHaven Support if you'd like assistance with setting up or updating your test environment. A list of the database and XML changes can be found in the Release Notes.
- Database Connections - If you have any database connections to CMS that are using the dbo database user credentials, they must be switched to the cmsuser credentials or your connections will fail. We recommend updating these before installing CMS TEN to ensure no connection errors.
- The default password for cmsuser is case sensitive and is CMSUser. As part of your PA-DSS Implementation this password should have been changed long ago, but, if you are still using it, be sure that you have the case correct. The most common use of an ODBC connection to your database is for keyed imports from UPS Worldship, it's ODBC connections named CMSPackages and CMSPackagesExport.
Install
NOTE: You must be running CMS 8.0 or later before upgrading to CMS TEN
- Test Installs - Go HERE for information on installing a test environment.
- All Installs
- Get everyone out of CMS (TIP: delete the file CMSNET.dat from the \NewHaven Software directory to confirm all users are logged out. If you are unable to delete the file, it means there are still users logged into CMS. They will need to log out or you can disconnect the open files on the server at the risk of their losing their work.)
- Update your server - This process may take up to twice as long as a typical server update. Upgrades from versions earlier than 8.x are not supported and, in such cases, an intermediate update to 8.0 will be necessary. NOTE - Your version 9 release code can be used to upgrade to CMS TEN, no new code required.
- Verify you can log into CMS without error
- Update workstations - Only necessary for Windows 8.x or 10 workstations
After Install
Required
Reiterating the above, if you have any workstations running Windows 8.x or Windows 10, you'll need to run a CMS workstation update on each to ensure the database drivers have been updated. This workstation update is run using the same installer software that was used to update your server.
There are otherwise no further post-update steps required.
Recommended (optional)
Changes or settings worth examining shortly after updating (if you've not already done so in a test environment):
- Last Card Used - If CMS is configured to recall the last credit card used, in such situations a new dialog message comes up asking if you want to use the card ending in XXXX (displaying last four digits.) If yes, the card will come over masked (cannot be unmasked) or, if you say no, you can proceed with entering a new payment. Previous versions would have just recalled the payment without telling you the last four and, if it was not the one you wanted, you would have had to delete the payment. Keep in mind card data is only retained per your PCI Data Retention Policy so no prompt to use the last card will be presented once the card data has been removed from the database.
- Manifest Changes - A few changes here worth reviewing before turning your shipping dept. loose on it for the first time.
- We've changed the way shipping methods are selected in the Manifest and added features to allow the setting of carrier pickup dates.
- Also, if you have multiple shipping stations using the Manifest, the default is now that each station will only show its own packages instead of a master list of all manifested packages.
- See a full list of Manifest changes in our Release Notes
- CMS TEN supports 'Active' flags now which are on by default. Removing this flag will prevent inactive choices from being offered in Order Entry or other places where new transactions are created. Inactive choices are still viable though for orders that were created using those now inactive choices. The goal is not to remove these choices from your system entirely but instead to limit new transactions to using only current options.
- Shipping Methods
- Adcodes
- Order Source
- Price Catagories
Known Issues
- CMS is attempting order status uploads for all eCMS order sources. If you've never uploaded order status before, you may experience an error since the resulting upload would be too large (potentially years worth of data.) There is an easy/quick fix to this which our Tech Support staff can assist you with if you run into it. Issues Dev-201 and 221
