Elliott 8.6 Requirements and Features Compatibility
Version: 8.6
Introduction
Unlike prior versions, Elliott 8.6 starts using the PSQL relational database engine to support features like Report Desk, PowerSearch, and Avalara. If you are thinking of using Elliott 8.6, this document will help prepare you to meet the requirements.
Generally speaking, Elliott 8.6 is compatible with prior versions of Elliott so you can run them side by side to allow you an extensive evaluation period before you fully convert to 8.6. Therefore, installing Elliott 8.6 has minimum risk. However, if you wish to use certain features in Elliott 8.6, they may have some limitations with regard to their compatibility with prior versions. You may want to migrate all your users to Elliott 8.6 before starting to use those features.
For example, the Avalara Sales Tax Interface posts strict requirements. Before implementing Avalara, you should first implement Elliott 8.6 with some users. Then start converting your Elliott users from prior versions to V8.6 one by one. Finally, implement all the prerequisites required by Avalara step by step.
Windows Server Requirements
- Windows 2012 Server
- Windows 2016 Server
- Windows 2019 Server
- Windows 2022 Server
Windows OS Requirements
- Windows 8 (all versions exception Windows RT)
- Windows 10
- Windows 11
PSQL Requirements
- PSQL 13 (May require v4.3.0.9811 released on 5/6/2019 or higher)
- PSQL 15
.NET Requirements
- 4.5 or higher (it comes with most modern Windows OS)
Features Compatibility with Prior Versions
Generally speaking, Elliott 8.6 can run side by side with prior Elliott versions. There maybe limitations depending on what features you like to use in Elliott V8.6. Certain 8.6 features are only be compatible with newer Elliott versions and some are exclusive to 8.6. Since you might keep some of your users on the older Elliott version during migration to 8.6, this can introduce complexities. In this section, we are providing guidelines on how the new Elliott features are compatible with prior versions. Below is a list of key features in Elliott 8.6 that are in question:
- Report Desk: Report Desk requires your database be converted to support segmented keys. This feature is compatible with all prior Elliott versions.
- PowerSearch: PowerSearch requires your database be converted to support segmented keys. This feature is compatible with all prior Elliott versions.
- Avalara: Avalara sales tax interface requires segmented keys and alphabetic document numbers. Once implemented, the AR (Accounts Receivable) and COP (Customer Order Processing) modules can only run in Elliott 8.6. The other modules can be in 8.5 or 8.6.
- Segmented Keys: To support the Elliott database for relational operations, we need to make sure the database supports segmented keys. If this is not yet done, you need to go through a conversion process. This feature is compatible with all prior Elliott versions.
- Alphabetic Document Number: Starting with Elliott 8.5, Elliott supports alphabetic document numbers which require conversion. Once converted, all Elliott users must run Elliott 8.5 or higher versions.
- Remove DAT Files: In Elliott 8.6, you can remove DAT files (for setup info) from your DATA* folders to tighten NTFS security. Once you do this, all your users must run Elliott 8.6. This step is optional and ls likely to be the last step in your migration to Elliott 8.6.
This following table summarizes the prerequisites of the three new features in 8.6: Avalara, Report Desk, and PowerSearch. It also shows the Elliott versions required to implement the prerequisites:
|
Prerequisites |
Compatible Versions |
Avalara |
Report Desk |
PowerSearch |
|
Segmented Keys |
7.5 – 8.6 |
Required |
Required |
Required |
|
Alphabetic Document Number |
8.5 – 8.6 |
Required |
Optional |
Optional |
|
Avalara |
8.5, 8.6 (AR & COP) |
NA |
Optional |
Optional |
|
Report Desk |
7.5 – 8.6 |
Required |
NA |
Optional |
|
PowerSearch |
7.5 – 8.6 |
Required |
Optional |
NA |
|
Remove DAT Files |
8.6 |
Optional |
Optional |
Optional |
Example 1 -- If you choose to implement PowerSearch, you must implement "Segmented Keys" as well. You can run PowerSearch in Elliott 8.6 side by side with other Elliott versions.
Example 2 -- If you choose to implement Avalara, then you must also implement "Segmented Keys," "Alphabetic Document Number," "Report Desk," and "PowerSearch," Once you implement Avalara, your AR and COP modules must run on Elliott 8.6. The rest of the modules can continue to run in 8.5.
Suggested Step-by-Step Procedure to Implement Avalara
Based on the above information, there are a lot of prerequisites to implement Avalara. We suggest the following steps to do so successfully:- Install Elliott 8.6 with your current Elliott Installation. Run Elliott 8.6 with prior versions side by side.
- Have some of your advanced users start using Elliott 8.6 first.
- Ensure the Elliott Database Is segmented. If this is done already, you can skip this step.
- Make sure all your users are using at least 8.5 & up.
- Convert the Elliott Database to support alphabetic document numbers. You don't need to use the alphabetic document number feature. But your database needs to support it. This may potentially bring up compatibility issues with your current Crystal Reports or third-party applications like shipment manifest systems. It is a good idea to test it first in a separate company.
- Start experimenting with the new features of Report Desk and PowerSearch so you know how they work in general.
- Make sure all your AR and COP users are migrated to Elliott 8.6.
- Implement Avalara.
EMK