Enhancements and revisions in Adagio OrderEntry 8.1F (2014.05.02)
New Features Done
Supports Transport Layer Security (TLS) / Secure Socket Layer (SSL) for secure email servers when emailing documents. Added option 'Use TLS/SSL' added to Email Setup function. Note: This new feature does not require a workstation install as it did in recent upgrade versions of PurchaseOrders and DataCare. If either of those versions were installed, the From field in received email showed the Return Address rather than the Display Name when emailing from any module, and there was an error when emailing from any module on an XP station. Installing OE will correct these problems in all modules. Secure email servers are not supported on Windows XP.
Added new codes to the specification designer for use on picking slips and other documents:
F44, total quantity originally ordered
F45, total quantity ordered
F46, total quantity backordered
Added option 'Allow create credit note' to the Entry Template in Security Groups to prevent certain users from entering credit notes.
The BOM Item and BOM fields previously added to the Inventory Transaction History record can now be shown in item grids in OrderEntry.
Problems fixed
Corrected problems in document entry, import orders and day end, where some fields were incorrectly defaulted from the customer / Shipto in some cases when a customer had a contact that was not a Shipto address and the Contact Code was blank (allowed for legacy reasons).
Changes have been made to improve the performance when Document Filters are used at sites with a large number of documents, many users and a large volume of document entry and printing.
When the 'Allow editing of invoice/credits' option was on in the Company Profile, the Manual Style Code could not be edited on invoices or credit notes by user SYS.
You can no longer change any detail type to a Text Block when editing an existing detail. Doing so caused a problem in some cases.
In OrderEntry 8.1F, disabling the option 'Allow editing of invoices/credits' did not work.
In OrderEntry 8.1F, if user SYS had a blank Security Group, the Company Profile option 'Allow editing of Invoice/Credits' was not respected. You had to make SYS belong to a Group that enabled the option.
In OrderEntry 8.1F, if when creating a Security Group you clicked on the Entry Template button before entering the new Group code, then canceled from adding the Group, the setting in the main Entry Template in the Maintenance menu were lost.
In OrderEntry 8.1D and higher, the Price List reports were missing from the menu tree in Security Groups for standalone OE (no IC). Note: these reports/functions show in the menu tree when IC is used and are not functional.
The Edit Item function from within OrderEntry did not respect the 'Allow invalid vendors' option in Adagio Inventory.
The spec code 'D41, Unit price per stocking unit' was actually printing the price per selling unit. The code has been renamed to 'D41, Unit price per selling unit' and new code 'D79, Unit price per stocking unit' has been added.
The Order Action Default template for the Order Action report could be overwritten and duplicates appear in some cases if you typed in an non-existing template name.
When printing the Tax Tracking report from an Automation FIle, if there were no records to print, the Automation file halted.
If the 'Allow editing of invoice/credits' option was on in the Company Profile and you edited a document that had already been copied to history, when Day End was run by an Automation File, the question asking whether to overwrite the History was not suppressed. A Noun with choices 'ReplaceHistory' and 'KeepHistory' has been added to the DayEnd command to handle this situation. Note: Existing Automation Files using the DayEnd command must be edited and resaved, otherwise the automation will be halted when the command is encountered.
OrderEntry 8.1F could not convert Plus OE databases to Adagio OrderEntry and an error was displayed.
The number of Previously Opened databases (saved by user) was increased from 25 to 100.
An error was displayed when installing to a 2 Terabyte drive or larger, although the install completed without problems. The error has been changed to a warning.