Security — We have added user and timestamp to every table to track who changes setup tables and who makes requests. We have also added menu level security that can restrict what is available on the menu for any given user. The structure will also support securing rules and tables (available in the near future). This will allow NaviX customers to implement whatever level of security is needed based on their internal requirements.

Output to Excel — You will now be able to extract data into XML format (current), SQL*Loader format (current) or Microsoft Excel comma-delimited format (new). You will be able to identify English headers for your columns and translate codes into text. This will provide more flexibility in the use of NaviX .

Input from Excel — You will also be able to upload comma-delimited files into your Oracle database.

Iconic Menus — You will definitely notice the difference when you move to NaviX 3.5! We have changed the menu structure to use images instead of the previous linked text strings.

Performance Improvements — NaviX 3.0 supports asynchronous processing. This means that for high volume requests, you can submit the request then move on to do other tasks without locking up your PC or the NaviX session. You can continue to monitor the progress of your request through the NaviX request status screen. Any number of requests can be submitted for processing, and multiple processors can be defined to support multi-threading of requests.  In addition, the use of SQL*Loader will facilitate the manipulation of large blocks of data.

New User Interface — The front-end of NaviX 3.0 has been totally rewritten using Oracle PL/SQL and HTTP Server. NaviX screens can now be viewed using your Internet browser, no longer requiring the use of Oracle Forms.

"Rules in Rules" — The new NaviX rule setup allows you to define business objects and re-use the business objects within other business objects. For example, you can create a rule called “Client” with all of the client related tables, then reference the client rule each time you have a link to client data.

Multiple Start Values — This allows you to base your selection of data for a NaviX rule on multiple variables when extracting or archiving data. For example, you could select a date and a product type against which to extract data.

Improved Default Values — If an incoming import file does not contain a not-null column and the column is defined in NaviX with a default value, NaviX will automatically add the column with the associated default value during the import. If the column is in the incoming import file, NaviX ignores the default value.

Bulk Export/Import — This new features allows you to select a NaviX option (e.g., export/archive), select a NaviX rule (from your defined rules), then type in a list of starting values to execute the rule for.  NaviX will automatically generate requests for each of the starting values, as well as a file which can be used to later generate corresponding Import requests for each of the exports.

Batch/Auto Execute — This feature has been enhanced so that the "execute now" option will display a list of the newly created requests, as well as creating a file containing a list of the individual generated requests (see Bulk Export/Import above).

Wildcard Data Map — The NaviX data mapping function now allows you to map a wildcard to new values.

Auto Execute — The new “auto execute” feature can now be used to support automatic running of any NaviX rule, including those that require a starting input value. The “auto execute” screen now has a query window where you can type in a query to select start values to be processed. This provides tremendous flexibility in determining the data to be accessed for a given rule.

Enhanced DB Update Feature — A DB Update button has been added to the NaviX Rules screen. This button will allow you to add/delete columns to all applicable NaviX rules, based on changes to the database structure, without requiring you to individually access each rule or table. You can exclude certain rules from the DB Update process, if necessary.

Multiple File Directories — NaviX now allows you to use separate file directories for the different NaviX functions. For example, you can archive data to a different directory from the one used for exports.

Database Views — NaviX now supports the use of database “views” in the NaviX rules.

Simplified Setup — The NaviX screens for the initial “set up” and definition of applicable code values have been redesigned to be simpler to use.

A new “auto execute” feature allows you to schedule a NaviX rule to be invoked automatically on a periodic basis

NaviX rules now have a new start value type  of “NONE” which will cause NaviX to bypass the screen that prompts for starting value

The DB Update button on the NaviX Tables screen has been enhanced to provide a summary screen which displays the tables and columns that have been updated

A new Delete Table button has been added, which will remove a table (and all of the corresponding columns and access instructions) from a NaviX rule, without requiring you to separately delete the corresponding data

A new View Summary button has been added to the Batch Results screen, which will allow you to view a summary of the results of any NaviX request processed in batch

You can now validate an import file (prior to running the actual import) to check for the potential file errors. The entire import file is checked and all issues are reported back to the user.

	All referenced tables must be in database.
	All referenced columns must be in database.
	All not-null columns in database (for tables in file) must be defined in the file, or a default value must be defined.
	All map names referenced in the file must be in the database.