FrontLine Desktop Release Notes

- Fixed: Potential SQL error using Export Journal Entry Lines for All Accounts from the Trial Balance when specific Location and Ledger Account Type are selected for the trial balance.

- Fixed: Customer Invoice Costing failed to use Trade-In values of unit-costed inventory.
This fix is in the CostInvoice db procedure.

- Added a Total Revenues subtotal to the Income Statement. This sum excludes Revenues - Other.

- In vendor Payables and customer Receivables the Closed view now opens with the most recently due at the top.

- In Periodic Invoices there is now a Consolidate Receivables function that combines all the AR in a periodic invoice into one receivable per [Customer, GL Account, and Bill-To] on the periodic invoice end date.
Receivables that have had credits, or payments, or write-offs applied to them before consolidation cannot be consolidated.
If an invoice that was part of a consolidated receivable is returned it will create an open credit when the return is completed, it cannot be automatically applied.
A Periodic Invoice Batch cannot be cancelled after consolidating its receivables. Batches that have had their AR consolidated are indicated by a black stamp icon.
In the Receivables window, consolidated individual receivables are shown as pink zeroed values in the Applied list of the sum receivable they were consolidated into.
The consolidated receivable (sum) value is marked as a Doc Type Periodic Invoice with [DocType] value 64.
The periodic invoice Ending Date becomes the Invoiced date of the new receivable,
the new Due date is calculated from this Invoice Date using the customer's Terms
and the new receivable's Posted date is the date of consolidation.

- FrontLine now ignores intangible package members when evaluating the quantity of a package first line to invoice based on fulfillment of package members.
This revision is in the NewInvoice db procedure.

- FrontLine now copies the Item Category to line items so that existing line items retain their category after a stock item's category is changed.

- Start a simple log of user changes to a Scheduler Event Start time. This log is not yet exposed to users.

The Db Console contains six required updates:
File: CostInvoice v7.0.061
File: NewInvoice v7.0.061
TRX.ItemCat (7.0.061)
File: CopyLineItems v7.0.061 Apply this one after TRX.ItemCat
ORDERS.ContractID (7.0.061)
AR.BillTo (7.0.061)

- Elaborated Company Setting Accounting Options to add a new option Recurring Billing Unearned Revenue JE Dates - Adjust to Open Period to automatically adjust Journal Entry Line JE Date for Recurring Bills forward to the next open Accounting Period if the date falls in a period that is Closed or AR Closed.
This is often necessary when recurring bills are generated for the past.
Reminder: FrontLine creates unearned revenue JE lines for recurring bills of periods greater than a month when relevant Item Categories have an unearned revenue account indicated in their Item Category Accounts.

- The Department selector is now available in purchasing when departments are in use and the new Company Setting Accounting Options Purchasing uses Departments is turned on.
Department is only required for purchasing line items that have a GL Code of account type Revenues or Expenses.
Department can be set for the entire order, or on individual line items, or both in which case the line department takes precedence.

- Fixed: FrontLine does not submit Late Fees to AvaTax so late fees last step processing should not try to commit AvaTax invoices that it did not create.

- Fixed: FrontLine 7.0.058 introduced a bug upon adding miscellaneous purchase suggestions to a new or existing PO. It changed TotalItems on unrelated orders.

- Payables Pay Now by Check now has a Duplicate Stubs feature that enables check-stub-stub output. This also requires a different APChecks form vs the single stub output.

- Fixed: Column title click sorting the Journal Entry Lines in Account Inquiry to sort by the Debit or Credit columns should sort by the JE Line Amount.

- Fixed: Recurring Billing should use a customer-specific AR account (when specified for a customer) for the AR receivable entry, as it already does for the JE receivable line.

- Fixed: 7.0.056 broke the addition of Miscellaneous Purchases auto-gen additions to an existing PO with a key violation of PK_TRX at the Add To PO step.

- Fixed: Customer Order Total Quote Items calculations were incorrect when rental period pricing with multiple periods was used on the line items.

- Job Details analyses now show "Costed Qty" in a separate column, highlight the value in bold when it differs from the line "Quantity" and use it to calculate the "Ext Cost" and variances.
This discrepancy is expected when a line is costed at "SpecialPQ" (Cost Special Order Intangible sales at Purchase Quantity) with purchase quantity different from sale quantity.

- Added a Standard Cost security context in the Customer Orders class.
If a user has a NULL or "None" permit value for this context then the "Standard Cost Column" menu entry does not show up.
And likewise now if a user has no permit for the adjacent C.Cost security context then the "C.Cost Column" menu entry does not show up.

- Fixed: Vendor purchase suggestion line counts in Generate Purchase Order should ignore the item's default vendor for customer order line items that have an alternate vendor specified in Resource Costs.

- Fixed: Company Setting Lookup Options Include agent name in Agent values shown should apply to Customer Orders and Purchasing windows.

- Fixed: The Customer Orders Ship-To drop down selector should include "Lookup Customer Drop-Ship Address..." instead of "Lookup Vendor Drop-Ship Address..."

- Fixed: In the Opportunities feature the Details function raised an ambiguous column name error.

- A recent revision caused purchase line items created by auto-gen to start at line 200 or 20 instead of 100 or 10.

- FrontLine now requires both BaseLink URL and Customer Portal URL Company Settings to activate the Publish to Customer Portal via BaseLink behaviours.

- Recurring Billing now copies a reference to the source Equipment Set (S.Doc) Identifier Document to the Recurring Bill itself (ESETS.UI to ORDERS.UI) for easy reference on the bill, and the user is not allowed to change the order identifier document on recurring bills or their refunds.

The Db Console contains a recommended data update: Recurring Bill UI from ESETS

- Fixed: A recent revision made Quote-only users unable to modify their own quotes.

- The built in image viewer now preserves aspect ratio when it fits the image to the window.

- Fixed: Journal Entries for Recurring Bill Refunds should set the JE Date of the AR line of the JE to the posting date, and any unearned revenue JE lines that were dated in now closed periods should have their date moved forward to the first period following the last closed period.

- Fixed: "Invalid argument to date encode" error once per session on a leap day. This could cause FrontLine to fail to create one journal entry.

- Fixed: To be consistent with how addresses are submitted to AvaTax during recurring billing, AvaTax submissions for "Recurring Bill Credits" should submit the Bill-To address as the Ship-To address when the recurring bill has no Ship-To address from the equipment set Residence.

- Fixed: In some circumstances it was possible to create a Vendor Invoice from a Purchase Order where the Vendor had no default Pay-To address, and the Vendor Invoice would end up with a Pay To address of the last vendor that an invoice had been created for.

- Added data checks in Recurring Billing to prevent more than one user from executing or cancelling the same Step thus creating duplicates or other discrepancies.

- Customer Special Orders checked out with option Cost Special Order sales by special Purchase Cost in Company Setting Cost Options have a new option to Cost Special Order Intangible sales at Purchase Quantity. This marks the costing "Method" as "SpecialPQ" and uses this purchase quantity for Cost of Sales in the customer invoice journal entry where it would otherwise use the sale quantity for intangibles.
Part of this revision is in the CostInvoice database procedure.

- In Item Category Accounts these accounts are now required: Income, Inventory, COS, Clear Inv, AP Discrep, Phys Adj Offset.
And these accounts are no longer shown: Inv Drop Ship, Clear RA, Clear Exch, Repair Exp, Vendor Refund, Labor Reimburse, Allow Damage.

- Added a Clipboard Commit feature available from the Selected Items context menu of Line Item Details for uniquely identifiable items.
This feature enables a user to copy a list of primary identifiers from a spreadsheet column or text file and have FrontLine validate then commit them to the current line item.

- Fixed: The output for AP Payments (Check Register) (details, not Summary) did not provide the context menu function with enough information about the order type so that it could open a vendor invoice.

- Fixed: Returning a Recurring Bill that had no JEID would not create a Journal Entry for the return because there was no reference journal entry. In this case FrontLine will now create a new journal entry directly from the bill credit.

- Fixed: After a Shipment that had an associated shipping charge was Cancelled and the shipping charge line voided in this process, invoicing the order to completion left the order in "Partially Invoiced" (lack of Completed) status. This fix is in the CommitInvoice database procedure.

- Fixed: After entering a Total Quantity value for a non-identifiable item in Physical Count the cursor would end up in the expected row but the view would scroll making it confusing to the user.

- Fixed: Equipment Search with the Include Non-Identifiable Items option off would include non-identifiable items anyway if the Search On Hand Inventory option was on.
And added an option to Exclude Rented Units when the Search On Hand Inventory option is on.

- Fixed: In Package As Discount mode when the package price was set directly from $0 discount to full discount (net zero for the whole package) FrontLine did not remove the taxed values of the package members. This would show up in tax reports.

- In a Vendor's Payables, or the Payables Dashboard, the list of payables can now be sorted by clicking column titles, and in All Payments mode the list of payments can be sorted too.
Note that the "Pay Now" and "Write Off" and "Doc Type" columns are not eligible for sorting.

- The inventory unit detail list of Inventory Valuation now shows the current status and the status at evaluation if they differ.
This makes it easy to see the current status of rented inventory, for example.

- FrontLine can now show JPEG (JPG), PNG, GIF, and BMP local images referred to in Identifier Documents directly in its internal image viewer.

- The Transactions missing Journal Entries special report for System Administrator now includes Recurring Bills.

- Drop-down lists of Vendors are now sorted by vendor name before vendor number.

The Db Console contains a required update that is backwards compatible:
File: CommitInvoice v7.0.053

- Fixed: When a customer order was closed with a receivable credit but without an invoice, like when the last open line items are cancelled instead of fulfilled and full payment had been taken by check, FrontLine did not create a Journal Entry for the AR.

- Fixed: When Web Parts were imported for an Agent whose Location differed from the Order Location, FrontLine failed to use the customer's price levels.

- The Order Totals summary now simply refers to "Sales" instead of "New Sales" for six of the columns.

- Fixed: Customer Order Redo could fail to transfer the Order Discount value resulting in a Line Effective Total Mismatch when the new order was opened.

- To enable drop-shipping purchases to another vendor, the Ship To address context menu for Purchase Orders now has separate Lookup Customer Drop-Ship Address... vs Lookup Vendor Drop-Ship Address... commands.

- For line items on completed orders that are not history orders, users with "Read, Add, Modify, Delete" (all) access to the Payables security context now have a line item context menu entry to toggle the History type of that line item so that it can be excluded from some inquiries (line Purchases Received without AP) and reports.
These changes to the line item history type appear on the change log.

- The line item context menu in purchasing now has a History Line toggle available on closed non-history orders to users with full "Read, Add, Modify, Delete" access to the general Payables security context.

- Fixed: Purchases Received without AP from AP Inquiry had some Qty Invoiced issues.

- Added a Unbalanced System JE security context in the Journal Entries class to enable users to change the Amount and Account of an unposted unbalanced system journal entry.

- Fixed: When a specific Location was selected for an Income Statement the account type subtotals of Budget values included all locations instead of only the selected location.

- Export of Journal Entry Lines in Trial Balance and Account Inquiry now includes the OrderRef, Location, Department, and JE Created date of the JE Lines.
OrderRef is also shown in the FrontLine (Trial Balance or Account Inquiry) window itself when the window is wide enough.

- Purchases Received without AP and Vendor RAs without AP from AP Inquiry now show any where the Vendor Invoice quantity does not match the (PO or V-RA) quantity, and if the Qty Invoiced exceeds the (PO or V-RA) Qty Received then those quantities are highlighted in yellow on the output.

- Detail (not Summary) AP Inquiry output for AP Payments (Check Register) now includes a [Vendor Ref] column for the Vendor Invoice.

- Added a Form 1099 Vendors special Search By to Vendor Lookup to list all Form 1099 Vendors.

- In the the list of a Vendor's Payables a user can now toggle the 1099 type of a payable for a vendor with a Form 1099 option using the 1099 Payable context menu function.
The user must have a F1099 context permit in the Vendors class greater than "Read Only" to do this.

- Fixed: FrontLine 7.0.045 introduced a bug refreshing the bottom line GL Amount value for Ending Balance of a Bank Reconciliation

- Fixed: Clicking a "R" (reconciled) checkbox in an open Bank Reconciliation and then changing the "Sort by..." order before moving the grid cursor lost the new checkmark.

- Fixed: Improved FrontLine System Users recognition of MSSQL database role assignment to users. The scheme it was using was unreliable for newer SQL Server versions.

- Fixed: AP entries for Vendor Invoice Cancellations should have [Invoiced] and [FinancialDate] set from the cancellation invoice by the same rules as an original Vendor Invoice instead of a copy of these two dates from the original vendor invoice AP.

- Fixed: Discrepancy calculations needed rounding in the creation of Journal Entries for Vendor Invoices.

- In the Form 1099 Payments Summary quick report the Tax ID now outputs Corporations as xx-xxxxxxx instead of xxx-xx-xxxx

- The Form 1099 Payments Summary quick report now includes Total Paid for ALL Payments made to the Vendor, and highlights the numbers in yellow when they don't add up.

- Moved the 1099 Payments Summary quick report link from the General Ledger section to the Accounts Payable section of the Welcome window.

- Journal Entry Lines in Trial Balance and Account Inquiry now outputs [Entity] (Customer Number or Vendor Number) and [Entity Order] (Customer PO or Vendor Reference) for export, and on screen when the window is wide enough. The filter includes these outputs.

- The Tax Report now includes a LocationDescription output, and tax report batches can now be voided using the context menu or keyboard shortcut.

- Email templates now provide a special tag <FLF>CustomerPortalURL</FLF> to output the base Customer Portal URL from Company Settings.

- The file name of templates used for Forms for Orders now qualifies the output to be Published to the Customer Portal.
CP_ directly after the base form file name is the trigger.
CPA_ is an alternate trigger that qualifies the publication for an Approval by the Customer.
Approval request is communicated to BaseLink using HTTP parameter ForApproval=1
Invoices and outputs related to invoices are submitted to the portal as Invoices
Quotes and Orders are submitted to the portal as Estimates

Here are examples of a quote form for approval, and an invoice form:
QuoteCPA_YourQuoteForApproval.rep
InvoiceCP_YourInvoiceFromMe.rep

- Fixed: In the Reconciliation Check Tally of Cash Drawer Reconciliation a check of large amount would appear with the green check mark before the user checked it off.

- Fixed: Receivables shown for a Warranty Vendor included Paid Transaction entries that were from the repair order customer who paid the non-warranty share of the service invoice.

- After processing Payables Pay Now by... FrontLine now offers output of Remittance Advice that can be produced invidually from the payment list for non-check payments, or for the list of checks successfully printed.
Output uses a form named APRemittanceAdvice.rep with the same optional account-specific form name option as the APChecks.rep form.

- Comments generated for Payables to Card Issuers that were created from AP Card Payments now contain the name of the Vendor paid instead of the name of the card issuer.

- To make longer AP comment texts more visible, FrontLine now enlarges the Comments column of Payables and All Payments grids when the selector enters the comments column.

- Fixed: Voiding a Payable Payment should set the Financial Date of the void entry to the Applied Date instead of the original Payment date.

- Fixed: A recent revision caused problems voiding AP Card Payments, such as refusal for "Net Zero" or failure to refund the payable to the Card Issuer.

- Account Inquiry output for AP Payments (Check Register) now includes a [BankDate] column from Bank Reconciliation.

- Fixed: Bank Reconciliation creation and refresh encountered a key violation of PK_BANKRECON when adding multiple AP Payments that were issued at the same time by different users.

- Purchase quantity suggestions in Generate Purchase Order (auto-gen) for replenishment of items with Min and Max quantities should suggest a quantity to restore inventory to Max instead of Min level.

- Pointing at an entry in the New Journal Entry from Template list in the Journal Entries feature now discloses in the status bar that you can (Hold down Ctrl key to open the Template) itself.

- Journal Entry Lines in the Journal Entries feature now highlight the Account in pink if the Location Segment is invalid or for a Closed Location.

- Before posting a Journal Entry, if active Locations have unique [LocationGL] codes then Journal Entry Lines are checked for a valid Location Segment that is a Closed Location.
If any are found then the journal entry is left unposted during system journal entry creation, or during manual journal entry posting the user is asked for confirmation before posting.
These JE Lines of closed locations have their Account highlighted in light purple.

- Recurring AP now offers checkboxes as an option for the user to hand pick vendor invoices to generate from the list.

- Pointing at the Line number box in Line Item Details discloses when the line was created.

The Db Console contains a required update, to be executed one line at a time. This update is not backwards compatible:
BANKRECON Key Revision (7.0.045)

- Fixed: Purchase Orders should not allow Receive activity on a line item with blank Cost.

- Fixed: When line items of Item Type Assigned Price were turned into Quotes they lost their effective quote Tax.
The tax came back when unquoted.

- Fixed: A recent revision of the Void Payment function in Payables voided only the single AP credit instead of all the AP credits from that payment.

- Fixed: Another combination of circumstances in Generate Purchase Order (auto-gen) that could cause an SQL error upon Accept to generate suggestions.

- FrontLine shows more information about consequences of changing the Item Type of Transacted Items between fundamental types Inventory, Service, and Charge.
And there is now a script provided in the Db Console to help support fix history data inconsistency caused by such a change.
Note that the script cannot create inventory transactions for items changed from intangible to tangible.

The Db Console contains a helper script for auto-gen issues caused by changes to fundamental (Inventory, Service, Charge) Item Types:
File: Clear Inventory of Intangibles

- Fixed: The line item COS account for Adjustments that are not a physical count should use the Cost of Sales item category account rather than the AP Discrepancy account.

- Fixed: History Purchase Orders should not be eligible to create Vendor Invoices.

- Recurring Billing now flags Closed Locations as an exception in the Exceptions and Batch Review stage.

- In the Journal Entries feature for the JE Lines there is now a Manual Column Resize option in the context menu.

- In the Receivables window the Applied list now shows the full comment of the selected credit in the status bar when pointing at the Applied list.

- In the Payables window the context menu for the Applied list now includes an entry to open the relevant Credit Memo when applicable, as well as the Purchase Order.

- When the user tries to void a customer order with only external (like Shopify) tenders that have been processed (authorized or captured) FrontLine now notifies the user and confirms that they want void the order anyway, instead of refusing because there are tenders on this order that must be returned (voided) before the order can be voided.

- Added a Filter (on Name, Address, Subject, or Agent) for the Task List (tentative events) in the Scheduler feature.

- In the Receivables window added a context menu uption to Show Location instead of Pline for the receivables list.

- Fixed: Purchase suggestions for Special Orders of Services in Generate Purchase Order (auto-gen) incorrectly suggested ordering the service again when the existing special purchase had been checked in, and a potential SQL error upon Accept to generate suggestions for =ANY= Vendor when future order options were in use.

- Fixed: When part of an AP Credit is Applied in Payables this applied fraction should refer to the OrderID reference source of the credit instead of the source of the payable.

- Fixed: Return of an order with many units per line item from the Returns could cause an access violation and subsequent inoperability of this instance of FrontLine until it was relaunched.

- Fixed: Upon committing an invoice, FrontLine should set the department of any invoiced line items that have no specific department assigned to the department of the order. This way if the order department is changed later those invoiced lines keep the department they were invoiced under. This fix is in the CommitInvoice database procedure.

- Fixed: Special Order lines added to Purchase Orders by auto-gen should copy the customer special order Department so that it can be applied to line item accounts such as Discrepancy.

- Fixed: FrontLine should ignore authorized zero value customer order tender lines during check out.

- For direct Write-Offs in Receivables FrontLine now uses the Department segment from the customer order (if any) as the first choice for the write-off account.
This is necessary because receivables typically have no department, while write-offs affect department income.

- When the user tries to void an external (like Shopify) payment tender that is authorized but not captured FrontLine now advises the user to cancel the payment using that external system.

- Added a confirmation when the user tries to void a customer special order line that is already on a PO, that if they unvoid it later they will no longer be able to use the special cost.

- It is now possible to Reverse a System-Generated Journal Entry when logged on as an administrator and the Ctrl key is held down when the Reversing Entries function is activated.
FrontLine prompts the user for the JE Date of the reversal, with a default of the original JE Date, and checks for closed periods.

- In the Journal Entries feature the "New Journal Entry from Template" list can now show up to 48 templates instead of 24.

The Db Console contains two required updates:
Expand ESETS.CustomerPO (7.0.042)
File: CommitInvoice v7.0.042

- Fixed: Void Payment in Payables could erroneously declare Net Zero when a follow up payment is voided, and Void AP entries should refer to the original payment user.
These changes are complementary, and the second part requires a data revision using the "Fix AP Payment Void User" Db Console script.

- Fixed: Purchase suggestions in Generate Purchase Order (auto-gen) incorrectly evaluated demand vs supply for non-special orders.

- Fixed: FrontLine should not try to reverse authorized zero value customer order tender lines, it should ignore them.

- On new Transfer Orders, FrontLine now ensures that the user has assigned a distinct Transfer To Location before adding a line item.

- Location ledger Accounts that are not "GL Code Only" now have their Department segment set when used on an order with departments.
For example, this sets the department segment of an Order Discount line.

- For direct Write-Offs in Receivables FrontLine now copies the Department segment from the receivable account to the write-off account.

- Order Lookup now has a special Search By "Quotes, Presented, without Orders"
Note that while the "Quotes, Presented" search includes orders that were partial quotes, the new "Quotes, Presented, without Orders" search only includes dedicated quotes.
And both of these now consider the company Presented Quote Life when applicable, so the search becomes "Quotes, Presented, without Orders within 30 days" for example.

The Db Console contains a required data fix script:
Fix AP Payment Void User (7.0.041)

- Fixed: "New Budget begin date..." error creating a new annual Budgets using mid-year account periods, and not accepting user input for existing budget period values.
Budget Period Values entry assistance options: % for a percentage of prior year actual. A to apply to All later periods. S to spread into all later periods.
Examples:

- Fixed: Percentages entered in Budgets should refer to the prior year Actual value instead of prior year Budget value.

- Fixed: Warranty Vendor Invoices should not cover package members whose package was applied to the repair unit under warranty when the user had removed the package from warranty coverage. This fix is in the NewInvoice database procedure.

- Scheduler Event Lookup now has a special Search By "Incomplete Past Events over 180 days old" that is the same as "Incomplete Past Events" except that it only includes events over 180 days old.

- Journal Entry Import is now more helpful to find the first issue in a large import.

The Db Console contains a required update that is backwards compatible for all 7.x releases:
File: NewInvoice v7.0.040
Note that there was no 7.0.039 release.

- Fixed: Some recent revisions threw off two subtotals on Income Statement
"Operating Income" should exclude Other Expenses and Other Revenue, and "Gross Margin" should exclude Other Revenue.

- Fixed: Equipment Search with option Show only Equipment under Contracts would include equipment that was under contract in the past.

- Fixed: The JEDate of Journal Entry lines for Returns of multi-month Recurring Bills should use the JEDate of the original JE when that date is later than the latest closed Accounting Period, but the JEDate of JE Lines that were dated prior to this date should be dated to the beginning of the next open period.

- Fixed: The customer order check out process should not consider card or external shopping cart tenders that have been authorized but not captured as verified.
Instead, if the tender is external (like Shopify) then the check out process will stop, and if the tender is internal then the check out process should attempt to capture it.

- The "Include Resource Costs" option in the line Copy List has been removed for now.

- FrontLine now validates more Location folders at logon to avoid potential mysterious delays later when it looks in these folders:
"Report Folder" "SD Folder" "Image Folder"

- The Income Statement now has an option (on by default as before) to "Show Account Sub-Type Sums"
and the option to not "Show GL Codes" now is available for all "By..." methods except "By Account Type" where there are no GL Codes to show.

- Added a Company Setting Company Account Types Used to indicate which overall GL Code (Ledger Account) Types are used.
By default at least one GL Code of each of the five general account types are required: Assets, Liabilities, Revenues, Cost Of Sales, and Expenses.
When an account type is unchecked here FrontLine does not warn users if there are no GL Codes of this type defined in the company Ledger Accounts.

- Fixed: The serial receiving sequencer in the Receive feature could drop intermediate zeroes for identifiers with more than 10 trailing digits.
Note that FrontLine can only serialize up to 19 trailing digits.

- Fixed: A recent revision broke line Cost determination of Work Order Assemblies as the lines were added to the work order.

- Fixed: 7.x introduced a failure to find relevant meter readings in the first step of Recurring Billing at the Begin stage.

- Fixed: The Checked In quantity in Generate Purchase Order (auto-gen) always showed zero.

- Fixed: Accounts that were marked "GL Code Only" were missing from Income Statements.

- Fixed: A blank JE Date column when viewing Journal Entry Lines that constitute rows on an Income Statement

- Fixed: The Show Accounts with Zero Ending Balance option in Income Statement did not reveal those hidden accounts.

- Fixed: When a Vendor Invoice that originated as a credit is applied in AP, and then this vendor invoice is Cancelled, FrontLine should add reversing entries for those applied AP Credits, restore the value of the original credit, and not allow users to void the reversed AP Credits.

- Fixed: An AP Cash Tender could be voided more than once (using the Void Payment context menu function in vendor Payables) when the user who voided it differed from the user who created the AP Invoice. This bug was probably introduced in 7.0.011

- Fixed: Paid Transaction entries in Receivables should not include in-process (not captured) card tenders.

- Fixed: Applying a full Payment balance to a single receivable in Receivables after part of that payment credit had been written off or otherwise consumed would apply the original payment value instead of the balance.

- Fixed: A recent revision made it mysteriously impossible to leave a customer record in Customers maintenance if that customer had a positive credit limit and no default bill-to address.

- Fixed: Changing the Special Order state of a Package line item did not change the auto-commit behaviour of package members until the order was deferred and reopened. The effect occurred if the package quantity was then changed.

- Changes made to the Minimum Balance and Days Past Due sticky print options of Receivable Statements now update the green highlights in the list below immediately instead of only after leaving the input box.

- In AP Inquiry the F8 key now runs a report, and the F3 key invokes Vendor Lookup instead, when applicable.

- The context menu available from the yellow System Administrator indicator in the Welcome window now has a function to find Transactions missing Journal Entries in a quick report with order links from which JE can be created. Results show Customer Orders before Purchasing, and newest first within. Third Party POs are excluded from this list.

- Added a Show Accounts with Zero Balance toggle to the Balance Sheet that is available when the output is not By Account Type

- A user who has no permission for the Vendor Invoices security context is no longer offered the special lookups "Open Vendor Invoices" and "Recently Approved Vendor Invoices" and cannot open Vendor Invoices via other paths.

- Ledger Accounts setup is improved with its own function outside Lists setup, and now have optional Subledgers to make collections of GL Codes that can be merged on the Income Statement
Subledgers on the Income Statement are italicized for distinction, and the "Period Journal Entries" output of a subledger show the JE of all the GL Codes in that subledger.
There is a new security context Ledger Accounts and Subledgers in the "Accounting Periods" class for this function.

- FrontLine now synchronizes a user's BaseLink password when the user's FrontLine password is changed without a prompt.
Password length must now be as least 7 characters, with a mix of letters and other characters like digits and punctuation.

- Fixed: The 7.x revision included closed line items in Allocated quantity sums in Scan Match.

- Fixed: Order Lookup specifically by Placed date did not obey the Newest First output request.

- Fixed: The summary row values shown in the Details analysis of Jobs were doubled. This bug was introduced in 7.0.028

- Added LineLocationExtRef to the outputs of Forms for Orders. This complements the existing (Order) LocationExtRef and (Transfer) SourceLocationExtRef outputs.

- Fixed: When a Receivable (AR) Write-Off that has a journal entry is Unapplied FrontLine should prompt the user for an optional "Financial Date" to use for the JE Reversal, and ensure that this date is not in a closed period.

- The Income Statement no longer includes subtotals for account types that don't have journal entries, and no longer right-aligns the Account column of its Report output.

- Added a Posted Date column to the Summary output of AP Payments (Check Register)

- Fixed: Shipping Charge Calculators were not triggered when a repair part or service reassignment changed the warranty coverage of that part or service.

- Bank Reconciliation lines for customer tenders that were "Deposit(1)" before now display "Deposit: Bill-To Name" instead when it corresponds to a single cash tender.

- Fixed: The Shipping Charge Calculators were adding new shipping charge line items instead of revising an existing open shipping charge line.
This bug was introduced in the 7.0 line item table merge.

- The Resource Categories list on the Scheduler board now includes an <unassigned> entry so that multi-day views can show events that have no participants along with other resource selectors.

- In the Pay Now by Check function, after FrontLine has loaded a check form, a user who has diagnostic output (like sa or the special 321 password signature) can click the top banner "Information to Print AP Checks" to open the check form in the forms editor. The hover hint discloses this.

- Fixed: Bill-To address checking missed a case where FrontLine had added the On Account tender during the invoicing process.

- Fixed: The Balance Sheet subtotals could be mispositioned when accounts marked as "GL Code Only" are in use.

- Fixed: The Tax Report should output zero TaxedValue on outputs for AR Tax Write-Offs and Tax Adjustments.

- Fixed: 7.0.028 introduced an access violation when trying to email Recurring Billing Output

- Fixed: In 7.x custom tender types did not appear in Cash Drawer Reconciliation

- Fixed: For inventory Transfers, Average Cost at the destination location should update when the transfer completes.
This fix is in the CostInvoice db procedure.

- Fixed: A possible access violation on the Scheduler Board after reassigning an event's Participants in the Scheduler Event window.

- Fixed: Before posting system journal entries, FrontLine should attempt to automatically fix journal entry line accounts that are blank, but not invalid accounts.
This way the JE with invalid accounts remain unposted so that they are noticed and the process leading to them discovered sooner.
In this revision FrontLine wil no longer attempt to fix invalid accounts on system journal entries.

- Improved handling of the Jobs list criteria to ensure that the job shown below is listed above, and agent lookup is invoked for invalid agent entry in the job list criteria.

- FrontLine will now default users to save PDF files in their Documents\FrontLine folder instead of their current active folder.

- Bill-To Address Requirements is now configured in Notify Options of Company Settings.

- The Form 1099 Payments Summary quick report now includes Reimbursement and Total columns to complement the 1099 Amount value.

- In the Details analysis of Jobs there is now a simple Find Order function,
and a toggle to Summarize All Jobs where line items are condensed into order totals.

- This revision includes a alpha of the feature to Publish to Customer Portal via BaseLink,
with new Company Settings for "BaseLink URL" and "Customer Portal URL"
FrontLine uses HTTPS here, neither URL should include http:// or https://
For example, using port 23456: ormandy.abc.com:23456/BaseLink/
This feature is not ready for general testing.

- Fixed: More Bill-To address checking misbehaviour in Customers maintenance,
and FrontLine now similarly checks for required bill-to address values before invoicing Customer Orders that have On Account tenders.

- Fixed: In Payables Pay Now by Check FrontLine should ensure that the account type is a Cash account before printing any checks, instead of before confirming the output.

- Fixed: Selecting 256+ Payables would result in a key violation of PK_APPAYNOW when Pay by (Checks/EFT/Card) was then selected.

- Fixed: A recent revision caused items that were manually added to the purchase suggestions in Generate Purchase Order to not appear in the list of items to add to a PO.

- Fixed: In Company and Stations the Current Station WorkStationID did not enable typing in 4-digit ID values although StationID values 1000 to 1999 were allowed as of release 6.8.001

- Fixed: Export of Inventory Valuation with Details included when hundreds of units were listed per valuation row caused an access violation and subsequent inoperability.

- Fixed: 7.0.024 broke Inventory Transactions when Summarize by Day was selected.

- Fixed: The 7.0.025 revision to save Customers with a positive Credit Limit could cause misbehaviour on saving a new address added.
It should also require at least one phone number on the bill-to address, and ignore prospects.

- Fixed: Paid Transaction entries in Receivables should not show aging days overdue or highlights.

- FrontLine now requires user passwords to contain both letters and other characters because they will soon be unified with BaseLink.

- Entering a partial Account on a Journal Entry line now invokes the GL Account selector with the last location preselected unless the account is a "GL Code Only" type.
Before it would only do this for a JE line when invoked by F3 otherwise it preselected location segment 0000 for a partial account entry.

- Journal Entry line export from the Trial Balance now have separate columns for Beginning Balance and Ending Balance values, and their Account columns includes the account description.
The Debit and Credit columns in the export only show values for actual journal entry lines.

- Before checking in a Transfer order FrontLine now validates the transfers and notifies the user of lines that are invalid:
Transfer Source Location is the same as the Destination, or Inventory Destination Location does not match Transfer Order Destination, or Inventory Source Location does not match Transfer Order Source.

- Fixed: A revision in 7.0.015 also omitted Vendor RA identifiers from the output of Forms for Orders.

- Fixed: When the new invoice is a credit, FrontLine should not allow the invoiced total on an order to be more negative than the order total.

- Fixed: A past revision made FrontLine use $0 as the Taxed Value for internal tax calculations on a Package line item in Package As Discount mode when the package was first added to the order.

- To save a Customer with a positive Credit Limit FrontLine requires that the customer have a default Bill-To Address with Name, Address, City, State, and Postal Code.

- The Tax Report no longer uses line package (or package membership) as an input to determine Taxable vs Exempt column values.

- Fixed: FrontLine should not allow users to add Services or Charges directly to a Transfer Order.

- Fixed: A recent revision in auto-gen could cause the multi-vendor selection list to overstate the number of items to be ordered from that vendor.

- Journal Entry Lines shown (and exported) on the Trial Balance now have Beginning Balance and Ending Balance rows per GL Code.
When JE Lines for All Accounts are shown or exported, accounts that had no activity in the selected Period are included with only Beginning Balance and Ending Balance rows, and the JE lines are sorted by GL Code before JE Date instead of date first.

- On the Balance Sheet and Income Statement, when the output is By Account Code there is now a context menu entry Show GL Code that can be turned off.

- Inventory Transactions now indicate special orders with the Sp icon, and a context menu link to Item Quantities.

- FrontLine no longer looks for the LOCATIONS.PublishFolder column added in 7.0.000

- Fixed: When a partially invoiced order was changed by decreasing line quantities so that it could be completed with no more invoices,
the AvaTax revision in 7.0.022 would set the order total to zero.

- Fixed: Journal Entry Accrual Reversal should require the JE to be balanced already.

- The Income Statement and Trial Balance now have a Region selector (when applicable) like the Balance Sheet in 7.0.015

- The Completed Deposits list and individual View Deposit details in the Bank Deposit feature can now be Exported from the context menu.

- Customer Order Lookup now has a Job specifier in the upper right: Job NA (all) vs Job Orders vs Jobless.

- Fixed: Journal Entry creation for a Vendor Invoice (AP Invoice) did not exclude lines that the user had voided on the vendor invoice.

- Fixed: A recent revision could cause an error "Cannot insert the value NULL into column Line" upon accepting purchase suggestions in auto-gen, resulting in a blank PO.

- The AvaTax integration now handles invoices vs orders such that FrontLine can catch tax changes ahead of creating an invoice and notify the user to adjust tenders.

- FrontLine will now refuse to open a Payment order if the user has no permit for the Customer Orders - Receivables security context,
and if the user has a read-only permit then payment orders are opened as view only.

- Fixed: When Discount Presentation Company Setting Location for Item Category Accounts - Revenue and Cost of Sales is set to Order Location the Revenue and COS GL Accounts of such line items should use the Location Segment value of the Order Location.

- Fixed: When inventory is committed to a line item (with no inventory already committed) from a different location the line location correctly changed but the new event moved the inventory to the prior line location.

- Fixed: Adding a package to a service order where it is automatically assigned to the one repair unit could raise a key violation error on PK_MNTLOGI.

- Fixed: Purchase Quantity suggestions for an item in auto-gen were inflated by prior quantities checked in.

- Transaction Inquiry now offers a Type distinction between Purchasing and AP Invoices (Vendor Invoices).

- With a confirmation prompt, Bank Reconciliation now allows a negative value for beginning and ending balance.

- Added three sums to the New Vendor Invoice feature to help users keep track of what has been selected for a new AP Invoice: Selected to Invoice ___ Already Invoiced ___ Total ___

- For users who have no permit for the Customer Orders - Receivables security context the "Recent Account Payments" and "Open Account Payments" order lookup Search By entries no longer appear, and payment orders that appear for other searches have their "Total Order" value hidden in the lookup display.
And for users who have no permit for the Bank Deposits security context the "Open Bank Deposit Payments" order lookup Search By entries no longer appears.

- There is now a menu entry to open a Vendor's Payables in the drop-down from the vendor name on a purchase order or vendor invoice.

- Company Settings Card Tender Fee % and Shipping Charge % now accept fractional percentages.

- Fixed: Journal Entry creation for Recurring Bills of bill frequency longer than one month that contain multiple item categories within a bill resulted in a key violation of PK_JE upon creating JE Lines for the unearned revenue.

- Fixed: FrontLine 7.x did not set the line item Completed date (if the user had left it blank) upon the final invoice of that line. This fix is in the CommitInvoice database procedure.

- Fixed: SQL Server versions prior to 2017 do not support the TRIM function that FrontLine began to use in 7.0.015 upon completion of an AP Pay Now batch.

- When an imported line item with an agent identified is assigned to a repair unit line the imported line agent should not be changed to match the repair unit line agent.

- Exports of Inquiries should remove characters that are incompatible with the file system from the default file name.

- Journal Entry Lines in Trial Balance and Account Inquiry now have separate columns for Debit vs Credit amounts. The single Amount value is still available for export.

- The current and overdue Receivables values shown left of the Bill-To address on a customer order no longer appear for users who have no permit for the Customer Orders - Receivables security context.

- Fixed: A recent revision broke the creation of Receivable (AR) Write-Off Journal Entries by omitting the AR line of the JE.

- Fixed: Void Payment of an AP Payment by Card did not void the Payable to the Card Issuer.
Note that part of this fix is in the Payment process itself, so this revison cannot fix Void Payment on payments made in older revisions.

- Fixed: The Service Quotes view in Scan Match lost its unit-specific focus in the 7.x revision.

- Fixed: Non-identifiable inventory committed to a Transfer Order with Company Setting "Disable Auto-Commit" in Line Unit Identify options would end up at the source location.

- FrontLine now sets TRX.Updated to the current date and time whenever a line item is modified in order processing.
This revision requires a database update to add the new TRX.Updated column.

- Fixed: Approve a Vendor Invoice with no Vendor Ref raised the issue of the missing vendor reference but failed to stop the approval.

- Fixed: Shipping that created a shipping charge line on a customer order referred to obsolete table TRXIP.

- In the Journal Entries feature only the "New Journal Entry from Template" list shows the creation date, the JE lists under "Open Journal Entry" show the JE Date (or date..date range when the JE lines have multiple dates, like for recurring billing) instead.

- Fixed: The GLJE Date of the journal entry for a Vendor Invoice Cancellation should be the Financial Date of the Cancellation order, not the JE Date of the original Vendor Invoice journal entry.

- Fixed: Assigned Price and Unit Cost identifiers should be omitted from Forms for Orders output.

- Fixed: The Show Accounts with Zero Ending Balance option in Trial Balance should not hide accounts with non-zero Debits or Credits.

- When a Bank Reconciliation is Refreshed, FrontLine now recreates the Bank Deposit lines that have no Bank Amount entered in case any of those deposits had changed since they were added to the reconciliation.
FrontLine now displays Bank Deposit $nnn in the Comments column of bank deposit lines. The $nnn only appears if a user had entered a total "Deposit Amount" on the bank deposit.

- The payables list in the Payables Dashboard now includes a Vendor Ref column, and this value is included in the filter search.

- In the Report Usage log FrontLine now saves the report parameters used, delimited by §
Note that log entries created by prior releases have no parameter data on record.

- The Balance Sheet now has a Region selector when regions are in use.
Selecting a Region clears the Location selection unless the location selected is (0000)
and selecting a Location clears the Region selection because a location is a subset of a region.

- Composition of the Comments of AP Payments now removes extra white space so that more of the pay-to address can be included.

- For more accurate period closure validation, FrontLine now requires the user to set the Journal Entry Type of a new Non-System JE before the JE Date can be set.

- Fixed: Under some conditions, identifier display in Line Item Details could trigger an "Invalid floating point operation" error.

- The three Payables Quick Reports are now available in the AP Inquiry feature, where there is now a prominent inquiry selector on the left side of the window.
Inquiry links from the Payables Dashboard now open the AP Inquiry feature with the end date preset when applicable.

- Added a context menu entry Report Usage available to super users in the Reports window to show usage of a particular report, starting with the most recent.

- Reports can be hidden from normal use in the Reports window by placing a hyphen at the beginning of their Description.
There is no need to change the report File Name.
Hidden reports reappear when the report list is in maintenance mode so they can be revealed to users when needed.

- Fixed: FrontLine 7 introduced a key violation error on PK_MNTLOGI when receiving an identifiable member of a package via the line ready checkbox invoked auto-receiving the other non-identifiable members of this same package on the PO.

- The context menu available from the yellow System Administrator indicator in the Welcome window now has a function to
Find Inventory Committed to Voided or Quoted Lines (in a quick report with order links) and an offer to release them after.

- FrontLine now checks that an open Purchase Order meets the Vendor Minimum Order threshold before printing PO documents.

- The 7.0.012 expansion of the Account selector for Receivable Statements to list all GL Codes now ignores the accounts of AR write-offs.

- The Location selector for the Financial Inquiries (Balance Sheet, Income Statement, Trial Balance, Account Inquiry)
now have a (Show Closed Locations) entry if there are unlisted closed locations, to reload the location list including closed locations.

- The Balance Sheet now has a basic Include Unposted JE option like the Income Statement.

- In addition to the default list of Location AR GL Codes, the Account selector for Receivable Statements now offers to expand the drop-down list by analyzing AR to:

- Fixed: Under some conditions, some outputs from Forms for Orders could trigger an "Invalid floating point operation" error.

- Fixed: Multiple users completing the Payables Pay Now by... process at the same time could trigger a key violation on the APTENDERS table.
This fix also requires a primary key revision in the database.

- Fixed: Journal Entry Import did not mark the JE Lines with the JE Type specified by the user, so the JE would not post if either AP or AR was closed for the period.

- Added a Vendor Invoice Location column to the non-summarized Payables Quick Report output, and added an Aged non-summarized version so that there are now:
Payables Quick Report
Aged Payables Quick Report
Aged Payables Summary Report

The Db Console contains a required update:
APTENDERS Key Revision (7.0.011)

- Added an optional Location selector to the AP Inquiry feature for outputs that do not combine POs or Vendor Invoices.

- The Void Payment function in vendor Payables now refuses to proceed if the AP Payment entry has no JEID, noting Cannot Void AP Payment that has no Journal Entry.

- Fixed: 7.0.001 broke the commit of "No Checks Printed" option for the AP Pay Now by Check process.

- Fixed: 7.0.006 introduced a bug in AP Pay Now by Check or EFT that caused a focus error upon completion of the payment.

- The JE Line Date of a Non-System Journal Entry can now only be changed by super user administrators, and when a normal user changes the overall Journal Entry Date of a non-system journal entry they no longer have an option to not change the dates of the JE Lines, they can either accept the new date for all lines or cancel.
JE Line Dates of System Journal Entries are still read only as before.

- The Payments list in Vendor Payables now includes columns for the Vendor Invoice (OrderID) and Vendor Reference.

- Fixed: A recent revision made taxes on returns use the wrong sign for the taxed value.

- Fixed: Partial check out (invoicing) of an order using built in taxes lost the tax calculations of remaining open line items.
This fix is in the CommitInvoice database procedure.

- Improved handling of "GL Code Only" Accounts in both account type-in entry and the Ledger Account Selector.

- Improved rejection of partial date range overlaps for Tax Reports:
It is only be valid to merge Tax Report batches if taxes in the existing batch (except AR write-offs) all fall within the date range of the new batch.
In other words, only complete existing batch(es) can be merging into a new batch, thus replacing existing batches completely.

- Added an Adjustments security context in the "Purchase Orders" class near the Transfer Orders context.

- The Journal Entries feature now has a My Recent Journal Entries entry in the Open Journal Entry drop down menu to list the last eight JE opened by the user, or created by their activity in this session.

- Added a pre Post check to Journal Entries to ensure that every day of the JE Dates balances before posting.
This is most useful for a manual or imported journal entry that covers multiple dates, but the logic is applied to all.

- Journal Entry Lines in Trial Balance and Account Inquiry now include a filter box in the upper right that searches Account, Name, Comments, OrderID, and Amount.

- On Customer Order line items, the C.Cost column can now show standard costs instead by activating a new Standard Cost Column menu entry.
To enable this standard cost display, the user must have at least a Read permit for the Cost security context in the Items class of their Access Profile.

- Added a filter for the Item Costing list of location costs that will match any part of the location (number or name) or the various costs and quantity.

- Added a filter for the Receivables list that will match Account, Customer Name (if names are shown), Comments, OrderID, Receivable Amount, or Amount Paid.
Receivables that have amounts set to pay now by the user are exempt from the filter.

- Fixed: Return of a repair unit from Depot referred to obsolete table TRXLOG.

- Fixed: Collecting Job Details in the Jobs window referred to obsolete table TRXIP.

- Job Details now uses the existing analysis of all jobs if less than 10 minutes old,
and if over 10 minutes but less than 12 hours asks the user if they want a refresh.
This saves the user from waiting for a lengthy analysis if nothing significant has changed.

- Fixed: Repeated customer address lookup from an order Ship-To where there are too many addresses to list in the menu lost the customer-specific address search after the first invocation.

- Fixed: Company Setting "Lookup Options" Include agent name in Agent values shown should not apply to outputs of Forms for Orders.

- Tender Account Numbers on Forms for Orders are no longer obscured for tender types beyond ATM.

- Added an Include Unposted JE option to the Income Statement to match the same option in Account Inquiry

- The Trial Balance now offers a Account Location option to summarize by GL Code per Location, ignoring Departments.

- Added a GL Code Account Type flag "GL Code Only" to indicate that when this GL Code is used for an Account the remaining segments are irrelevant and should all be digit 0.
This flag affects the behavior of the Ledger Account selector, and Item Category Accounts assignment of order line items.

- Export of Payments in Vendor Payables now includes the Vendor Invoice OrderID, and Vendor Reference. The context menu now has an entry to view the Vendor Invoice.

- Added an AP Inquiry feature accessible from the Accounts Payable panel on the Welcome window, and from the context menu of the upper sections of the Payables Dashboard.
These quick reports can be selected using the right-click context menu from on the top banner that indicates the current selection:

- The multi-vendor list of payables in the Payables Dashboard is now sorted first by Vendor Name instead of Vendor Number.

- The Ledger Account selector in Trial Balance and Account Inquiry now provide for a trailing % to indicate all accounts that begin with the shorter lead text.

- Journal Entry Line Comments shown in Trial Balance and Account Inquiry now show the Journal Entry Subject when the line comment is blank.

- The Income Statement now offers a By Account Location option that summarizes by GL Code per Location, ignoring Departments.
This output can be compared to the budget if the budget is also broken down by location.

- The Income Statement can now Compare Budget when summarized By Account Type.

- The JE Line Amount of a System Journal Entry can now be changed by super user administrators.

- Improved data Export speed on a shared host with low random write performance storage.

- Fixed: FrontLine did not prevent Approval of a Vendor Invoice that is On Hold,
and should also prevent Approval when the Vendor itself is On Hold if the user does not have an ADD permit for the "Purchase from Vendor On Hold" security context.

- Fixed: When the user changes the date of an open invoice/confirmation/check-in FrontLine should ask for confirmation of a suspicious date spread based on the current date instead of the order placed date.

- The Income Statement now offers a Department selector if departments are used.

- There is now a Mail Log function available from the Order ID title drop down menu in the upper left of an order processing window.

- The Expired Unit Warranties notice upon checking out a service order now uses a condensed format (one line per line item instead of using more white space for reading ease) when there are more than 10 relevant units, and when there are more than 40 line items the list stops after 40 lines with ... and X more.

- Clicking a Due by date invoice footer title on a time-sensitive Vendor Invoice now toggles their displays and inputs to a Discount by date amount instead.

- FrontLine now only puts thousand separators in number column exports for visual outputs like HTML, not for CSV and Spreadsheet output.

- In Order Lookup orders On Hold now include a stop sign icon in the leftmost column.

- Added a Recently Approved Vendor Invoices search to Purchase Order Lookup,
and the Recently Completed search now excludes Vendor Invoices.

- FrontLine now requires a Location to have its Region assigned when there is a list of Regions,
and in the GL Account selector the Region will follow the Location selected unless Region N/A is set.

- FrontLine no longer requires entry of Payment Gateway Company Settings to activate its Square integration when it finds Square keys in LISTVALS from BaseLink,
and can use an Access Token encrypted by BaseLink as indicated by LISTVALS.Attributes=1

- Added an Accounting Options Company Setting to provide an option to use Date Created instead of the default No Preset for Preset Vendor Invoice AP Financial Date

- The Payables Quick Report now includes the Vendor Invoice number, both the OrderID and EntityOrder, and enables the user to view these vendor invoices.

The Db Console contains two required updates:
File: APTENDERS.PayMethod (7.0.001) This has three sections.
Expand LISTVALS.Display (7.0.001)

- Fixed: Journal Entries created for cash-type Customer Invoice Tenders (not deposits) with no Account specified on the tender line should default to the Account specified in "Tender Types" Company Setting before using the Location Cash Account.

- Fixed: The short term Rentals Overdue special Order Lookup should consider the rental order End [Fulfilled] date the Rental Return Due date.

- Fixed: Cancelling Apply ($...) Credit in Payables did not remove entries from APPAYNOW, causing errors later.

- Fixed: The Income Statement did not exclude Corporate Taxes from the Net Income before Taxes subtotal.

- Fixed: The Total Value shown in Inventory Valuation did not multiple the Unit Cost by the Quantity for items received in non-unique chunks of quantity greater than 1.

- When a Ledger Account is retired by adding a hyphen to the beginning of its Account Description, FrontLine now checks if this GL Code is used on open Customers, Vendors, Locations, and Orders, and if so rejects the retirement, notifies the user of the usage counts, and offers to list these affected in a quick report.

- When viewing a Template JE in Journal Entries there is now a drop-down on the Template button up top to list the last 24 Journal Entries created from this template.

- The Show Usage function in the Reports window is now available for the signature Ormandy login.

- Added a History Order Type flag to mark orders that should be ignored by some lookups.
In this release the "POs Checked In with no AP Invoice" search ignores purchase orders marked with this flag.

- Implemented a new Line Item Change Log. Note that the old change log data in the database has to be converted to show up.
Log entries where a user took over an order In Use are highlighted in yellow.
Order entry and purchasing are not available if the TRXLOG table is still in the database.

- Vendor Invoices now display the Invoice date in gray italics as the default Financial Date when no financial date is entered.
This discloses the "New Payables" revision made in 6.8.065

- Locations now have a Publish Folder. FrontLine expects the Publish Folder to contain folders named for designated purposes.
For example, a location has a Publish Folder that contains an Estimate folder and the user produces an output from Forms for Orders using a form that has "Estimate" in its name, FrontLine will ask the user if they want to publish the document they produced, and if so then FrontLine will place a PDF of the document produced in that folder named EntityID_OrderID_InvSeq_FormName.pdf

Note that the line item consolidation necessitates breaking changes.

The Db Console contains eight required updates:
LOCATIONS.PublishFolder
File: v7 Line Item Table Merge Apply this one first. This is a multi-step script that requires close attention.
File: NewInvoice v7
File: CommitInvoice v7
File: CostInvoice v7
File: CopyLineItems v7
File: GetTaxes v7
File: v7 Line Log Conversion This has multiple sections.

Release: February 24, 2023

FrontLine 6.8.075

- Fixed: Refresh of a Bank Reconciliation could raise a key violation error and subsequently ignore those new journal entries.

- Fixed: The Shipping charge line item added for Shipments did not force the Item Category Accounts of the Shipping Charge to set the accounts of line item added.

- Fixed: Landing Cost was not spread (divided) correctly among multiple units received on the same line item.
This fix is in the CostInvoice db procedure.

- The date produced and company name label "IncomeStatementTitle2" on the Income Statement form is now optional, but a notice is displayed when it is missing due to potential license violation.

- PRICELEVELS.PriceLevel=0 is now the only key value for Period Pricing of rentals, so negative PriceLevel can be used for special cases like Shopify.

- Added a Separate Credits from Debits option to the journal entries listing Account Inquiry that is initially turned on by default for and cash account.

- Added a LastPaid output to the Tax Report that is when the cash tender was collected (typically the invoice date) or when a payment was last received on the receivable.

- Added a What If... Price and Margin feature to Line Item Details for items that have a Unit Cost identifier value.
Here the user can enter values for Price, Margin, and Margin % while the other two values instantly reflect the entered value, using the Unit Cost value of the unit for sale.
This feature is opened when the user clicks in the Unit Cost Identifier Name where a balance scale is shown, or clicks the unit cost value itself while holding down the Ctrl key.

The Db Console contains a required update:
File: CostInvoice v6.8.075 This supersedes and replaces the 6.8.074 revision.

Release: February 14, 2023

FrontLine 6.8.074

- Fixed: The Service Order notice of unit Warranty expiration at invoicing (introduced in 6.8.073) did not appear when the warranty expiration was on the same day that the service order was entered.

- Fixed: FrontLine erroneously claimed that "This write-off was made along with a payment..." when attempting to Unapply an independent Write-Off applied in customer Receivables (AR).

- Fixed: FrontLine should allow the fixed identifiers (like Serial Number) of an unidentified Return unit to be set and changed during the return. When this was broken is uncertain.

- Fixed: FrontLine did not Reverse Journal Entries when customer Receivables (AR) independent Write-Offs were discarded to zero.

- Fixed: In some situations, changing a customer order bill-to right after changing a line item price reverted that price change.

- Added to Company Setting Return, Repair, and Unidentified Options an option "Lines added to a Service Order with a single Repair Unit are automatically assigned to the Repair" to opt in to the auto-assignment of repair parts and services to a single equipment repair order feature introduced in 6.8.073

- Added a Unit Cost system identifier that FrontLine assigns to identifiable inventory Received whose Costing method is Unit (Actual), and uses for the Costing of Customer Invoices.
Unit Cost identifier values cannot be changed by the user.

- Payables Quick Reports now prompt for an End Date, and are now also available from the Summary section of the Payables window.

- Receiving a Special Purchase line no longer auto-commits to the linked customer order line if the special order flag has been removed from the customer order line.

- When the user specifies a range of check numbers to print in the Pay by Checks function of Payables that overlaps with Checks Already Used from that account, FrontLine now offers to show these in a quick report.

- Added an informational confirmation message before Quoting or Voiding a Special Purchase line item because these cannot be undone.

- A missing Payables (AP) account in Vendors maintenance is now highlighted for a Card Issuer and FrontLine refuses to save it.

- When FrontLine makes a local copy of itself from a shared folder launch, it now also copies the backdrop image files.

The Db Console contains two required updates:
File: CostInvoice v6.8.074
IX_AR_ApplyTo v6.8.074

Release: January 24, 2023

FrontLine 6.8.073

- Fixed: Users should not be able to change the header values of an unposted system generated Journal Entry

- The GL Account column display value of order payment tenders now includes the GL Code Description.

- Designating a Journal Entry as a Template now causes it to show up on the New Journal Entry from Template list right away without having to leave the template.

- To streamline addition of repair parts and services to a single equipment repair order, when a line that is eligible to be used for repairs is added to a Service Order that has only one repair unit FrontLine now assigns this new line item as used for the repair of that single repair unit instead of showing a repair assignment menu for the user to decide whether to assign it.

- Before invoicing a Service Order FrontLine now checks if the Warranty of any of the Repair Units has expired since that unit was placed on the order.
If it finds any, it lists the line number(s) and expiration date(s) and gives the user an opportunity to stop before creating an invoice.

- The Form 1099 Payments Summary quick report now includes a VendorID column to enable a quick link to Vendor maintenance.

- Added an Aged Payables Quick Report quick report to the context menu of Account Inquiry

Release: January 17, 2023

FrontLine 6.8.072

- Fixed: FrontLine should reveal the Clearing Account on Line Item Details of Intangibles on Purchase Orders and Vendor Invoices.

- Fixed: Unposted system generated Journal Entries should not allow the user to change the JE Date of the journal entry lines.

- Added a 9 Month option for Bill Frequency

- Added a missing Depreciation Intent, available for manual Journal Entries.

- The Form 1099 Payments Summary quick report now offers to output a specific year. It can still output all years.

Release: January 13, 2023

FrontLine 6.8.071

- The Fiscal Year drop-down selection list now shows the most recent year first.

- Order Status On Hold no longer inhibits import of Mobile Connect (MC) line items.

- Removed the text color and bold highlight on the Prior Retained Earnings and Current Retained Earnings rows near the bottom of the Balance Sheet

- When a Check or Cash customer order tender is Collected prior to invoicing, FrontLine now asks for the date when it was received, assigns that date to PAYMENTS.Captured, and uses that date for the customer deposit Journal Entry

Release: January 11, 2023

FrontLine 6.8.070

- Fixed: Bank Reconciliation could list Cancelled AP Payments using the wrong sign.

- FrontLine now uses the Retainage percentage value set on an order (or the order's job) to split On Account tenders and the corresponding Receivables into the fractions of the regular receivable and retainage amount. This split occurs after the user confirms the On Account tender and before it is posted to AR and JE.
The Due Date of the retainage receivable is set to the Job End date, or one year from the Invoice date if there is no job end date.
Note that there is a new Retainage security context in the "Customer Orders" class near the Bank Deposits context.

Release: January 5, 2023

FrontLine 6.8.069

- Fixed: Receivables did not allow Application of Credits that were partially written off, and other bugs related to the 6.8 AR sign change.

- Fixed: Pay Now by could miss the AP and JE targets when a long Confirmation Code was used.

- Assigning the Non-AR Customer (designated in Company Settings) to a customer order now automatically makes the order a Non-AR order.

- Order Discount is no longer available in Purchasing.

Release: December 23, 2022

FrontLine 6.8.068

- Fixed: FrontLine did not handle Payments on Non-AR customer orders correctly.
These Payments should not invoke the customer Receivables list, and should not be applied to AR upon completion of the order.

- The Trial Balance now notifies the user when there are X unposted Journal Entries excluded, and provides a new context menu function to Show All Unposted JE lines below.
Trial Balance account lines that excluded Unposted JE are marked with an open book symbol in the Account column.

Release: December 19, 2022

FrontLine 6.8.067

- Fixed: Journal Entries for Vendor Invoice Cancellations were neither Posted nor linked to the Cancellation Order.

- The Price Levels view embedded within Items maintenance now uses location-specific costs at the workstation location to show percentage Price Type calculations of Price instead of the generic standard "Cost" seen directly in Items maintenance. (same as in 6.7.066)

Release: December 13, 2022

FrontLine 6.8.066

- Fixed: After a Refresh to add new entries within the period of a Bank Drawer Reconciliation the GL Amount of the "Ending Balance" did not reflect the added entries.

- Fixed: The built-in Tax Report omitted partially invoiced line items from output until those line items were completed in customer order processing.

- The context menu in Account Inquiry now has a Payables function to show vendor payables outstanding at the end of the selected period.

- The Payables function Commit Application of Credit should prompt for an Applied Date override even when there were no Write-Offs.

- Payables can now Pay by EFT when only Write-Offs are taken from the Select for Payment list.
In this case the Confirmation Code is a Write-Off Reason for the AP entry.

Release: December 5, 2022

FrontLine 6.8.065

- Fixed: The actual dates displayed in the Period Date columns of Account Inquiry had the years reversed from the 6.8.064 revision.

- New Payables now have FinancialDate set to the Vendor Invoice "Invoice" date if no explicit "Financial Date" was set on the Vendor Invoice.

- AP Payments now have Invoiced date set to the Invoiced date of the Payable they are applied to.

- Retainage background development has begun but is not yet usable.
However, a database update is required for a new column in tables JOBS and ORDERS.

The Db Console contains a required update:
Retainage (6.8.065)

Release: November 30, 2022

FrontLine 6.8.064

- Fixed: Costing intangible components of a Work Order Assembly check in should use the Price (Cost) entered on the line item itself.

- Fixed: Journal Entries for Work Orders and Vendor RAs should use Costing values instead of costs entered directly on the line items.

- Fixed: Journal Entry creation for Payment of Payables did not set APTENDERS.JEID so Bank Reconciliation could not determine Check Numbers.

- In Account Inquiry the financial year columns are now reversed.
The current year is now first, followed by the prior year, and finally two years prior.

- Added an 11 Month option for Bill Frequency

- Added a Sort by Comments option to Bank Reconciliation

- The Balance Sheet now offers a By Full GL Account option.

- Added an Export function to the context menu of the Journal Entry Lines of Account Inquiry.

- Added to Company Setting Order Activity Reactions an option Do Not Auto-Assign Order Contacts

The Db Console contains a required update:
File: CostInvoice v6.8.064

Release: November 15, 2022

FrontLine 6.8.063

- Fixed: Subsequent Customer Invoices on the same line item would value the Journal Entry lines for Inventory and Cost of Sales including the preceeding invoices of this same order line item.

- Fixed: A recent revision broke the Cash Drawers Report to forms output with an error about PrintCondition.

- Cash Drawer Reconciliation can now provide Details about all tender types, not only Cash and Checks.

Release: November 11, 2022

FrontLine 6.8.062

- Fixed: The Card Refunds -- Add Tagged Return function on the context menu of customer return order tenders should copy the TransId for Square refunds.

- Account Inquiry now has an option to Include Unposted JE instead of including them by default.
Unposted Journal Entries in the list of JE Lines below are marked with the open book icon on the right side of the Account column, and counted in the title of that list when present.

- Added a special admin user login scheme where the login name begins with two underscores.
These special logins must be created in the database management system, where they must be granted appropriate security access.
They have separate passwords, are not considered FrontLine users, and do not appear in FrontLine System Users,
but must correspond to a normal FrontLine user name without the underscores.
For example, special admin user __john must have a corresponding normal FrontLine user john to log on to FrontLine.

Release: November 8, 2022

FrontLine 6.8.061

- Fixed: FrontLine should allow posting Bank Reconciliation Journal Entries where all the JE Lines are zero value.

- Fixed: In the Payables feature the new type-in filter for the Vendor List did not work when the Summary was By Due Date.

- While viewing results in Equipment Search when the highlighter is moved to the Description column FrontLine now removes most other columns so that only the Stock, Description, the first Identifier column, and Customer/Vendor Name columns remain, and the Description column is widened the most.

- The Location column in the Available Inventory view of the Scan Match window no longer adds the Location ExtRef if the Description begins with that same text.

Release: October 24, 2022

FrontLine 6.8.060

- FrontLine should not allow the user to set the quantity of a line on Vendor Invoice that was created from a PO greater than the quantity declared when the Vendor Invoice was created.

- The Purchasing & Receiving link in the Welcome window is now POs, Receiving, AP Invoices instead.

- In the Payables feature there is a new type-in filter for the Vendor List to search the Vendor Name and Vendor Number,
and a type-in filter is now available for the All Payments view to search the Account, Amount, and Comments of payments.

- Recurring Billing Output now has a sticky option (that is on by default and has been the standard for a long time) to Output Units Covered by Contracts
This effectively enables removal of those contract coverage details.

- Customer Order Lookup has a new special Search By entry Open Account Payments

Release: October 18, 2022

FrontLine 6.8.059

- Fixed: Canadian sites could not create a Vendor Invoice for a Card Issuer.

- Fixed: The special Search By entry POs Checked In with no AP Invoice in Purchase Order Lookup should exclude Transfer Orders and Work Orders.

- Fixed: When a positive partial invoice was tendered On Account, then a subsequent negative partial invoice is checked out,
FrontLine should turn the positive open On Account tender line into a split positive and negative, to send the credit to AR.

- Bank Reconciliation now shows the GL Codes of the Accounts along with the descriptions in the menus and header.

- The Income Statement now offers a By Full Account option.
Note that this output cannot be compared to a budget due to granularity differences.

- Added an optional Customer vs Purchasing discriminator to Tax Report batch creation. This is primarily for Canadian sites.

Release: October 5, 2022

FrontLine 6.8.058

- The Income Statement now has inclusive options to:

Show Prior Year the original view with prior year values and variances.
Compare Budget to compare the selected Period and YTD to the budget.

Budget values are available to compare on the Income Statement when all these conditions are met:

The Income Statement is By Account Code
A defined Accounting Period is selected for the income statement, not a custom date range.
A Budget exists for the selected Period.

The Db Console contains an update to add PGID to CUSTOMERS and LOCATIONS for upcoming SquareUp revisions in cooperation with BaseLink and CP:
Payment Gateway ID (6.8.058)

Release: September 29, 2022

FrontLine 6.8.057

- Added Account Type "Revenues - Goods Sold" and "Revenues - Services Rendered" for Ledger Accounts (GL Codes) to refine the Income Statement.

- Ledger Account drop-down lists now have GL Codes preceeding the Description texts.

- The Income Statement now has Variance columns for the Period and YTD,
and can now show Journal Entries for open accounting periods, custom inquiry (Other) periods, and YTD periods.

- Journal Entries shown below "Account Inquiry" and "Trial Balance" inquiries now include a column for the GL Account itself.

- The Assigned Price special identifier is now available in Line Item Details for applicable Adjustment-In and Customer Return units.

- Equipment Search now has a Detail view toggle to show more equipment and entity information in selectable text with more space up top.

- Lookups now have a Starts with option for combined field searches to disable the recently introduced feature to search for terms within the multi-column texts.

- A right-click on the Cancel button in Item Action prompt now offers to Reset the user's item action counters.
The Item Action Counters are used to preselect a default Item Action for the Enter key or Spacebar.

The Db Console contains a required update for MSSQL:
PK_LISTVALS update (6.8.057)

Release: September 12, 2022

FrontLine 6.8.056

- Fixed: The Location GL field of Locations maintenance was missing a security context.

- Fixed: When a Location GL is changed in Locations maintenance, any accounts set on that location
(AR, Cash, Deposits, Discount, AP, AP Discount, Tax Payable, Bank Fees)
that have a non-0000 location segment are now updated to use this new GL segment value.

- Added Labels entries for "Current Retained Earnings" and "Prior Retained Earnings" to enable customization of these row labels in the Balance Sheet and Trial Balance outputs.

- The Income Statement and Trial Balance now provide an (Other) selection in the Period drop-down list for a custom date range.
F2 is a shortcut to this selection.

- Account Inquiry now includes an optional Location selector.

- Added an Import Journal Entry feature.

The Db Console contains a required update:
Expand SUINFO.KeyName (6.8.056)

Release: August 26, 2022

FrontLine 6.8.055

- Fixed: The ellipsis function for the GL Account column in Receivables was missing while F3 worked to invoke the GL Account selector.

- When attempting to Cancel a Vendor Invoice, instead of simply informing the user of payments made towards the payable FrontLine will no longer allow cancellation until the applied AP credits add up to zero.

Release: August 23, 2022

FrontLine 6.8.054

- Includes the fix from 6.7.054

- Fixed: In some circumstances the Trial Balance end value failed to subtract Prior Retained Earnings resulting in a non-zero balance.

- Ledger Accounts (GL Codes) of Unknown Account Type found at logon are now listed after the account issues count message.
This message can be copied to the clipboard for later reference.

- In the Journal Entries function:

Expired JE Templates are now disabled on the list and labelled as such.
Exposed the F2 function in the top menu as Open Journal Entry by JEID
Changing the JE Date in the top section now offers to apply this date as the JE Date of all the JE Lines.
Holding down the Ctrl key while clicking a template entry from the New Journal Entry from Template list now opens the template itself.

- The Payables filter text is now also matched to the PO#, Amount, and Discounted Amount.

- In Reports the Balance Sheet and Income Statement built-in report templates are now excluded from the "Add All" and template file selection list.

Release: August 15, 2022

FrontLine 6.8.053

- Improvements to the new EMail Statements in Receivable Statements and includes fixes from 6.7.052 and 6.7.053

Release: August 5, 2022

FrontLine 6.8.052

- Receivable Statements now offers an EMail Statements interactive function in the context menu to send qualified statements by email.
Email template files can be used to auto-generate the email subject and message body using <FLF> placeholders to insert information for the particular statement.
ReceivableStatements*.eml templates are sought when the function is invoked, where the * wildcard allows for a numeric addition to the file name to indicate that this template should be used for statements that are at least that many days past due. For example, if these files are found:
ReceivableStatements.eml
ReceivableStatements30.eml
then the second template is only used for statements where the maximum past due is at least 30 days.

The number of digits after ReceivableStatements in the file name should be consistent, so for example, to have >=60 day and >=120 day distinct templates the files should be named:
ReceivableStatements.eml
ReceivableStatements060.eml
ReceivableStatements120.eml

- Bank Reconciliation now provides a Bank Ending Balance minus calculated Ending Balance Difference display in the top section.

- Recurring AP now refreshes its list of candidate invoices after a Template is modified within this feature.

Release: July 29, 2022

FrontLine 6.8.051

- FrontLine Shipping now records the OrderID in the SHIPMENTS table when option Order Combination is NOT used.
The OrderID column must be added to the SHIPMENTS table.
Note that this is the same revision as in 6.7.051

The Db Console contains a required update:
SHIPMENTS.OrderID (6.8.051)

Release: July 27, 2022

FrontLine 6.8.050

- Fixed: When an Assigned Price unit was committed to an existing sale line item with a different price the line item taxes were not recalculated.

- Equipment Search now has a Search On Hand Inventory option that includes a Location filter.
Equipment Search can now be opened from Order processing using the line item context menu.
Search On Hand Inventory removes address columns and replaces Customer with Vendor for both search input and output.
When invoked from an order, the Search On Hand Inventory option is preselected and the order line location preset in the Location filter.

- Added ItemCat and TaxCat to the outputs of Forms for Orders.

Release: July 18, 2022

FrontLine 6.8.049

- Budgets feature is now available when the database contains the BUDGETS table.

- Purchase Freight Charges that are assigned to a specific tangible line item on a purchase order no longer display a ready checkbox because they are checked in along with their associated tangible line item.

- Equipment Search now:

Adds a trailing wildcard % to search values if the user doesn't specify one, except for customer number and country.
Adds a leading wildcard (to search anywhere within the identifier value) for identifiers that are multi-value.
Includes Assigned Price in the identifier type selector drop-down.

Release: June 28, 2022

FrontLine 6.8.048

- Pay Now by Check now allows prior check numbers that have been skipped to be printed.
FrontLine verifies that the begin check number and number of checks to be printed fit in a skipped checks range.

Release: June 24, 2022

FrontLine 6.8.047

- Fixed: Some bugs in the SquareUp integration.

- Fixed: The default GL Account for an order payment tender (shown in italics) should appear as soon as the user sets the tender type.

- Fixed: Recurring AP should not create a new invoice for a series when the last invoice created has not been committed, those shown when the "Show Pending" option is enabled.

- Manual Journal Entries now only allow one of these five JE Types to be selected: Payroll, Depreciation, Miscellaneous, Accrual, Beginning Balance
and only these six JE Intents are offered for manual JE Lines: Miscellaneous, Payroll, Miscellaneous Accrual, Miscellaneous Accrual Reversal, Payroll Accrual, Payroll Accrual Reversal

- In Recurring AP a right click on Show Due within the Next Week changes it to Show Due within the Next 30 Days.

- Payables listed for multiple vendors together in the Select for Payment list are now sorted by Vendor Number before Due Date.

- In Pay Now by Check/EFT/Card the Account selected is now sticky per user and per Check/EFT/Card.
Important: The sticky Items Per Stub value for check printing has to be set by the user once more.

- Added an Export function to the context menu of Bank Reconciliation.

- The New Bank Deposit Batch function invoked in the customer orders window now provides the GL Account selector for the user to choose a bank account.

- The context menu available in the Generate Purchase Order window now offers three quick reports. It is not necessary to select a Vendor or create purchase suggestions to use these:
View On Order by Location for Items On Order by Location
View On Order by Stock Number for Items On Order by Stock Number
View All On Order by PO for Items On Order by Purchase Order

Release: June 15, 2022

FrontLine 6.8.046

- Fixed: Vendor Invoices now assigns the item category account for AP Discrepancy to the line item COS account to be used for Journal Entry creation from Vendor Invoices.

- Fixed: The AR Total and Overdue display introduced in 6.8.041 miscalculated dues when payments were made by a different customer.

- Fixed: The optional Account selector for Receivable Statements should be a GL Code instead of a complete Account.

- Fixed: In addition to POs, FrontLine should check for AP entries before allowing a Vendor to be deleted.

- Fixed: Part of a revision made in 6.8.039 caused Rental Reservations to crash FrontLine.

- Fixed: In the Bank Deposits window New Deposits created (with no related orders) were not saved.

- Fixed: FrontLine now creates a Customer Tender Removal Journal Entry for customer cash tenders removed after prior acceptance.
The original invoice date (if there is one) is used for the JE Date, if that period is closed then FrontLine does not auto-post the JE.
When a user who has an ADD permit to Journal Entries right clicks a tender removal line that is missing the JE (on a customer order) FrontLine presents the Journal Entries context menu entry to enable the user to create these missing JE after a confirmation prompt.

- During a manual Journal Entry, after the user selects an Intent for a JE line the subsequent JE lines entered during that session are presumed to be of that same Intent if the user does not explicitly select another Intent.

- When a Journal Entry that was created from a template is posted, the JE Date of this new Journal Entry is saved as the last date used on the template.
When the next Journal Entry is created from this template FrontLine can use this date as a base for the Date interval to add instead of the original JE Date of the template itself, but asks the user to confirm which base date to use.

- When an Income Statement is produced "By Account Code" the value in a Period column can be double-clicked (or the context menu used) to view the Period Journal Entries for that Account in that Period if the period is closed.

- Export of the Payables list now includes Terms (of the payable) and Vendor Number.

- When viewing committed Invoices (CheckOuts) FrontLine now shows the On Account amount with Terms discounted dates and amounts due.

- Added SquareUp card tender processing capabilities, using the Square Terminal as the entry point for customer credit cards.
To activate SquareUp features:

In the Payment Gateway Keys entry "API Key" of FrontLine Company Settings enter SquareUp followed by the "Application ID" used for this merchant.
For the "API Secret" enter the Merchant's Access Token (typically 64 characters) found in the merchant's Square account management in a web browser.
FrontLine 6.8.050+ relies on BaseLink to generate the Access Token, so just paste SquareUp 8 times here to fill 64 characters.
In the Payment Gateway Merchant entry "Merchant (Location) ID" of FrontLine Company Settings enter the Square Location ID (typically 13 characters) to be used as a default location shown in the merchant's Square account management in a web browser, as seen in the "Locations" section.
Square Location IDs should also be used in FrontLine Locations Payment Gateway Merchant entries to map the merchant's Square locations to FrontLine locations.
The same Square Location ID can be used in more than one FrontLine location, like for a Rental and Non-Rental at the same site.
"Token" and "Tokenization Key" are not required for SquareUp. Paste SquareUp six times to fill in the Token.
When FrontLine detects SquareUp in the API Key of the Payment Gateway Keys a new button SquareUp Terminals appears just below the WorkStation List in FrontLine Setup.
This opens a SquareUp Terminals window where square terminals are identified to be in a FrontLine Location and are Paired to the FrontLine application by their Serial Number.
FrontLine provides instructional prompts for the functions in its SquareUp Terminals window.
Note that while the card chip (dip) reader is at the base of the Terminal, the contactless (tap) sensor is near the middle of the Terminal.

- Customer Order Lookup has a new special Search By entry Card Tenders Pending to list orders with card tenders that have been authorized but not yet captured.
Such payment tender lines have their Verify Code shown in yellow and include PAYMENTS.VerifyCode flag value 16384.
For these card tenders the context menu has an options to:

Capture Authorized Payment. Note that Square authorizations typically expire in 36 hours, so the capture may fail.
CANCEL Authorized Payment for payments that have been authorized ahead of invoices on an open order.

- Includes fixes and feature added in 6.7.050

Be sure to apply these updates in the Db Console:
Expand PAYMENTS.TransID (6.8.046)
PAYMENTS.CaptureBy (6.8.046)
File: CopyLineItems v6.8

Release: March 30, 2022

FrontLine 6.8.045

- Fixed: Committing a Physical Count with added inventory could raise an SQL error.

- Fixed: FrontLine did not ensure that a Vendor Invoice had a Pay-To address assigned when the user Approved it as Payable.

- Fixed: Customer orders that are assigned to a Bank Deposit should journal (JE) cash received to that Bank Account (GL Code) instead of the Order Location Cash Account as it does when no bank deposit is specified.

- Includes fixes and feature added in 6.7.049

Release: March 16, 2022

FrontLine 6.8.044

- When the Income Statement is produced "By Account Code" it now has a "Show Accounts with Zero Ending Balance" option.
By default, account detail rows with zero in all four output columns are not shown.

- A visual report of the Income Statement is now available from the context menu.
It uses a form IncomeStatement.rep with explicitly named expressions so that FrontLine can perform additional visual manipulations at runtime.

- FrontLine has begun to log user actions to Void an order, and turn an order into a Quote and vice versa. There is no output of this log information yet.

- WEBPARTS with NULL Quantity again qualify for import as Quantity 1, as in 6.7

- Includes fixes and feature added in 6.7.048

Release: February 24, 2022

FrontLine 6.8.042

- Fixed: The last revision broke clicks on checkboxes within grid lines.

- Fixed: Import of BaseLink data was broken by GL revisions.

- Added JobCode to the Invoice output of Forms for Orders. This is the job code of the line item, which is the job code of the order unless the line item is explicitly assigned to a different job.

- A visual report of the Balance Sheet is now available from the context menu.
It uses a form BalanceSheet.rep with explicitly named expressions so that FrontLine can perform additional visual manipulations at runtime.

- Includes fixes and features added in 6.7.047

Release: February 11, 2022

FrontLine 6.8.041

- Fixed: When checking for Accounting Period Closure before accepting a Vendor Invoice FrontLine should use the Invoice Date [Placed] before the posting date if the user entered no Financial Date [Fulfilled] thus matching the JE Date used for posting the journal entries.

- Fixed: Starting a Vendor Invoice with a vendor already assigned to a blank PO, then choosing Enter Invoice without PO from the New Vendor Invoice window now preserves that prior assigned vendor instead of opening Vendor Lookup.

- Fixed: Recurring AP began to lose the OrderType flags on the generated invoice.

- Display of GL Codes for Item Category Accounts in Lists is more consistent with the GL Account selector, and the input accepts both GL Codes and fragments of their descriptions.

- Customer Orders now show an AR Total and Overdue (if any) to the left of the Bill-To address section.

- Includes fixes and features added in 6.7.046

Release: January 27, 2022

FrontLine 6.8.040

- Fixed: When a Vendor Invoice is Cancelled, and the cancellation (return invoice) is Approved, the original vendor invoice is now marked as Cancelled in OrderStatus so that the New Vendor Invoice feature can ignore it.

- For a system administrator, the custom Reports window now has a Show Usage function to produce a quick report of Reports Usage since FrontLine began to log custom report execution.

- Includes fixes and features added in 6.7.045

Be sure to apply the updates:
Expand LOCATIONS.MailRelay (6.8.028)
File: NewInvoice v6.7.045 (Same as in 6.7.045)

Release: January 5, 2022

FrontLine 6.8.039 Ledger Accounts Conversion beta

- Fixed: Voiding an AP Cash Tender (Void Payment) should allow backdates to the Applied date of the cash tender instead of the Issued date.

- Includes features added in 6.7.044

The Db Console contains a required update:
Expand ITEMS.Desc1 (6.8.039)
(This is the same column expansion as in 6.7.044)

Release: December 16, 2021

FrontLine 6.8.038 Ledger Accounts Conversion beta

- Non-Miscellaneous Manual Journal Entries no longer apply a default History JE Intent. If the JE Intent for the line is left blank then the intent list is shown for the user to choose from.

- Added a Cancel feature for Approved Vendor Invoices that creates a reversal vendor invoice. If the Cancellation is Approved then reversals are created in AP and Journal Entries.

- Added a basic Form 1099 Payments Summary quick report to the GL group of the Welcome window.
All years of 1099 payments are output, sorted by year then vendor name.

- Includes features added in 6.7.043

Release: December 7, 2021

FrontLine 6.8.037 Ledger Accounts Conversion beta

- Fixed: Committing a Recurring Bill Credit caused an SQL error since 6.8

- Fixes in the new Recurring AP feature.

- A new Refresh function is now available in the context menu of an open Bank Reconciliation that attempts to add journal entries within the reconciliation period that were not there when the reconciliation was created. Note that changes to Bank Deposits should be handled by opening the bank deposit from within Bank Reconciliation.

- In the Accounting Periods feature, added an ability to close AP and AR before closing the period completely. These partial closures are checked at:
AP Payments, Write-Offs and Write-Off Cancellations,
AR Write-Offs and Tax Write-Offs,
Issued date of Recurring Bills,
Vendor Invoice and Customer Invoice Commits.
Note that Journal Entries created by special functions in the Db Console may not check for closed periods.

The Db Console contains a required update:
APERIODS AP and AR Closures (6.8.037)

Release: November 28, 2021

FrontLine 6.8.036 Ledger Accounts Conversion beta

- Added an optional "Job Code" to Jobs.
Job Codes can be edited in the Jobs window, and are included in the job list text search filter.
If present, Job Codes are included in the Job ID drop-down texts of the customer order window.
The JobCode label can be changed in Label Maintenance.

- Balance Sheet and Income Statement inquiries now have an optional Location specifier.
The financial inquiries (Trial Balance, Balance Sheet, Income Statement) now have a NONE option to analyze only journal entries posted to location code 0000 Non-Specific Location.

- Equipment Sets now have an optional Job ID that flows to Recurring Bills.
Recurring Billing considers a Cancelled or Completed Job an Exception, and allows the user to view the job.

- Added a Recurring AP feature to create Recurring Vendor Invoices from existing Vendor Invoices that are marked as a template for future vendor invoices on a given frequency with optional time limits and recurrence limits. There is a "Recurring AP" security context added to the bottom of the "Purchase Orders" class.

- Includes fixes and features added in 6.7.041 and 6.7.042

The Db Console contains four required updates:
ORDERS.TemplateID (6.8.036)
ORV (New in 6.8.036)
ESETS.JobID (6.8.036)
JOBS.JobCode (6.8.036)

Release: November 12, 2021

FrontLine 6.8.035 Ledger Accounts Conversion beta

- Fixed: A recent revision broke disabling Tender Types in Company Settings.

- Fixed: A recent revision broke the Account Description display in Journal Entries.

- Added a "Miscellaneous" Journal Entry Intent that is now the default line intent for Miscellaneous Journal Entries.

- Includes fixes and features added in 6.7.040

Release: October 26, 2021

FrontLine 6.8.034 Ledger Accounts Conversion beta

- Fixed: Package Recall was broken by the GL conversion if the old columns had been cleaned out.

- Fixed: Creation of the shipping charge line after Shipping was broken by the GL conversion.

- Fixed: Copy of Item Category Accounts in Lists was broken by the GL conversion.

- Includes fix and feature added in 6.7.039

- HTML Export has an improved tabular format.

- FrontLine can now map single addresses in the browser without a Company Map API Key.

- Committed Bank Reconciliations now keep entries that were left blank because they were not on the bank statement.
These entries reappear on the next bank reconciliation as they did before.

Release: October 8, 2021

FrontLine 6.8.033 Ledger Accounts Conversion beta

- Fixed: Fiscal Year of Accounting Periods should correspond to the calendar year of the end of fiscal year.
This affects sites that use fiscal years that do not end on December 31.

- Fixed: Fixes made in 6.7 through 6.7.038 were added in this release.
Be sure to apply the CostInvoice v6.7.038 stored procedure update.

- Added Account Type "Corporate Taxes" for Ledger Accounts (GL Codes)

- The AP function to Void Payment in the Payables window now asks for an optional override Void Date that is recorded in AP.Applied and flows to JE.JEDate

- Financials now include an Income Statement inquiry.
Account Types of Ledger Accounts (GL Codes) must be set correctly for the Income Statement to make sense.

Note that FrontLine has begun to use some SQL that requires SQL Server 2016 or newer.

Release: September 16, 2021

FrontLine 6.8.032 Ledger Accounts Conversion beta

- Fixed: Fixes made in 6.7.035 were added to 6.8 in this release.

- Fixed: Journal Entry lines were not created for Warranty Vendor Invoices.

- Financials now include a Balance Sheet inquiry.
Account Types of Ledger Accounts (GL Codes) must be set correctly.
The Balance Sheet can be produced By Account Type (the default shorter summary) or by By Account.
Some new account types have been added (Other Current Assets, Intangible Assets, Taxes Payable, Other Current Liabilities) and some account type attributes changed.

Release: August 24, 2021

FrontLine 6.8.031 Ledger Accounts Conversion beta

- Fixed: A recent revision introduced an SQL error when check numbers were skipped in Pay Now by Check.

- Fixed: The (Paid) indicator did not appear on customer order On Account tenders whose receivables had been paid.

- AP Check output now consolidates both the vendor's Name1 and Name2 into the PayToName output, and includes [APInvRef] the vendor's default AP Invoice Reference.

- Worded number output of AP Check values now includes 00/100 when there are no cents.

- MOL Third Party Export produces a new column output specified by Motorola Solutions.

- Financials now include a Trial Balance inquiry.

Release: August 6, 2021

FrontLine 6.8.029 Ledger Accounts Conversion beta

- Fixed: Journal Entries for Recurring Bills paid by cash put the wrong sign on the cash account line, producing an unbalanced JE.

- Fixed: FrontLine should assign the Location Discount account to an Order Discount line item's Revenue account.

- Fixed: A Vendor Invoice created from a Purchase Order should not copy the PO's Vendor Reference.

- AP Payments Journal Entries now include the payment [Issued] value for Bank Reconciliation.

- MOL Export is revised to Motorola's new specifications.

- Journal Entries and Account Inquiry now show currency values without currency symbols.

- Journal Entries for a Recurring Bill (or Late Fees bill) that lacks a journal entry can now be safely created from the individual bill, and Journal Entry creation from Recurring Billing Output can create JE for either the one bill selected or all bills in the batch that have no JE yet.

Release: July 22, 2021

FrontLine 6.8.028 Ledger Accounts Conversion beta

- Fixed: Receivables "Days Overdue" and "Max Past" were not adjusted for the AR sign changes.

- Fixed: FrontLine did not post Journal Entries for Recurring Bill Credits when the credit was committed.
If the journal entries were later created from Recurring Billing Output then the entire billing batch was reversed.

- Fixed: Journal Entries for Vendor Invoice lines that have no corresponding Purchase Order (PO) should not generate Vendor Invoice Inventory Clearing values, and should generate Vendor Invoice Expense lines instead of Vendor Invoice Discrepancy because there is no PO.

- Bank Reconciliation development along with enhancements to Bank Deposits.

The Db Console contains a required update:
Expand LOCATIONS.MailRelay (6.8.028)

Release: June 15, 2021

FrontLine 6.8.027 Ledger Accounts Conversion beta

- Fixed: Pay Now by Check would output some blank check numbers in some data circumstances.

- AP Payments now notify the user and refuse to complete if the Account selected for "Pay Now by Check" or "Pay Now by EFT" is not a Cash Account.

- The Customers function in Vendors maintenance is now hidden and unavailable unless company setting "Return, Repair, and Unidentified" options include "Invoice Vendors for Warranty Service."

Release: June 3, 2021

FrontLine 6.8.026 Ledger Accounts Conversion beta

- Fixed: When tendering an order On Account the customer's open receivables were incorrectly analyzed.

- Fixed: Fixes made in 6.7.032 were added to 6.8 in this release.

- Because FrontLine does not process cards that are used to pay vendors, the Credit Card field for AP on Vendors now accepts short reference codes, like x1234

Release: May 25, 2021

FrontLine 6.8.025 Ledger Accounts Conversion beta

- Fixed: An assertion error in Inventory Valuation caused by the GL Account revisions.

- Fixed: FrontLine incorrectly added a Vendor Invoice Discrepancy Journal Entry line when a Vendor Invoice was accepted for an Open PO.

- Fixed: The New Vendor Invoice feature now reveals Quantities Ordered, Checked In, and Invoiced in separate columns, and suggests new invoice quantities Checked In minus Invoiced.

- Layout and graphic revisions to the FrontLine Logon window, including removal of the title bar. To move the window click and drag the bridge art on the right or the Ormandy logo in the upper left.

- Diagnostic Reports now have a Journal Entries context menu entry that is enabled when the row has a JEID value and the user has access to journal entries.

Release: May 6, 2021

FrontLine 6.8.024 Ledger Accounts Conversion beta

- Fixed: FrontLine should not change the ID of Ledger Accounts (GL Codes) in Setup Lists.

- Fixed: Journal Entries for subsequent Invoice Taxes included tax values from prior invoices of the same order.

- Fixed: Journal Entries for prepaid (by Collected deposit) or overpaid (ex, by Check for Order Total) invoices consumed all the tender on the first invoice resulting in unbalanced journal entries.

- Fixed: FrontLine should not allow Ledger Accounts (GL Codes) that have been used for Journal Entries to be changed or deleted, only the account description can be revised.

- Fixed: The Summary and Vendor List did not refresh after a payment was made in Payables.

- Fixed: FrontLine should create journal entry lines for AP Discrepancies for Services and Charges.

- Fixed: Late Fee Billing had not been revised for the AR sign changes.

- After voiding an AP Payment in Payables the Posted date of the user's last voided payment is highlighted in pink.

- When Payables are opened for a single vendor, Vendor Credits shown in the Payables feature can now be applied to payables using the new Apply Credit and then Commit Application of Credit functions. The function buttons have been reorganized, and the payables filter text box moved to the far left.

- Added a Ledger Account (GL Code) Type "Inventory" to the "Assets" group.
"Fixed Assets" and "Other Assets" have their attributes values changed to accommodate.
"Equity" moved to the Liabilities group with a corresponding attributes value change.
These changes involve updates to the corresponding LISTVALS [Attributes] values.

Release: April 19, 2021

FrontLine 6.8.023 Ledger Accounts Conversion beta

- Journal Entries are now created (and posted if possible) without user interaction.

- Account Inquiry can now show information for an entire Account Type. Click on the pink account name display in the top section to select from a list of Account Types.

- Vendor Payments shown in the Applied list of Payables can now be voided using the context menu.

Release: April 13, 2021

FrontLine 6.8.022 Ledger Accounts Conversion preview

- Receivables and Payments, as recorded in the AR table, now have Amount values independent of DocType.
Receivables are positive, Payments and Credits are negative.

- The Account Inquiry feature now has three options for the periods sums shown:
"Period Sums" vs "Fiscal Year Sums" (new) vs "Lifetime Sums" (as before is default for assets and liabilities).
After the summary has been produced and shown the user can choose to see sums different from the default.

Release: April 6, 2021

FrontLine 6.8.021 Ledger Accounts Conversion preview

- "Pay Now by Card" and "Pay Now by EFT" now offer a "Pay Date" override to the user. The default value is today.

- "Pay Now by Card" now includes a "Due Date" for the user to indicate the card statement due date for the new card payable.
FrontLine estimates this due date by adding the Card Issuer vendor's Terms (if any) to today.

- Location Ledger Accounts are now validated before first use, and a message shown if any are invalid. This message can be very long when there are many locations.

- Added Report Groups for AP_ (Accounts Payable) and GL_ (General Ledger).

Release: March 30, 2021

FrontLine 6.8.020 Ledger Accounts Conversion preview

- Added an Accounting Periods feature where fiscal year accounting periods can be defined, and periods can be closed.
Journal Entries cannot be posted into a closed period.

- Added an Account Inquiry feature where journal entry lines on individual ledger accounts can be summarized by periods (cumulatively or not, assets and liabilities are cumulative when opened), listed in detail per period, and the complete journal entries that contain them opened.

- Accounting Periods, Account Inquiry, Budgets, and Journal Entries links are now in their own "GL" section on the Welcome window.

- Added a "Beginning Balance" Journal Entry Type.

- AP entries posted for a 1099 Vendor now have a distinct DocType, and if the invoice includes a Reimbursement that value is separated in AP.
These changes enable Payables records to maintain their 1099 characteristics even after a Vendor's 1099 status changes, and simplify extraction of 1099 totals from AP.

- Location display texts (as in the drop-down location selectors) no longer include the location ExtRef unless the location has no Description.

Release: March 11, 2021

FrontLine 6.8.019 Ledger Accounts Conversion preview

- When the GL Account selector shows a subset of GL Codes due to the context, the complete list of GL Codes can be revealed with the new "All" button on the right.

- The GL Account selector now has "N/A" options for Department, Location, and Region.

- Payables can now be opened for a single vendor from Vendor maintenance.

- The Payables features now has:

An Applied option to show payments applied to the selected payable.
An All Payments option to show all payments that have been made to a single vendor.
The All Payments view is only available in context of a single vendor.

- On a Vendor Invoice for a vendor who is marked for a 1099 box, there is now an optional Reimbursement entry field in the lower right of the vendor invoice window.
This requires a [Reimbursement] column to be added the ORDERS table.

FrontLine 6.8.018 Ledger Accounts Conversion preview

- Some system-generated Journal Entry lines now include Comments from the source.

- FrontLine now determines the Transfer From Account during order entry of Transfer Order line items.
The value is stored in the line Clearing (CLR) account, and is shown and available for user changes in Line Item Details.

Release: February 17, 2021

FrontLine 6.8.017 Ledger Accounts Conversion preview

- Enhancements in the Payables window, and the "Pay Now" features now cover "Pay by EFT" and "Pay by Card".

Release: February 5, 2021

FrontLine 6.8.016 Ledger Accounts Conversion preview

- Revisions to the "Pay Now By Check" feature including actual AP Check printing output.

This revision requires a new table APPAYNOW table that will be rolled into the initial 6.8 conversion.

Release: January 28, 2021

FrontLine 6.8.015 Ledger Accounts Conversion preview

- Fixed: FrontLine omitted journal entry details of customer receivable write-offs made while receiving payment from the customer.

- The "Select for Payment" and "Pay by Checks" functions in Payables have been elaborated for more complete functionality, including payable write-offs and Journal Entries.
Actual check printing output is still missing.

Release: January 14, 2021

FrontLine 6.8.014 Ledger Accounts Conversion preview

- The GL Account selector will not Accept GL Codes with a blank Account Description or a Description that begins with a hyphen. This is a means to mark a GL Code as Inactive.

- The "Pay by Checks" function in Payables opens a Pay Now By Check window, and there is a search filter for the Payables list that does partial matches on Name, PO, and Account.

This revision requires a new table APTENDERS table that will be rolled into the initial 6.8 conversion.

Release: December 9, 2020

FrontLine 6.8.013 Ledger Accounts Conversion preview

- Fixed: The GL Account selector did not handle a lack of Regions or Departments well.

- The GL Account selector now reduces the GL Codes listed for some contexts.
For example, for a customer Receivables (AR) account only Asset accounts are listed, and for a GL Distribution (GLD) account on a vendor invoice only Expense accounts are listed.
If no Ledger Accounts in Setup Lists have a relevant Account Type then the GL Code drop-down list will appear empty in the GL Account selector.

- Removed the 1099 flag added to VENDORS in the last revision and replaced it with a new field [F1099] for Form 1099 selection.
A built-in list of current options is included, they will be revised within FrontLine as needed:

0 or null = No 1099
1  = Box 1: Rents
2  = Box 2: Royalties
3  = Box 3: Other income
4  = Box 4: Federal income tax withheld
5  = Box 5: Fishing boat proceeds
6  = Box 6: Medical and health care payments
7  = Box 7: Nonemployee compensation
8  = Box 8: Substitute payments in lieu of dividends or interest
9  = Box 9: Direct sales
10 = Box 10: Crop insurance proceeds
13 = Box 13: Excess golden parachute payments
14 = Box 14: Gross proceeds paid to an attorney

If a vendor requires a 1099 form then FrontLine requires a TaxID for that vendor.

This revision requires an addition to the VENDORS table that will be rolled into the initial 6.8 conversion.

Release: December 4, 2020

FrontLine 6.8.012 Ledger Accounts Conversion preview

- Added an Export function for the detail list in Payables, and improved the "Select for Payment" checkboxes with a hard vs soft selected/unselected to make the "All" toggle more useful.

- The GL Account field label in Customers maintenance is now "Receivables (AR)" by default and the db name is CUSTOMERS.lacAR
The display label can be changed in Label Maintenance under Name lacAR.

- Vendors maintenance now has:

GL Account for Payables (AP) [VENDORS.lacAP] used as an override of the location AP account for Vendor Invoice journal entries. This replaces the previous generic "Account" field.
New GL Account for Expenses (AP) [VENDORS.lacEXP] used as a default expense account for Non-PO Vendor Invoice journal entries.
New 1099 flag (VENDORS.VendStatus value 16) to indicate vendors that require a 1099.

- Added OrderID and ItemCat columns to the Journal Entries list.

- The "Open Order..." context menu entry in Journal Entries now shows the InvSeq when present.

- Integer columns name "JEType" and JEIntent will now be translated to journal entry types and intents in FrontLine reports.
Note that JE.JEType contains both the journal entry type, and the intent of the row.

- In Access Profiles the Entity Order security context (in class Customer Orders) and Vendor Ref security context (in class Purchase Orders) now require "Special" access level to enable a user to reuse a value (for the same customer or vendor) after confirmation.

- Purchase Order Lookup has a new special Search By entry POs Checked In with no AP Invoice
Using "Lookup PO" from the New Vendor Invoice feature now invokes this search by default.

- Vendor Invoices created by "Enter Invoice without PO" from the New Vendor Invoice feature are now considered Non-PO AP Invoices where GL Distribution line items can be created using the "GLD" Scan Code. GL Distribution line items:

Are charges with no ItemID.
Cannot have a zero Cost.
Respond to F3 (Lookup) with the GL Account selector.
Display the expense GL Account (recorded in the line Inventory Account) and Description.
Are journalled as Expenses to the line Inventory Account balanced by Payables to the Vendor's GL Account (if defined) or the Location's AP Account (if no Vendor GL Account).

The Db Console contains a required update:
IX_ORDERS_OrderRef (6.8.012)
This revision also requires changes to the VENDORS table but these are rolled into the initial 6.8 conversion.

Release: November 17, 2020

FrontLine 6.8.011 Ledger Accounts Conversion preview

- Added a Budgets feature to create and manage budgets.

The Db Console contains a required update:
File: BUDGETS (6.8.011)

Release: October 2, 2020

FrontLine 6.8.010 Ledger Accounts Conversion preview

- Journal Entries now has a Template function to make a posted user-generated a template that can be used to create new user-generated journal entries using a New Journal Entry from Template menu entry in the "New" drop-down.
FrontLine offers to offset all the dates of the new journal entry by a user-selected number of Days, Weeks, or Months.

- Posted Journal Entries can now be effectively cancelled using a Reversing Entries function that creates a identical new journal entry with the amounts reversed.
If the journal entry has already been reversed then FrontLine offers to show that reversal.

- Unposted user-generated Journal Entries can now be discarded using the Cancel function.

Release: September 22, 2020

FrontLine 6.8.009 Ledger Accounts Conversion preview

- Journal Entries now has a Reverse function to create reversing accrual entries for "Accrual" and "Payroll" journal entry types.
FrontLine will reverse entries with reversible Intents: Misc Accruals and Payroll Accruals
producing Intents: Misc Accrual Reversals and Payroll Accrual Reversals
for the specified date, which defaults to the first of the next month.

- Fixed: The sum shown in the lower section of Payables.

Release: September 11, 2020

FrontLine 6.8.008 Ledger Accounts Conversion preview

- Journal Entries are now added for Transfers and Work Orders. Third Party POs (for subrentals) are not journalled.

Release: September 9, 2020

FrontLine 6.8.007 Ledger Accounts Conversion preview

- Journal Entries are now added for Adjustments and Physical Count adjustments.

Release: September 1, 2020

FrontLine 6.8.006 Ledger Accounts Conversion preview

- Journal Entries are now added for Receiving check-in and Vendor Invoices.

Release: August 21, 2020

FrontLine 6.8.005 Ledger Accounts Conversion preview

- Enhanced Journal Entries with columns such as the Journal Entry Intent (that is always set for entries created by FrontLine), JE Date, and line Comments.
Journal Entries for Recurring Billing frequencies longer than a month will now consume Unearned Revenue into Income (Revenue) monthly.
FrontLine can only create unearned revenue journal entry lines when the relevant Item Categories have an unearned revenue account indicated in their Item Category Accounts.

Release: July 16, 2020

FrontLine 6.8.004 Ledger Accounts Conversion preview

- Basic Journal Entries are now added for customer invoices, recurring billing batches, and write-offs (including taxes) of Receivables.
The journal entries are shown to the user every time for inspection.

Release: May 26, 2020

FrontLine 6.8.003 Ledger Accounts Conversion preview

- Added a basic Journal Entries feature, available in the Maintenance group of the Welcome window.

Release: April 15, 2020

FrontLine 6.8.002 Ledger Accounts Conversion preview

- Added a Company Setting GL Account Display to abbreviate GL Account displays.
Shortening the GL Account display does not change the 20-character data value.
Any positions omitted by the abbreviation are left-filled with digit 0 (zero) characters.
For example, Location segment "1201" shortened from 6 to 4 positions is recorded as "001201"
Department, Region, Division, and Company segments can be hidden completely by setting their display length to zero.

For output on custom Reports and in the Db Console, FrontLine will format and interpret the 20-character account number for columns named:
- AccountGL with any additional trailing text in the name. Examples: AccountGL or AccountGL2W
- lac with additional trailing text in the name. Examples: lacINV or lacSomeOtherAccount
Both of these column name leads are case sensitive.

Release: March 19, 2020

FrontLine 6.8.001 Ledger Accounts Conversion preview

- Ledger Accounts are now 20-character GL Accounts in all cases except Item Category Accounts where only the 6-digit "GL Code" is entered leaving the rest of the "GL Account" to be determined by the context. In FrontLine the GL Account segments are digits or upper case alphabet characters:

6: GL Code (Account)
2: Department
4: Location
3: Region
3: Division
2: Company

- GL Account segment values must be entered in their respective Lists for Departments and Regions.
Locations have a LocationGL value introduced in 6.8, while Division and Company segments are preset without lists in Company Settings at this time.

- GL Account values can be entered directly where needed, FrontLine then validates the entry and if valid accepts it without further interaction.
Otherwise a new GL Account selector window opens to help users determine the GL Account desired. This window can also be opened explicitly using the F3 key in an applicable field.
Users can enter a leading part of a GL Account (like only the Code segment) before entering the GL Account selector.
If a segment is not included in the user's entry then the GL Account selector window preselects a value for that segment from the context, for example line location, department, etc.

- GL Account values are displayed with hyphens between the segments to improve readability. These hyphens are not saved in the data, and are ignored for GL Account validation.

- FrontLine Workstation StationID values can now be set as high as 1999 instead of 999. Four-digit StationIDs are not recommended until a site has used up the 100-999 range.

Release: February 10, 2020

FrontLine 6.8.000 Ledger Accounts Conversion preview

- Ledger Account columns and values are changed from a smallint reference to a char(6) GL Account segment, with extensive consequences:

The accounts in LISTVALS are transformed (and reduced because per-location accounts are no longer needed) from [LName]='Account' to [LName]='AccountGL' with the 4-character account in [StrValue]
This evolved into [LName]='CodeGL' with the 6-character account in [StrValue]
Database tables replaced are: ITEMCATS becomes ITEMCATA, PTL becomes PTLA.
Database tables modified are: CUSTOMERS, VENDORS, LOCATIONS, AR, PAYMENTS, TRX, TRXIP, TRXLOG, TRXTAX, TRXTAXIP, TAXDTL.
Tables with an [Account] column have a replacement column [AccountGL]
Tables with multiple account columns have replacement columns named with a "lac" prefix meaning "Ledger Account" for example:
- In TRX [AccountREV] is replaced by [lacREV]
- In LOCATIONS [Cash] is replaced by [lacCash]
LOCATIONS table gains a [LocationGL] column for the location segment of the eventual GL Account.

- Many basic features are affected including:

Order Processing - Line Items, Tenders and Tagged Card Refunds, Tax details, MC Import, Returns, Invoicing
AR - Receivables, Receivable Statements
Recurring Billing and Late Fee billing
Built-in and custom Reports
Setup - Lists - Ledger Accounts, Item Category Accounts
Company Setting - Tender Types - Account assignments
Maintenance - Locations, Customers, Vendors, Taxes

The Db Console contains three required updates:
File: GL Accounts Conversion 6.8 Apply this one first. This is a long multi-step script that requires close attention.
File: GetTaxes v6.8
File: CommitInvoice v6.8

- Fixed: The last revision made FrontLine fail to show the default account that will be assigned when a cash tender is collected if the user doesn't explicitly specify one before that.

- Fixed: Negative Ledger Account IDs were displayed as "Unknown" in the "Inventory Account" of Inventory Valuation.

- Fixed: Negative Ledger Account IDs were displayed as blank in the "Account" of order payment tenders.

- Fixed: The built-in Tax Report omitted partially invoiced line items from output until those line items were completed in customer order processing.

- Fixed: Work Order Check In would find a fractional assembly on other work orders.

- Fixed: Location Accounts (example, LOCATIONS.AR smallint) with negative values were not handled correctly in AR Payment collection on a Customer Order.

- Fixed: (Ported from 6.8.059) When a positive partial invoice was tendered On Account, then a subsequent negative partial invoice is checked out,
FrontLine should turn the positive open On Account tender line into a split positive and negative, to send the credit to AR.

- Fixed: FrontLine 6.7.053 did not allow typing into the Pay Now column when applying a credit in Receivables.

- Fixed: FrontLine should not allow the user to change addresses on a Work Order, but when the Work Order Location is changed its address should change to match.

- Fixed: The Receivable Payment security context in the Customer Orders class is now Receivables and lack of a Modify permit here should prevent changes to Due Date, etc.

- The Receiving commit and link to Unidentified and Backorders list (shown at the bottom of window) now sorts the backorders by Order Scheduled date (if any) then Order Placed date.

- FrontLine Shipping now records the OrderID in the SHIPMENTS table when option Order Combination is NOT used.
Note that the column must be added to the SHIPMENTS table.

- Fixed: FrontLine did not handle negative Ledger Account "Key ID" values correctly when assigning Item Category Accounts to line items.

- Fixed: Selecting "Files" from Item Lookup then accepting the prompt "Would you like to select the record last filed?" did not work as expected on Purchase Orders.

- After the retired address notification, FrontLine now offers to update the order retired Sold-To address if the customer has a new Sold-To address on file.

- Voiding a line item will now check for Mobile Connect (MC) (Baselink) entries to void even if the line was not imported.

- Upon completion of a shipment, when the SHOPIFYSYNC table present in the database FrontLine will now add a record with (SyncType=64, ID1=OrderID, ID2=ShipID) for each order in the shipment. A shipment may span multiple orders when the Order Combination option is used in Shipping.

- Fixed: Import of Mobile Connect (MC) Parts or Labor related to Repair Equipment that had been entered in FrontLine first and then added in MC could end up linked to the wrong line item when there were multiple imports of that service order.

- Fixed: On a Payment order, FrontLine should not allow the customer to be changed by various address and customer number text edits.

- If the Job panel is open on an order but no job is assigned upon checkout then FrontLine prompts the user, asking "Do you want to continue without assigning a Job?"

- Third Party launchers (all Third Party entries aside from "Send POs to MOL") now require a "Modify" permit for the "Third Party" Access class.

- Jobs listed in the customer orders window now consider both the Bill-To and Ship-To entity.

- Fixed: FrontLine would incorrectly apply AR credits to the customer vs warranty vendor on a Service Order Invoice that included a Warranty Vendor Invoice.

- Fixed: When a user had specific Event Categories selected for the Scheduler Board view and attempted to open a scheduler event from an order Line Item Details window that was not in that event category, FrontLine would claim that it could not find the EventID.

- Fixed: The SD sheet function had disappeared from Order windows in 6.7.046-047

- Multiple billing contact email addresses assembled for Recurring Billing Output EMail now have comma delimiters added instead of semicolons.

- Added a Disable Auto-Commit (except Fast POS) option to User Options with the same effect as the Company Setting in Line Unit Identify Options on an individual user basis. If the Disable Auto-Commit company setting is on then this user option has no additional effect.

- The Receivables window now includes a Periodic Invoice ID [PVID] column instead of [InvSeq] and the InvSeq is shown in the [OrderID] column after a hyphen instead.
When exported the columns are separate.

- Diagnostic Reports enhancements including more translated columns and there are now separate Edit vs View Order context menu entries.
The View Order and Edit Order functions only appear when there is an OrderID column.
To enable the Edit Order function there must also be OrderType and OrderStatus columns, the order status must be open and not in use, and the user must have appropriate permission.

- Fixed: SD sheets created in context of a Purchase order should use the Vendors template instead of the Customers template sheet.

- Fixed: SD sheets could be opened by users with "None" permission for the relevant Supporting Documents security context.

- Fixed: Built in taxes did not recalculate at the new value due to a line item Rental Periods change.

- Fixed: Resource Costs could be modified, added, or deleted by users who lacked permission.

- Fixed: When card tenders were combined with On Account on a customer order, FrontLine might skip over card tenders and put the customer invoice all on account.

- Added to Company Setting Order Activity Reactions an option to Always show the Job panel on open Customer Orders.

- In an identifier document of Line Item Details clicking the identifier type while holding down a Ctrl key will now open the resource (local file or web page) indicated by the identifier value.

- Custom Reports with varchar output columns of width between 20 and 63 and column name ending with -UITypennn (where nnn is a variable length number corresponding to a UIType) are now processed as Identifier Values of that Identifier Type (the Data Type and Edit Mask are applied) and the column name has the -UITypennn text removed.
For example, this will output a column named "Latitude" and display the values as latitudes if UIType 7 has Data Type set to Latitude:

- Fixed: Item Quantities provided an erroneous calculation of Open PO quantity when multiple units had been received on open PO line items.

- Fixed: Shipping Charge Calculators did not trigger in time for line item changes made without moving the cursor just before check out.

- Fixed: FrontLine should ignore client locale when submitting numeric values with decimal points to the database server.

- Fixed: Producing a customer invoice on a service order that also produced a Warranty Vendor Invoice took too long due to poor planner results from MSSQL Server.
This fix is a rewrite of one query in the db procedure NewInvoice.

- FrontLine can now send email compositions to a web browser window to be mailed via a Google Workspace or Gmail account.
The user's Return EMail address in System Users must correspond to their Google address, and the user will have to log in to their Google account in the browser if they haven't already.
FrontLine opens an email composition window in the browser with the recipients, subject, and body text, and provides a visual object that the user can drag and drop on the browser to add all the attachments.
To use this method instead of SMTP the Mail Relay in Locations should be set to:

The Db Console contains two required updates:
Expand LOCATIONS.MailRelay (6.7.045)
File: NewInvoice v6.7.045

- When adding a Bill of Materials (BOM) to a Service Order with Repair Unit Lines, the Package Content Selector now offers a Repair Unit Assignment selector to link with one click all the line items added from the BOM as repair consumption of the selected repair unit line.

- Added a Max Resource Labor Hours Company Setting to have FrontLine notify the user before checking out a customer order if the total "Labor" in Resource Costs exceeds this threshold.
Values greater than zero enable this check.

- Added a Stock and Description option for "Scan Auto Lookup" to Company Setting Lookup Options that changes the Description* combined search to Description and Stock Number*
This affects both line item Scan Code auto-lookup and general Item Lookup searches.

- Added to Company Setting Return, Repair, and Unidentified Options an option to "Copy Unit Warranty Parts Expiration Date entered to blank Services and Charges Expiration Dates"
When enabled, this option copies the parts expiration date entered by the user to services and charges expiration dates if this other expiration date is blank and the standard warranty for the item includes coverage for this (services or charges).

- Users who have a "Modify" permit for the Setup--Security access context can now change User Options and Access Profile in System Users.
To enable this to work for any user, this SQL must also be executed in the database:

- The Item Locations view in Scan Match can now be sorted by clicking column titles.

- Terms are no longer required on Vendor Invoices. Invoice Date and Due Date are required.
When the Terms are blank, the Invoice Date and Due Date can be set independently.

- Expanded Desc1, the first description field for ITEMS, from 40 characters to 160.

- The Line Item EDI feature now has a Copy function that makes the currently viewed EDI values available for when the next line item EDI is added.

- Setup Identifiers now has a !Warr flag to indicate that the identifier is required on Warrantied line items that are not returns.

- Imported line item quantities should only be locked for OrderIDs below the normal FrontLine 100,000,000+ range.

- The jobs listed in the drop-down of the Job selector for an order are both customer-specific jobs and jobs not assigned to any customer.

- The jobs listed in the drop-down of the Job selector for an order are now customer-specific.

- Fixed: Line items imported from Mobile Connect (MC) where the customer has a price level or other discount on the item did not adjust the effective total to match.

- Fixed: Pressing F4 to view a customer order from Receivables after entering a Pay Now value but before pressing Enter or an arrow key would cause FrontLine to lose track of this amount.

- Fixed: AR Credit should not be issued on a subsequent partial customer invoice where prior cash tenders exceeded the amount invoiced so far.

- Added a Receivable Statements sticky option "Group by Periodic Invoice" to enable statement forms to summarize by periodic invoice.

- Line items can now be added to Web Orders at zero price after user confirmation, and these non-imported lines can also be voided.
To do this, users require an ADD permit for new context "Add Items to Web Orders" that is near "Transact Unidentified"

- Restored the new Export MOL Third Party export format to the new scheme developed in 6.7.037

- Fixed: Returns of an AR Payment order where the payment credit had been applied after the payment receipt did not spread the payment reversal to all the receivables credited.

- Added a Compare feature to Access Profiles to Report All Contexts and Report Differences of Access Level between all profiles.

- Fixed: Returns of Repairs of Customer Equipment via the Returns window did not forward the warranty and service contract coverage of that customer equipment.

- Fixed: Costing of a customer Special Order where the special Purchase Order had been voided and recreated could end up using the purchase price from the voided PO. This fix is in the CostInvoice db procedure.

- Fixed: Costing of Transfer Orders using Average, Last, or Standard cost would use the cost at the destination location instead of the source location. This fix is in the CostInvoice db procedure.

- Fixed: 6.7.037 introduced a class not found error before printing a Packing Slip from the Shipping feature.

- Fixed: FrontLine should make a negative "on account" tender out of an open positive on account tender to complete a negative invoice on a positive order.

- Fixed: Periodic Invoices function to Print All as regular invoices did not output the identifier values of intangible line items, and did not exclude refunds like the main periodic invoices output.

- Reverted the Export MOL Third Party feature export format to the scheme used before 6.7.037

- Enhanced capability for filling out Excel workbooks from Forms for Orders
Order values can now be used in the line item output.
FrontLine will look for a Lines range on the second worksheet as well as the first.

- The Export MOL Third Party feature now outputs the new file format defined by Motorola.

- FrontLine now rechecks for any retired addresses assigned to the order before checking out or completing an order. If any are found the user is notified and the process stops.

- Fixed: AvaTax has begun to include messages that are not errors. FrontLine will show these to the user as an AvaTax Transaction Notice.

- Fixed: Export of large text columns in Spreadsheet mode should double the double-quotes like it does for shorter text values.

- Fixed: For customer invoices that also generated a warranty vendor invoice, the built in Tax Report output would double the values.

- Fixed: Adding two lines of a Set Eligible item to a customer order where the customer had no Equipment Sets yet could result in key violation of PK_ESDTL.

- Fixed: Submitting an order to AvaTax immediately upon adding an order discount (before moving the cursor off the line) would result in tax calculations missing the latest order discount.

- Added an option to the "AvaTax Configuration" Company Setting to "Exclude All Purchasing" from AvaTax.

- Fixed: A recent revision caused the order payment tenders special menu entry "Repost all AP" to appear for customer orders instead of "Repost AR"

- Submissions to AvaTax for non-exempt invoices now omit the "customerUsageType" instead of sending "TAXABLE" Customer Usage Type.

- Fixed: In Fast POS mode auto-commit should occur even if disabled in Company Setting Line Unit Identify Options.

- Fixed: An earlier revision to add the Shopify tender type awareness introduced a bug when the Tender Types accepted were changed in Company Settings.

- Fixed: FrontLine did not collect a negative tender on a subsequent invoice when prior invoices had collected positive tenders and the order was then changed to produce a negative invoice.

- Scheduler Events now have a Notification value specified in Minutes.
There is a new Company Setting Scheduler Notification (LValue=63) to set the default value.
CALEVENTS.Notification contains the customized minutes for an event, or NULL (blank) for default, or negative for No Notification.
To set "No Notification" on a scheduler event enter any leading part of the word NONE in any character case.
It is recommended to set the Scheduler Notification Company Setting for any site that uses the scheduler.
The program default in FrontLine is 15 minutes when neither value is set in the data.
Actual notifications are implemented by the Mobile Connect App.

The Db Console contains a required update:
Scheduler Notification (6.7.031)

- Fixed: Line item MaxTax did not work correctly on unlinked returns. This fix is in the GetTaxes db procedure.

- Added an Equivalents feature for Items.
There is now an Equivalents tab in Items maintenance where equivalents can be added and removed.
FrontLine raises a notice against adding equivalent items that mismatch by Item Types Inventory vs Service vs Charge, Recurring Bills, and Set Eligible.
The Reservation window offers Equivalents when the reservation began from a new (blank) line item.
An equivalent item can be selected from the list by either a double-click or the Enter key.

The Db Console contains two required updates:
EQUIVALENTS (6.7.030)
File: GetTaxes v6.7.030

- Rental Reservations can now be started before creating a line item.
In this case the stock item to be reserved can be changed in the Reservation window.
The order customer must be assigned before creating a reservation.

- Invoking the Reservation shortcut Ctrl-' on a blank customer order now turns it into a Short Term Rental order,
and assigns the workstation's rental location (if defined) to the order location if the order was not already assigned to a rental location.
Invoking the Reservation shortcut again then opens the Reservation feature before any line items exist.
When a reserved line item is added to a blank order with a blank order scheduled date FrontLine will now set the order scheduled date to the reservation begin date (the line scheduled date) of this first line item.

- Fixed: Scanning a suitable identifier value in Line Item Details Scan Code for an adjust out line should commit the unit to adjust out.

- Fixed: FrontLine could fail to collect Card and EFT refund tenders on an order credit check-out.

- Fixed: The last revision introduced a potential incorrect notice about Substitute Category mismatch when saving an Item in Items maintenance.

- Fixed: An invalid pointer operation could occur in some databases after opening Costing of the Check-In of a received purchase order.

- Fixed: Repairs of Rented units should remain at the Rental Location, regardless of Company Setting Repair Units in Order Location.

- Fixed: Closed Locations should not appear in the Ship-To address selection list of POs.

- Fixed: Invoicing that closes an order should process any remaining tender credits.

- Fixed: Shipping Charge Calculators should ignore any return line items from the Order return function.

- FrontLine no longer attempts to send ErrorStack emails about Db Errors (typically from bugs) that it encounters.

- Stock numbers are now shown in the Substitute field of Items maintenance. There is also a hover hint for the substitute.

- In the Service Contracts window the "Show other customer equipment" option no longer includes equipment that is Out of Service.

- Upon taking customer payments, in the Receivables window Write-Offs are not allowed against a receivable when no payment is applied to that receivable.

- Costing values shown in the Invoice/Check-In/Out window are now negated for returns and adjust-out.

- The Scan Code entry field in Line Item Details can now be used to quickly return multiple rented units on a Rental Return line item of multi-quantity.

- After creating a rental return line the cursor now rests on the return line quantity, and if the quantity is increased for a uniquely identified item the Line Item Details window opens with focus on the Scan Code entry field to quickly scan the other rental returns of the same stock number.

- Added an option User Agent priority on new Lines to the User Options available in System Users.
With this option, the user's agent takes precedence over the Customer's Agent and the Order Agent on line items created by the user.

- AvaTax began adding a blank "messages" section to successful invoice commit responses. FrontLine should not interpret these as an unknown failure indicator.

- Changed the Shopify tender type [PAYMENTS.PType] from -42 to 42 and for AR purposes consider it a card tender.

- Fixed: FrontLine should not permit voiding a scheduled line item when the order has WEBLABOR, WEBPARTS, or WEBREPUNITS imported from Mobile Connect (MC)
Those related line items must be voided first.

- Added a permit context for Send POs to MOL in the Third Party class to control access to this function specifically within the Third Party section.
Sites that use this function will need this permit value set for their people who use it.

- The Web Order order type flag is repurposed to indicate that a customer order is from an external source. The characteristics are now:

The Db Console contains two required updates:
TRX.RefQty (6.7.021) Apply this one first.
File: CommitInvoice v6.7.021

- The Mobile Connect Image output FileName from Forms for Orders now matches the FrontLine line item image viewer for MC images revision made in 6.7.018

- FrontLine now confirms that the user wants to invoice an order when there are related Mobile Connect (MC) entries that have not been imported yet.

- Mobile Connect labor entries with no hours indicated are no longer imported on the same day they were entered. The next day (or later) they will be imported with a default (as before) of one hour.

- Revised a small query related to ContractExpiration output from Forms for Orders that was causing SQL Server to make expensive query plans for large databases.

- Some other outputs from Forms for Orders from large databases can be made more efficient by adding this index to the SQL Server database:

- Fixed: The email address helper invoked from a scheduler event referred to the wrong customer order.

- Fixed: The Create Db Procedure feature introduced in 6.7.017 Inventory Valuation was missing the look back loop.

- Fixed: An Equipment Set member whose Initiated date was in the future would be marked as billed if its equipment set was included in the billing for other members, and subsequently this member would be included in future bills even before the Initiated date was reached.
In addition to this program fix, the data must also be patched with this SQL:

- Voiding an order no longer removes declined tenders, only unprocessed tenders are discarded.

- When authorize.net returns code 1 (Approved) but no Transaction ID FrontLine now shows the user any message text in the response, warns the user, and declines the card payment.

- The PSet (periodic invoice batch) report context parameter introduced in 6.7.012 can now also use a more descriptive PeriodicInvoiceBatch name which appears as "Periodic Invoice Batch" in the Query Parameters window.

- Recurring Billing now sets the end date of a bill (ORDERS.Fulfilled) to one day before the next billing period instead of the first day of the next billing period.

- It is now possible to begin the process of creating a Vendor Invoices directly from a Purchase Order that has been at least partially checked in.

- Work around a SQL Server issue that can cause a revision in 6.7.002 Equipment Search options Exclude Committed Units and Exclude Out of Service Units to make the search to take three times as long.

- The FrontLine line item image viewer for MC images from WEBREPIMAGES now adds a RepUnitID_ after the CalendarID_ that is adds if the recorded file name does not already have a CalendarID_ lead text.

- The Scheduler Event window now gives display precedence to the "Complete" Event Status so that events marked complete by invoicing the related order line item to completion show this "Complete" mutually exclusive status rather than the last one set by a user.
Additionally, the revised CommitInvoice db procedure now removes the other mutually exclusive event status flags.

- Fixed: 6.7.016 introduced a bug where returned units were not removed from Equipment Sets.

- The default PDF file name suggested by Recurring Billing Output is now Bill_nnnnnnnn.pdf (where nnnnnnnn is the OrderID) when:
- "Print One" is used, or
- "Print All" is used and there is only one bill in the batch.

- Added a Create Db Procedure feature to the evaluation batch list context menu of Inventory Valuation to create a database stored procedure for inventory valuation hard coded using the current options.
The user is prompted for the procedure name, and the two output tables. The stored procedure truncates these two output tables before adding data to them, it does not create the tables.
The two tables require these columns, additional columns can be present if they accept NULL values:

- Fixed: Order Redo should put the new order in the same location as the source order.

- Fixed: Repair Unit line items Imported from Mobile Connect (MC) should remain at their last line location.

- Fixed: The Item Tax Category check added in 6.7.013 for Recurring Billing with built-in taxes incorrectly applied the Location flag Tax on Location GeoCode.

- Package Recall will now transfer member quantities to the package selector when Company Setting Package Sale Method is set to Package As Discount.

- The Scheduler Board view, To Be Scheduled list, and Resource Summary now give precedence to the Location of the Agent (Resource) over the Event Location for Location Group selections.

- Added a report group: Related to an Inventory Valuation and a menu to use these from the valuations list in the Inventory Valuation window.
Reports in this group have access to the corresponding valuation result temporary table sequence in parameter value IVTT
Example FROM clause using aliases:

- Fixed: 6.7.013 introduced an error "qrEX_: Field 'Tax Category' not found" in Step 2 of Late Fee Billing.

- Fixed: FrontLine should not recheck the card expiration date of a tender that was collected (as in a deposit) prior to invoicing.

- Fixed: The Item Tax Category check added in 6.7.013 for Recurring Billing with built-in taxes did not use the option Bills use ESet Residence as Ship-To in Company Setting E-Sets, Rentals, Contracts.

- Changed the shortcut key for the Browse for Resource File for identifier values feature from F3 to F5.
This applies to identifiers in Line Item Details and the Identifier Documents window, and folders in Locations maintenance.

- Recurring Billing with built-in taxes now checks for Item Tax Category missing from applicable Tax GeoCode in Step 2.

- Forms for Orders output now includes an MCI (Mobile Connect Image) dataset with Caption and FileName outputs.
Typically the best layout is one image per output page with the caption at the top.
(MC) Image data is based on information in WEBREPIMAGES.

- FrontLine E-Mail composition now has an Add Images function that can show the FrontLine Images window with MC images relevant to the order or customer in context. From there multiple images can be selected to attach to the email.

- The Copy to Local Storage feature introduced in 6.6.048 now also checks for a local "Documents/FrontLine" folder that the official Microsoft "RD Client" on the iPad and iPhone can provide. To enable this the RD Client connection must enable "Storage" under "Device & Audio Redirection" and the user must create a "FrontLine" folder on their local device in their local "RD Client" folder.

- Fixed: Built-in taxes were not calculated for Mobile Connect (MC) lines imported.

- Fixed: Inventory Valuation should not consider received from depot repair a costing event.

- Fixed: The message shown when a Job as Completed when there are open orders on the job was garbled.

- Fixed: Redo of an order where line item warranties had to be re-evaluated would double the order totals in the new order.

- The Order Type filter entries in Order and PO Lookup is now reduced to relevant values.

- In the Identifier Document editor, and in the identifier section of Line Item Details the F3 key can be used to browse for a local file to select as a linked resource.
This function is only valid for plain text identifiers with no edit mask or selection list.

- Added three report groups: Related to a Customer Order, Related to a Purchase Order, Related to a Periodic Invoice Batch and a menu to use these in the three corresponding windows.
If, for example, there are reports in the "Related to a Customer Order" group then FrontLine adds corresponding menu entry to the Print button that opens the Reports window offering only reports in that group.
Note that FrontLine only builds this menu once per window per log-on session so if there were no reports Related to a Customer Order when the user opened Customer Orders, then the user goes to the Reports window to add some reports in this group, returning to the same customer orders window will not show the new menu until the user logs out and back in.

Reports run in this way can have the following parameters supplied by the program without need for user input, so if there are no other report parameters then the report will run without a prompt for parameter values:
OrderID
ItemID
EntityID
AddressID
DtlID
PSet (periodic invoice batch)
Both plain queries and visual form reports are supported. Plain SQL reports are output in a grid in the report window like a diagnostic report.
Not all values are available in context from all features where this is implemented, and some values vary within the same window.
For example, an ItemID comes from a line item on orders so it changes as the user scrolls through line items.

- Fixed: When Landing Cost is available for a unit sold of an item whose costing method is "Unit (Actual)" it should be forwarded to the Customer Invoice Costing.
This fix is in the CostInvoice db procedure.

- Fixed: Inventory Valuation for Unit (Actual) costed items should include Landing Cost, and the Details list should show primary identifiers that are not serial numbers.

- Purchase Freight charges can now be assigned to a specific tangible line item on a purchase order to indicate that this particular freight line applies entirely to the landing cost of that one line. Non-specific freight can be included on the same Check-In, in which case the target line landing cost receives the full freight charge from its line-specific purchase freight plus the freight fraction it receives from the non-specific freight charge that was spread (weighted by unit cost) between all tangibles on the Check-In.

- Identifiable Tangible Items flagged with the new Item Type Assigned Price (value 1,048,576 or 0x100000) have, when received on a purchase order, a special identifier type "Assigned Price" (UIType 32750) added to their identifier documents.
The "Assigned Price" identifier value is required to check in received inventory on a PO, and can only be modified on a PO.
When one of these units is committed for sale on a customer order that is not a special order FrontLine will set the line item price to this Assigned Price value, and flag the line (TrxStatus flag value 4,194,304 or 0x400000) as having an assigned price so it is not eligible for automatic discounts. If the user manually overrides the line item price then this flag is removed.

- Fixed: A recent revision broke the Rental Items special Item Lookup Search By.

- Locations now have an optional Location Group. Location Groups are defined in Setup - Lists.
Location Groups are used to filter events on the Scheduler board, Scheduler Event window (where when an event is opened the Location Groups preselected reflect the selection on the scheduler board) and in Scheduler Event Lookup.
Location Groups can also be used to filter Agent Lookup results.

- Fixed: Line item taxes that are levied in flat amounts (not a percentage rate) did not negate on "Return Next Scan" line items. Part of this fix is in the GetTaxes db procedure.

- Fixed: Invoking Transaction Inquiry from an order line item, and opening an order from within Transaction Inquiry, then returning back to the original line item would put the original order window in a state that did not accept new line item entries until the order was deferred.

- Fixed: After redirecting billing on a customer order, set eligible line items added could end up in the Bill-To customer's equipment set instead of the Ship-To customer.

- Fixed: It was possible to check out an Order Discount by itself. This fix is in the NewInvoice db procedure.

- Fixed: Line Item Change Log entries did not show resulting Quantity correctly.

- In the Scheduler Event window if an event is part of a recurring sequence and not yet associated with an order then in the list of orders shown to add this even to, the order associated with the lead event (if any) is highlighted with bold text.

- Added Job Commission Paid Update to the Third Party panel in the Welcome window. This link launches a Python program file in the FrontLine program or ACC\ folder named JobCommPaidUpdateFLFL.pyw where FLFL is the name of the database in use.

The Db Console contains two required updates:
File: NewInvoice v6.7.009
File: GetTaxes v6.7.009

- Fixed: FrontLine could not interpret Payeezy results when the response header length exceeded the first chunk size.
This became a potential issue when Payeezy began to insert nearly 500 character long "Content-Security-Policy" http header lines.

- Fixed: Creating a service order by a Repair of the first scanned unit where the last known address of that unit was Retired would assign the order locations Tax GeoCode to the order but fail to make it POS as this GeoCode indicates. FrontLine should use the customer's default ship-to address in this case.

- Fixed: Costing a sale Return order did not attempt to use the cost determined for the sale. This fix is in the CostInvoice db procedure.

- Fixed: After adding equipment to multiple new Equipment Sets of a new customer a violation of primary key PK_ESDTL could occur.

- Fixed: Errors in the Overdue value shown in the Batch Review step of Late Fee Billing and the calculations on the Late Fee Bills.

- Late Fee Billing will not create bill line items for receivables that are less than $1 due remaining.

- When Recurring Billing redirects the Bill-To customer on a recurring bill it now changes the bill's Tax Exemption to match the customer receiving the bill instead of the customer whose equipment set incurred the bill.

- Fixed: A recent revision could cause FrontLine to erroneously claim that "Customer has insufficient credit to cover this order, or it is partially tendered" when the order was automatically tendered on account.

- Added item Desc2 and Desc2 to the export columns available from Physical Count.

- When Company Setting Use Special Cost for Commissions, when available in Cost Options is OFF, Order Totals now ignores any line item C.Cost [CCost] values for non-miscellanous lines.

- Order Totals now now gives special treatment to Miscellaneous line items.
Miscellaneous lines ignore Average and Last cost regardless of the user's selection for Cost Used.
When Company Setting Use Special Cost for Commissions, when available in Cost Options is

- Fixed: Buffer overflow leading to access violations was possible when importing 60+ lines at once from Mobile Connect (MC) activity.

- Fixed: A recent revision broke unidentified handling in Fast POS mode such that they were returns even when Return Next Scan was off.

- Added logging of Payeezy results:
Log files are saved in %LOCALAPPDATA%\FrontLine\PayPort
Every day uses a different log file, named PayPort_yyyymmdd.txt
A single line is logged per transaction with no confidential information, unless the response is not recognized as an approval in which case the response body is added on a second line.

- The access permits in the Setup group and their corresponding features are now more functional:

- Fixed: Again some circumstances could trigger a database primary key violation on PK_ESDTL upon saving Equipment Set members.

- Fixed: A recent revision made the Location ExtRef fail to appear on Tax Report output if an order had not been opened before.

- Fixed: Warranty Vendor Invoice date should match the override date entered for a (backdated) Customer Invoice.

- AvaTax response for Order Discount changed from "discountAmount" to "totalDiscount".

- Fixed: Selecting an event from Scheduler Event Lookup that does not qualify to appear on the scheduler board now offers an opportunity to edit the event directly.

- Added Include agent name in Agent values shown to Company Setting Lookup Options for both the search results and Search By Agent selector.

- Added Security Contexts (not used by FrontLine desktop) for MC Users Management, OBO Integration, and HubSpot Integration.

- Fixed: AvaTax stopped using chunked responses, FrontLine has to read them accordingly.

- Fixed: Recurring Billing Output output of contracts and covered equipment is improved to prevent "No Data Available to Print" caused by coverage history.

- Fixed: Total Quote Taxes display was not highlighted with pink and a question mark when AvaTax calculations were out of date.

- Fixed: A recent revision broke the PO Total calculation after using autogen to add line items to an existing purchase order.

- Fixed: The "Total Quote" value shown in Order lookup (both customer and purchase) incorrectly added return values.

- Fixed: Equipment Search results did not exclude units that have been adjusted out.

- Fixed: Short Term Rentals of items with a default Bill Frequency did not accumulate in the same equipment set for one order.

- Fixed: Paused AvaTax submissions introduced in 6.6.064 caused a tender auto-update issue when a customer order was deferred.

- Fixed: When a single FrontLine shortcut was used to enter multiple databases by selection from the logon window, after logging out from one company then logging into another without closing the FrontLine application, the Location list in Tender Types accepted (and possibly other windows) contained locations from the prior database.

- Added Require Scheduled date to Print or Present a Customer Quote to Company Setting Quote Options.

- Added a Release Orders In Use by Disconnected Users function to the context menu that appears with a right-click of the System Administrator indicator in the Welcome window.

- If an On Account or Card tender is 1 cent off from the needed amount when invoicing, FrontLine will now adjust the tender by 1 cent.
This accommodates AvaTax invoice taxes that do not add up to the total order taxes estimated by AvaTax due to rounding breakdown.

- Tentative events shown in the Scheduler Task List now exclude events that are Closed.

- Added to Scheduler Event Lookup a Search By Agent and special search Events not linked to Orders.

- Added the order note subject to the list of open orders offered Scheduler Event window to add the event to.

- The recent orders recall list has moved from within the OrderID cell to a drop-down beside the Orders lookup button, and now includes some text and an icon to help with recognition.

- The new recent orders recall menu in the customer orders window also has a Go To Purchasing entry to open a purchasing window that can be used side by side with customer orders.
Note that in this scenario, closing the customer orders window also closes the purchasing window.

- If a reference transaction tag is available, Payeezy card refunds now attempt a VOID transaction before a REFUND transaction.
A card transaction can be voided by the card processor before it has been collected by an end-of-day process.
FrontLine does not know if the original card transaction has been collected so it simply tries a void first, and if that fails it tries a refund.

- The context menu of the payment tenders for a customer return order where the sale was tendered by a tagged card transaction now offers a list of the original card transactions to add as a tagged refund tender. FrontLine does not check how much of the sale amount is still available to return so the tagged card refund may fail at Payeezy, in which case a new unlinked card refund has to be used instead.

- Vendor Invoices no longer require tenders, and like recurring bills, are Approved without a check-in process and without INVOICES records.

- The Payables (preview) window now has a function tool bar between the summaries above and the payables list below.
A payment process (preview) begins using the "Select for Payment" function to begin a "Pay Now" mode that removes the summaries to maximize space for the payables.
In the "Pay Now" column that appears the user can enter an amout to pay, or use the checkboxes in the "Amount" or "Discounted Amount" (if applicable) to pay those specific amounts.
There is also an "All" toggle to default payment of all listed dues to the Amount, or Discount Amount (if available and within discount date).
"All" mode retains any specific selections made by the user.
Below is a summary of the dues listed, and a "Total Pay Now" to keep track of all the amounts selected to be paid.
Actual payment using the "Pay by Checks" and "Pay by EFT" and "Pay by Card" functions have not been implemented yet.

The Db Console contains two updates:
ORDERS TotalDiscounted (6.7.002) Required.
AP (New in 6.7.002) Only required if the AP preview is used. It is a redo of the AP table. Do not create the AP table if you do not want to enable AP preview.

- Fixed: Forms for Orders output of Pick Ticket and Ship Ticket should use the customized line sorting introduced in 6.6.052 when option "Sort by Line number" is off.

- Fixed: Adding generated Miscellaneous Purchases to an existing purchase order would prompt the user with an Order Effective Total Mismatch after reopening the PO.

- Vendor Invoices now show and allow selection of Pay To addresses instead of Ship To in the main entry window.

- Received quantities are now shown per line in the New Vendor Invoice window, and selecting a PO that has not been received yet raises a warning notice.

- Added a MC and CP Administration class to Access Profiles with contexts for MC Logs, CP Logs, and CP Users Management. These security contexts are used by Mobile Connect and Customer Portal.

- Fixed: 6.5.053 introduced a bug Package maintenance that triggered a database key violation of PK_PACKAGES when a member was moved from one Group to another Group.

- Fixed: 6.5.050 broke forwarding of unit warranties and service contract coverage on depot repaired equipment.

- Fixed: 6.6.064 introduced unintended case sensitivity matching user-typed location identification texts.

- Fixed: Company Setting for Default Bill Location did not reveal the ID of the Value last entered.

- Fixed: The Returns window should not allow returns of lines that have units still at depot.

- Fixed: Equipment set members did not prorate correctly to the order when the equipment set currency was not base currency.

- Fixed: When an unknown Scan Code entered on an order was turned into an identifier of a previously unidentified unit, FrontLine did not enforce the UPPER case option on this new identifier value that came from the scan code.

- Fixed: Moving and Exchanging Equipment Set members for customers with large equipment sets could raise an SQL error "Cannot insert the value NULL into column ESLine, table ESDTL" when FrontLine saved changes. This was caused by ESLine values out of range of the smallint data type.

- Note outputs from Forms for Orders are now processed to convert any bare line feeds (LF) or carriage returns (CR) to CRLF pairs to ensure correct spacing interpretation by Windows functions.

- Added a Company Setting Cardholder Requirements to allow company customization of the cardholder information fields required.
The default requirements are now CVV and Zip.
If Payeezy is used then FrontLine will turn on CVV and Cardholder Name requirement even if they are turned off in the company setting.

- When it has a list to match typed text from, the QuickFind function now has new options and defaults to "Begins with" vs "Contains text" behaviour.

- The drop-down menu from Customer Number in the customer orders window now offers a link to the customer's Receivables without context of taking a payment.

- Printing order related forms with AvaTax does not invoke an AvaTax update if the order is Exempt and the current tax total is zero.

- The Members count in Service Contracts maintenance now ignores dummy members with a negative XRDTL.DtlID

- Added Lockbox Import to the Third Party panel in the Welcome window. This link launches a Python file in the FrontLine program folder named LockboxImportFLFL.pyw where FLFL is the name of the database in use.

The Db Console contains six required updates, some must be applied by administrator before standard users can log in:
ESDTL.ESLine type int (6.7) Includes ESMETERS. This can take a while in a large database.
File: NewInvoice v6.7
VENDORS.APInvRef (6.7)
PAYMENTS.CardIssuer (6.7)
TRXIP.RefQty (6.7)
AP (New in 6.7) Do not create the AP table if you do not want to enable AP preview.

- Fixed: 6.6.062 broke historic Inventory Valuation by causing an SQL error when a Date in History was used.

- Fixed: Packages were taxed incorrectly when package quantities and/or package discounts were changed on the line item. *

- Fixed: Line item taxes were not allowed to recalculate after a line was on an invoice. This fix is in the GetTaxes db procedure. *
* Neither of these tax bugs affected companies integrated with AvaTax.

- Only applies to AvaTax Submissions to AvaTax for order taxes are now paused during order entry, instead there are indicators that taxes are out of date.
Order taxes are automatically submitted for updates:
a) When a tender of any type is about to be added for the order balance total.
b) When a Cash (not check or card) tender is added or changed.
c) When the order is about to be invoiced (not for sys admin).
d) Before printing an open order.
e) Before showing Order Totals.
Invoices taxes are submitted for every invoice as before.
Users can request an order tax update when desired by clicking the Recalculate Taxes bar.

- Fixed: Opening Order Totals or Opportunity Totals could cause FrontLine to crash later with an access violation.

- Fixed: The Inventory Valuation list of unit Details did not always include all the units in the "Total Quantity" and when this occurs inventory items set to "Unit (Actual)" costing default to the location Average cost for the total value instead of the sum of the unit costs.

- When Return Next Scan is used in Fast POS mode FrontLine now asks for the Item Action to offer Return, Repair, and Exchange actions.

- When a user clicks Signature in Line Item Details for an imported line item that has no signature on file FrontLine asks if they want to collect a signature now instead of assuming they do.

- Partially checking out a previously invoiced order that was cash tendered (like with a check) for the order total now asks the user for confirmation to proceed with the Excess Tender already collected.

- Removed the Unique Contact EMail Address constraint that was added (conditional on presence of the Customer Portal) in FrontLine 6.6.055

- The {} indicator for Custom Reports introduced in in FrontLine 6.0.0067 is now separated into code interpretation vs column name alteration indicators:
{} turns off code interpretation
[] turns off column name alteration
To use these indicators the very first characters of the SQL can be {} or [] or {}[] or []{} where the last two are equivalent.

- Fixed: A user with a quote in their full name would get an SQL error upon saving an appended AR note.

- Fixed: Recurring Billing Output could fail to output contracts whose covered equipment were committed to an open order.

- Fixed: FrontLine should exclude account Payments from Paid Transactions in the Receivables window. This requires a db update.

- Fixed: FrontLine did not clear the prior payment verification results upon cancellation. This bug was introduced with the Payeezy development.

- Fixed: FrontLine should not allow users to toggle Special Order on a Purchase Order line that has been received and committed to a customer order.

- Fixed: The "Total Quantity" shown in Inventory Valuation included units in the following conditions but they were not shown in the Details list:
"In Use", "In Shop", and "Defective"
and the event date shown in the Details did not reflect the Check-In (Invoice) date.

- The Invoice/Check-In/Check-Out date (that users can override) that is used as an inventory event override date for Inventory Valuation is now used likewise for Inventory Transactions.
The Receive Date and Time override in the Receive window is no longer applicable and has been removed.

- FrontLine now records and shows the user who created (and changed) a batch in Export MOL and Tax Report. This requires a db update.

- FrontLine can now show the OrderID that the receivable being paid is from on the Payment line item when the payment was taken with company setting "Enable application of Payments to Receivables" turned off.

- FrontLine now converts (from SVG to Ink) and imports signatures collected by Mobile Connect (MC) as line item signatures.
If an line item that was imported with a signature is voided in FrontLine desktop without voiding the MC entry then the line item signature is removed from the desktop data.
FrontLine also looks for a MC event signature and if found, converts and attaches this signature to the line item linked to the scheduler event.
This MC event signature is presumed to exist in these CALEVENTS fields added by MC: Signatory, SigDate, and SigPath.

Microsoft Ink requires these four COM libraries to be present and registered: INKED.DLL INKOBJ.DLL INKDIV.DLL TPCPS.DLL
FrontLine needs the 32-bit version of these components, they must be registered using REGSVR32
They are typically found in the 32-bit folder "C:\Program Files (x86)\Common Files\Microsoft Shared\Ink"
although INKED.DLL is often in folder "C:\Windows\SysWOW64" instead.

The Db Console contains three required updates:
SYNCLOG User (6.6.062)
File: NewInvoice v6.6.062
File: Tag Payment Only Invoices

- Fixed: Improved interpretation of Payeezy error responses for users to see in FrontLine Payment Verification.

- The Payeezy Transaction ID is now shown in Verify Code column of collected card tenders on an order, and the Transaction Tag is shown after the 4-digit card number fragment in the Account Number column.

- FrontLine now records Payeezy Transaction Tag values to use for Tagged Refunds that do not require re-entry of card or cardholder information.
Note that for tagged refunds Payeezy may provide a Transaction ID "RETURN" instead of a new ID.

- Technician (limited) user features have been revised as Technician User of Scheduler & Services.
Now technicians:

- Fixed: 6.6.059 introduced a potential SQL error in Receivables when viewing Closed receivables with customer Group inclusion.

- Fixed: Adding a scheduler event to an existing customer order did not import Mobile Connect (Web) entries linked to this particular event until the next time the target order was opened.

- Fixed: Receiving a batch of backordered items that have identifiers without uniqueness (like a lot number specified at receiving) would use the same identifier document for the sales backorder fulfillments as for the receiving, thus linking their identifiers.

- Fixed: Costing a Transfer where the available cost layers of an item in the source location only fulfill a fraction of the quantity transferred would result in an SQL key violation of primary key constraint PK_TRXINVCOST and incomplete costing results. Similarly when multiple layers in the source location were consumed only the cost from the last layer was added to the cost layers in the destination location with the total quantity.
This fix is in the CostInvoice db procedure.

- Fixed: The Resource Categories and Resource Certifications selections for the Scheduler board can now remember (sticky) selections for the first 64 categories instead of only 32.

- Fixed: Service order line items imported from Mobile Connect should now consider repair unit warranties for both the repair unit line and attached repair parts and services.

- Fixed: In Fast POS mode, FrontLine would commit Unidentified even when inventory was available at the order location.

- Preset Identifiers are now saved to new (unit identifier and line item) identifier documents upon creation, instead of when the user saves the document.
Note that so far this only applies to sales and rentals, and doesn't discriminate on preset application.
Contexts are: Unit added to order, intangible line item added to order, and customer order redo.
A revision to the db procedure SpawnItemDtl is required to accompany the FrontLine desktop executable revisions.

- Payment Verification when using pcauthor now disables "Cancel" until the first timeout.

- Clarified the Item Cost label in Resource Costs to Item Unit Cost, and highlight the Item Unit Cost entry when blank for a miscellaneous line item.

- When a customer order that has been returned is Redone FrontLine now moves the special order references on the corresponding PO to the new order.
Note that if the new order is voided the special order references from the PO do not revert to the first customer order.

- The System Users administration feature now provides colum title click sorting, and a filter for the user list that examines User Name, Real Name, and Return EMail.

The Db Console contains two required updates:
File: SpawnItemDtl 6.6.060
File: CostInvoice v6.6.060

- Fixed: Total shown on a line item after overriding the EstRental (estimated rental) with a custom price on a short term rental would revert to a line total based on the EstRental instead of the new price after the order was reopened or AvaTax calculations were performed.

- Fixed: Warranties shown by clicking the Line # column of a covered unit could include a defunct warranty.
This display bug was introduced in the 6.6.050 revision that added warranty history.

- Fixed: Redo as Quote no longer copies order I.Docs or Customer PO to the new quote.

- Fixed: A recent revision would cause key violations on ESDTL after regrouping Equipment Set members.

- Fixed: Costing a Return invoice of Special Orders should attempt use the special purchase cost.
This fix is in the CostInvoice db procedure.

- Fixed: The EE Custom "Sales Order" output from Forms for Orders should not exclude line items that are On Hold.

- In the Receivables window, the status bar now shows the Selected Receivable Comment when the mouse pointer is within the receivables list.

- When Closed entries are requested, the Receivables window now includes cash tenders as Paid Transactions.
One combined Paid Transaction is shown per invoice, and omitted if the net is zero as in a cancelled tender.

- Order Returns now copy the Job and Job Phase of the source order, and include the Job Budget section of Resource Costs in the return copy.

- The Budget Cost and Variance shown in Job Details are now rounded to 2 decimal places. Rounding is performed before summarizing.

- Customer Orders now assign an estimated "Budget Cost" (BCost or B.Cost) to line items, which is used for budget costing Jobs if no Job Budget Unit Cost was entered in Resource Costs.
Budget Cost uses the item's inventory costing method except for Unit actual costing which uses Average cost, and all default to Standard cost if the specified method yields no result.
When an order is created from a quote, the new order receives the new Budget Costs from the quote, but FrontLine no longer creates Budget Unit Cost values in the Resource Costs of the new order.

Line item Budget Costs are evaluated when:
+ New line items are created.
+ New line items are added from the Copy List.
+ An order is Redone as a Quote (Redo as Quote).
+ A unit is returned without a sale line reference.

Line item Budget Costs are copied when:
= An order is created from a Quote.
= An order is Redone (Redo Order).
= An order is Returned.
= Line items are Returned.

The Db Console contains three required updates:
TRX[IP].BCost (6.6.059) Apply this one first.
File: CommitInvoice v6.6.059
File: CostInvoice v6.6.059
To assign existing open customer order line items BCost values after the Db Console updates use the Set B.Cost on open lines context menu entry that appears with a right-click of the System Administrator indicator.

And here are three MSSQL updates to copy Job/Phase to existing job order returns:

- Fixed: When a Scheduler Event recurring sequence is created from an event that was already linked to a service order the future events created were missing a copy of the original event notes and subject.

- Fixed: Returning an item without identifiers on a rental order where unit identification was not required resulted in a line item flagged as a sales return so rented units could not be committed to it.

- Fixed: Recurring billing items on a return order that have not yet been on a recurring bill are returned at the sale price.

- Fixed: Large Unit Cost values would cause a database error upon PO check-in on MSSQL.

- Fixed: Changing the unit price of a package line with package quantity greater than one would miscalculate taxed value. This was partly fixed in 6.6.057 for unquoting.

- Entering a Credit Card value in Equipment Sets and Customers maintenance when Payeezy is active opens a Cardholder Information window and from there generates a card token to save on file for future use. The token itself is not a usable card number.
The last four digits of the card number and the card expiration date are saved and shown to users, with a color highlight if the expiration date is within a month (yellow) or closer (pink).

- Tokenized credit cards in Equipment Sets are used for recurring bills generated by that ESET, and tokenized credit cards on a Customers record can be used on that customer's orders by entering a hyphen in the Account Number of a new tender line for the order.

- CVV and Name in the Cardholder Information window are now only required when using Payeezy.

The Db Console contains two required updates:
CardHolder (6.6.058) To add CardHolder and CardExpires to CUSTOMERS and ESETS, and ESetID to PAYMENTS
Expand ITEMCOSTLAYERS.UnitCost (6.6.058) To fix large unit cost overflows on MSSQL

- Fixed: The tender collection fix in 6.6.034 could cause erroneous splits on mixed tender orders.

- Fixed: Voiding an assembly collection of lines on a work order did not discard the assembly.

- Fixed: Intangibles sold at rental locations with multiple Periods did not apply the periods to tax calculations.

- Fixed: Unquoting a package with package line quantity greater than one would miscalculate taxes by overstating the package taxed value.

- Location Payment Gateway Merchant is now used per order location instead of workstation location.
Note that a Company "Payment Gateway Merchant" is still required and used by default,
the Company "Payment Gateway Keys" are always required for Payeezy integration,
and the workstation location must still specify Payeezy to enable Payeezy on workstations at that location.

- Fixed: Changing the line item price of a miscellaneous item could fail to refresh the order totals.

- Fixed: A Service Order opened in read-only mode did not present the "Service Order" option in Forms for Orders.

- Fixed: Rented equipment covered by a service contract that is committed for repair while rented could appear twice on a recurring bill.

- Fixed: Manual adjustments of serialized inventory at a rental location could still trigger the Rental Mismatch message Rental Location disagrees with Rental Line Item.

- Fixed: Returning an item by Scan Code where the precision of tax rates was beyond 2 decimal places would initially result in rounded tax rates on the return tax.
This fix is in the CopyLineItems db procedure.

- Fixed: Malfunction when an agent notification email was triggered upon opening an order from a Scheduler Event.

- Fixed: Rental Repairs were removed from Service Contracts. This fix is in the SpawnItemDtl db procedure.

- Fixed: 6.6.055 began showing completed orders in Customer Order Lookup Service Orders for Invoicing.

- Fixed: Improved linking of repair parts and services imported from Mobile Connect.

- Added ability to copy extended identifier documents of repair parts created in Mobile Connect during import.

- Added QuickBooks Receivings Export to the Third Party panel in the Welcome window. This link launches a batch file in the FrontLine program folder named QBRecvExpFLFL.CMD where FLFL is the name of the database in use.

- Receivables posted by Recurring Billing now copy the bill Customer PO to the receivable Comment.

- Cancelling an AR Write-Off now sets the Invoiced date of the cancelled write-off to the date it is cancelled.

- To facilitate having other orders concurrently in read-only view, Order Lookup can now be performed while editing an open order.

- Added security context "Payment Gateway" in the Locations class to control access to location-specific payment gateway configuration.

- Added a "Resource Summary" view to the Scheduler.
The resource summary brings together a participant's events for a week or 5-day period.
Participants are grouped by agent category, using the same color scheme as the scheduler board.
Participants included in the summary are determined by the same resource criteria as the scheduler board.

The Db Console contains two required updates:
File: CopyLineItems 6.6.056
File: SpawnItemDtl 6.6.056

- Fixed: In the Scheduler Event window the Regions revision broke the All agents listed selector, and the agent list could be partly obscured by the region selector.

- In multi-day views (Week and 5 Day) the Resource Region selector for the Scheduler board now filters out events for agents not in the region selected.

- Locations can now override the company Payment Gateway Merchant by entering location-specific merchant information using the P.G.Merchant button.
The "P.G.Merchant" button text is bold when the location has its own merchant information.
The Payeezy indicator in the Welcome window reveals whether the workstation is using the Company or Location Merchant in its hover hint.

- Because the Customer Portal requires unique contact email addresses when FrontLine detects the portal (by presence of the CPUSER table) it now checks that the email address entered for a contact is not used by another portal contact.

- Added a Service Order Order Type to simplify and improve the efficiency of making a distinction between service orders and sales orders.
The Db Console provides a script to set this flag on existing service orders.
Failure to run this script in a database will not result in errors, but FrontLine will not recognize the old service orders as service orders in functions like Order Lookup.

The Db Console contains two required updates:
Expand LOCATIONS.PVT (6.6.055)
File: Service Order Type (6.6.055) If this script raises an error "Cannot insert the value NULL into column OrderType" then first run this one-line update then retry "Service Order Type"
ALTER TABLE ORDERS ALTER COLUMN OrderType int

- Fixed: Manual adjustments at a rental location triggered the Rental Mismatch message Rental Location disagrees with Rental Line Item.

- Fixed: "Invalid floating point operation" under specific circumstances with the C.Cost column shown on a customer order.

- Fixed: Vendor-specific last costs from a primary vendor with no vendor part number were not used.

- Added Payeezy payment gateway support.
To enable Payeezy at a workstation location enter Payeezy in the Locations Payment Gateway.
By default FrontLine uses the live Payeezy gateway host at api.payeezy.com
To specify the sandbox Payeezy gateway set the location Payment Gateway to Payeezy;api-cert.payeezy.com
When a user whose workstation is at this location collects a card tender, the card transaction is submitted to Payeezy.
The Cardholder Information window now requires the cardholder name, and street address is recommended. Before only the CVV and cardholder Zip code were required.
A workstation where Payeezy is enabled shows a light blue indicator on the left edge of the Welcome window.
Two Company Settings are relevant to the Payeezy gateway:

- Added a simple Company Setting Card Tender Fee % to trigger fee reminders to the user, it does not automatically add any fees and only accepts whole number percentages.

- Fixed: A revision in 6.6.046 caused the Tax GeoCode drop-down list on addresses to remain empty, and raised a warning "No Tax GeoCodes found for this address" when saving even when there were matching Tax GeoCodes.

- Fixed: Receivable Statements for a Parent customer did not summarize child customer receivables correctly.

- Fixed: 6.6.047 broke the Line Item Note hover hint pointing position when the Agent column was shown.

- Fixed: 6.6.052 broke the "Purchase From" address section of the Purchase Order window.

- If there is no Invoice, the Updated date output from Forms for Orders for pick tickets is now the Order Updated date.

- Service order imports of Mobile Connect (web) mobile agent (technician) line items now default to the agent's Inventory Location, unless a specific unit is identified in which case the last known location of the unit is used. If neither location is defined then the service order location is used for the imported line location.

- Service order line items imported from Mobile Connect (web) can now be Voided with two different results:
Y: Void the corresponding entry in Mobile Connect. This line item can later be unvoided, which will also unvoid the MC entry.
N: (Previous Action) Release the entry in Mobile Connect so it can be edited by web users and re-imported. This line cannot be unvoided.

- Locations now have an optional Region. Regions are defined in Setup - Lists.

- Added a Schedule Notify flag to Agents to offer an email notification (with iCalendar attachment) upon saving an event in which this agent is a participant.

- Agents now have an Inventory Location to indicate the usual location they use inventory from in the field. This location typically corresponds to the technician's vehicle.
An agent's inventory location implicitly defines the region an agent (technician) operates in.

- Scheduler Events now require a Location before saving.
If the primary participant is added when the event has no location specified then this agent's location is assigned to the event.

The Db Console contains three required updates:
WEBxyz.LineStatus/Create/EditBy (6.6.053)
AGENTS.LocationID (6.6.053)
LOCATIONS.Region (6.6.053)

- FrontLine will no longer modify report column labels that contain spaces from the SQL query.

- 6.6.040 output of bare LocationID from Forms for Orders is now also done for Recurring Billing Output.

- Added source location and location ExtRef values to outputs from Forms for Orders:
LocationExtRef (corresponds to LocationID)
SourceLocation (bare ID for transfer orders)
SourceLocationExtRef (corresponds to SourceLocation)

- The sold-to icon is no longer shown in the Attributes column of the address list in customer maintenance.

- Customer Info Sheet can now be opened from a Customer Identifier Document window for side-by-side use.

- The To Be Scheduled Task List in the Scheduler can now be exported, and sorted by clicking the column titles.

- The Contract Assignments window now includes the order where the contract was sold, and provides a link to view that sale order.

- The -36 Month, -48 Month, and -60 Month billing frequencies now have a leading hyphen by default so they do not show up in the drop-down lists.

- Order and Line Item tax values recorded from AvaTax responses now use "totalTax" and "tax" instead of "totalTaxCalculated" and "taxCalculated" per AvaTax record-keeping.

- Added a Line Item Sorting facility. Line items can be viewed By Line Number or Customized Line Order. When a service order is first plnaced in Customized Line Order it is equivalent to the previous option to Sort Service Orders by Repair Equipment. If the order can be modified, the user can switch to Line Sort Mode and then drag and drop lines into new positions.
Most line editing features are disabled in Line Sort Mode.
Package members are moved together with their package line.
Orange cues are used to clarify activity in Line Sort Mode.
The line (or package group) picked up to move is highlighted in orange across.
The line (or package group) just moved is highlighted in orange only in the leftmost column.
When custom sorting has been activated for the order an indicator appears Order has been custom sorted. Clicking that indicator offers to remove the custom sorting.
In Forms for Orders the Sort by Line number option is now available for all forms. If turned off the output is sorted in the Customized Line Order.

The Db Console contains two required updates:
TRX[IP].LineSeq (6.6.052) Apply this one first.
File: CommitInvoice v6.6.052

- Fixed: A recent revision caused an access violation in Generate Purchase Order the first time it was run after logging on to FrontLine if the Vendor had already been assigned in the Purchase Order window.

- Fixed: The 6.6.049 revision to warranty package members on warranty vendor invoices incorrectly warrantied other attached parts or service lines that had been marked by the user as not covered under the warranty. This fix is in the NewInvoice db procedure.

- Fixed: Users should be able to void Quotes based on a Delete permit on the Order Quote security context rather than the main Orders permit.

- Fixed: Changing to $0 the automatic shipping charge line just added by shipping from the order window did not record the new order total.

- Fixed: Line Item tax values recorded from AvaTax responses now use "taxCalculated" instead of "tax" to avoid potential rounding discrepancies in the AvaTax results.
The "tax" value can be from a client override, but FrontLine does not override AvaTax calculations.

- Added an option to the Scheduler to show the To Be Scheduled events (Task List) in full Window. Closing the window restores the scheduler board.

- Added two entries to the label translator to help with column names of Motorola Sales View reports. Note that the names are completely lower case:
motodcn "Dealer Motorola Customer Number"
motopeci "Partner to End Customer Invoice"
These do not work if translation is disabled via a leading {} in the query.
Note that in 6.6.063 this indicator became [] to make it distinct from code interpretation.

- Periodic Invoices now provide an optional Location criteria for the batch. The order locations are matched, not line item locations.

- After the unit warranty of a repair unit on an open service orderis modified FrontLine now offers to adjust the warrantied status of all applied repair part and service lines.

- Unit Warranties now keep a history of their application as a unit of equipment moves through transactions. For example, if a unit of equipment was given a warranty at time of sale, then when repaired the warranty is revised, both of these warranties are now kept on record. In other words, after the repair it can be shown that the warranty was AAA at the time of sale, and then became BBB at the time of repair. Unit Tracking now shows expiration dates of these historic warranties.

- Service Contracts now keep a history of their application as a unit of equipment moves through events, similarly to Unit Warranties. Additionally, when users add or remove units from a service contract a record is kept of these changes.
Note that both of these revisions are breaking changes to FrontLine data and programming.
History prior to these changes is not available unless filled in with estimates by a separate process.
Contract assignment history can be viewed using the context menu entries in the Service Contracts window.

The Db Console contains five required updates that are NOT backwards compatible:
XRDTL++ (6.6.050) Apply this one first, one line at a time, then the other four in any order.
File: SpawnItemDtl v6.6.050
File: CommitInvoice v6.6.050
File: ITEMDTL.Delete (6.6.050)
File: NewInvoice v6.6.050

- Fixed: Exporting Inventory Valuation when the results include many thousands of details that have to be filtered out for each export row resulted in unacceptable slow exports.
Now when the Details checkbox is unchecked the Export no longer offers inventory detail fields, and when the Details checkbox is checked and the row count is high FrontLine asks if details can be omitted, so the export process handles rows quickly even with large primary data sets.

- Fixed: Due dates output from the PAYMENTS data set from Forms for Orders should be based on the invoiced date instead of the tender collection date.
This also applies to Recurring Billing Output.

- Fixed: Adjustments created from committed Physical Counts sheets should use the physical count location Ship-To address instead of the SELF entity purchase from address.

- Fixed: When a Scheduler Event is added to a new order, the order location is also set to the event location instead of the workstation location. Previously only the line location was set to the event location.

- Fixed: Users with only a Read permit for "Transact Unidentified" could not select "Unidentified" from the Scan Match window when it appeared after Item Lookup.

- Fixed: Users with a Modify permit for quotes but not orders could not add lines to the Copy List.

- Fixed: A recent revision broke the order total refresh after an open order is shipped and a shipping charge is added automatically.

- Fixed: Changing an order's ship-to address by typing into a ship-to address field set the order ship-via to the customer's ship-via instead of the new ship-to address's ship-via.
The customer's ship-via is still used when the ship-to address has no ship-via of its own.

- Fixed: Warranty Vendor Invoices did not consider order location when seeking vendor-specific price levels. This fix is in the NewInvoice db procedure.
Note that if location-specific warranty vendor invoices are used for a warranty vendor then no price level for that specific vendor should apply to ALL Locations.

- Warranty Vendor Invoices did not include package members when a package was assigned to a repair as a repair part. This revision is in the NewInvoice db procedure.
Note that packages should only be assigned as repair parts in Package First mode.

- Fixed: Removing an event from the Scheduler board did not remove the possible line item reference to the event.
FrontLine now informs the user of the line information in the removal confirmation, and indicates that the user must void the line item themself if desired.

- Fixed: The Shipping Charge Calculators miscalculated percentages on partially invoiced orders.

- Added a VendorName output from Forms for Orders for customer orders that corresponds to the VendorNumber output.

- Implemented a 36 Month (3 year), 48 Month (4 year), and 60 Month (5 year) billing frequencies.
The database field [BillFreq] values are 8448, 8704, and 8960 respectively.

- Forms for Orders output to both forms and Excel sheets using the Print Order I.Doc option, added a LineUIDocname1 to the existing OrderUIDocname, RepairUIDocname, BillToUIDocname. ShipToUIDocname, and EntityUIDocname.
Unlike the other accessory documents, there can be multiple line items, and multiple units per line. LineUIDoc outputs them all, sequencing the names with numbers that begin with 1.
For example, if there are three color identifier values on the line items and units, they would output to labels with these names:

- Added Delivery Status Undeliver to the Third Party panel in the Welcome window. This link launches a Python file in the FrontLine program folder named DeliveryStatusUndeliverFLFL.pyw where FLFL is the name of the database in use.

- Fixed: Adding repair parts to a Service Quote did not trigger the repair unit assignment menu.

- Fixed: Checking in warranty repair equipment back from the vendor on a Warranty PO should not affect item last cost, average cost, or costing layers.
This fix is in the CostInvoice db procedure.

- The Warranty V-RA indicator on Items and Orders is now Warranty PO and Warranty Vendor Return Authorizations are Warranty Purchase Orders.

- The email address helper list now includes the contact category, if applicable.

- The Edit Definition context menu entry in Reports now only appears for administrators.

- Non-AR orders are now exempt from the Isolated company setting for Constrain Payments.

- The workstation configuration file parameter WS= on the command line can now contain a %s token that FrontLine replaces with the Windows user name.
For example, WS=C:\Ormandy\FL\WSFiles\FL%s.CFG will use file name C:\Ormandy\FL\WSFiles\FLjohn.CFG when Windows user John launches FrontLine.
This enables the same shortcut to be used by multiple users with workstation configuration files in non-private folders.

- If FrontLine is used in a remote desktop session where the RDP client has given the session access to local storage, and the client PC has a local folder C:\Ormandy\FrontLine then after writing any of the following files FrontLine will ask the user if they want a local copy of the file:

The Db Console contains a required backwards compatible update:
File: CostInvoice v6.6.048

- Fixed: The Remove Payment function failed to create the On Account 'Substitute' to remove a negative tender, as on return order.

- Fixed: Changing the primary participant of a scheduler event linked to an order line item changed the line item Agent, but if the order was concurrently open with the scheduler this change did not appear in Line Item Details until the order was deferred and reopened.

- Fixed: Changing an open order location with Company Setting Location for Item Category Accounts set to Order Location now updates all open line item accounts that haven't been custom set by a user.

- Fixed: Changing an open service order into a service quote would save the repair unit identification but the repair unit identifiers were not shown in the quote's Line Item Details until it was deferred and reopened.

- Fixed: Clicking the ready checkbox of an assembly line item on a work order did not receive the assembly.

- Fixed: Invoking Transaction Inquiry from an order line item included transactions from other customers upon retrieval.

- Order entry line items now have a line Agent column to view and set line agents without opening Line Item Details.

- Added a drop-down menu to the Zoom function in order entry with new options to Hide Voided Lines and Hide Line Agent.

- Added a Redo Order as Quote next to the Redo Order function. "Redo Order as Quote" does what "Redo Order" does for customer orders except the result is a quote and no units are committed. A user must have an Add permit for both the "Order Quote" and "Redo Order" security contexts to Redo Order as Quote.

- The Info Sheet window now floats with the customer order and customer maintenance window so that it can stay in view while a user works in the other window. When the customer goes out of context the Info Sheet window should close itself.

- The Item Status flag Simple PO Cost introduced in 6.5.003 now gives precedence to the non-location standard cost over location last cost.

- Added to Company Setting Notify Options an option to Confirm opening web URLs clicked in Equipment Search and Reports.

- Item Cost in Resource Costs now only allows positive values, and returns no longer negate this value.

- If the location of a short term rental order is changed to a non-rental location the Periods and Est Rental columns now remain visible for the line items.

- Upon making an order a short term rental when the order's location is non-rental or blank, FrontLine now only assigns the workstation's Rental Location, if the workstation rental location is undefined FrontLine no longer assigns the first rental location it finds among all the locations.
To assign all workstations with no Rental Location to the first rental location use this SQL:

- For addresses, the State entry can now be up to 8 characters long, and is not forced to upper case for Caribbean Netherlands and Curação.

- Fixed: A recent revision broke launches of the FrontLine executable from a UNC path that uses an IP address.

- Fixed: Physical Count now only requires an identifier for items that have identifiers required at receiving instead of items with any identifiers.

- The Copy List feature now has checkboxes to select multiple entries to copy, and a corresponding Add Selected button.
In an order, Ctrl-Y is now the shortcut to add the current line to the Copy List.

- If FrontLine is launched with no INI file parameter it now provides a Company selector at the logon window that gives a choice of INI file configurations that contain CO= descriptions.

- If FrontLine finds no Task Bar on the desktop it now removes the Minimize option from most if its windows.

- Added "Caribbean Netherlands" to the built in country list, using TLD bq and telephone country code 599.
Telephone country code +599 is shared with Curação.
Note that Caribbean Netherlands is the same country as the former Netherlands Antilles, which has TLD code an.

- Fixed: Rental line items that used Periods to calculate the line total did not use the periods to calculate taxes.

- Added a MultiValue identifier property in Setup Identifiers.
Identifier Value List entries for MultiValue identifiers can be entered as Key=Value pairs to fit more entries in a single identifier text.
Typed input is also accepted when editing multi-value identifiers, as a list of values separated by commas. Each value typed in can be a partial match to the start of the key or value.

- The SUMS output from Forms for Orders now includes list price totals as SUMS.TotalList and SUMS.QuoteList

- Quote outputs from Forms for Orders now include options to output line item identifiers.
Note that these are not unit identifiers, because no units are committed to quotes.

- Clicking http(s) URLs output in a diagnostic report now open pages in the default browser after confirmation.

- When the Subject of a recurring Scheduler Event is changed FrontLine now asks if the subject of later events should also be changed.
Only subjects of events that are not yet attached to order line items are updated.

- Fixed: Item Action prompt could appear when transferring to a rental location.

- Fixed: Access Violation could occur upon starting a Transfer order in purchasing.

- Fixed: A recent revision caused a stack overflow upon adding a recurring billing line item to an order.

- Clicking http(s) URLs output in Equipment Search now open pages in the default browser after confirmation.

- Periodic Invoices for Vendors now assign one of the vendor customer's unexpired Blanket POs (if any) to the periodic invoice INVSUM.CustomerPO

The Db Console contains a backwards compatible update that should have been included in 6.5.054:
Expand PVIDS.CustomerPO (6.6.043)

- Fixed: 6.6.040 output of bare LocationID from Forms for Orders broke output of LineLocation.

- Fixed: 6.6.032 fix for contacts at destination location of purchase orders broke the ship-to contacts for drop-shipped purchase orders.

- Added a Copy List to copy and paste line items on customer and purchase orders. Exchanges and repairs cannot be copied. Lines copied from customer orders cannot be added to purchase orders, or vice versa.

- Purchase orders created by workstations in Canadian locations are no longer made tax exempt by default, despite SELF having a tax exempt category or exempt code. Users can exempt the order if desired.

- Fixed: 6.6.039 broke manual price overrides of rental line items on customer orders.

- Fixed: 6.6.039 broke manual recurring pricing changes to Rental members of Equipment Sets.

- Identifiers Setup now includes a RxClr (Clear on Repair) identifier flag to complement the existing RClr (Clear on Return) flag.
The behaviour of either is that when a unit whose identifier document template contains identifiers with this flag is accepted for Repair(RxClr) or Return(RClr) the unit is given a new identifier document with those flagged identifier values removed. The identifiers on the new document can then be modified without affecting the equipment identifier document contents on preceeding transactions.

- When Return Next Scan is used in order entry substitutes are not considered so that non-identifiable units of discontinued items can be returned or repaired.

- For Miscellaneous line items Job Cost now uses only the Item Cost entered in Resource Costs.

The Db Console contains two required updates:
CommitInvoice v6.6.041
SpawnItemDtl v6.6.041

- Fixed: In company settings for Discount Presentation, Quantity Repricing, Cost Pricing, Line Accounts when Location for Item Category Accounts - Revenue and Cost of Sales was set to Order Location FrontLine did not keep custom accounts on line items flagged Custom Accounts Assigned (CAA) when the order or line location was changed.

- Fixed: The 6.6.038 revision to put line items created with input from the Package Recall feature at the recall location regardless of the current order location should not apply to Transfer Orders, transfers should move to the destination location.

- Fixed: The Package Recall feature is now better at forwarding available accessories to commit from the exact package receivings where non-identifiable accessories were received in fragmented quantities.

- Forms for Orders now has a Bottom Margin override capability for forms output. The value entered here can be used to adjust the bottom margin designed into a form to change the flow of output between pages. If the Apply Bottom Margin Override option is active when Forms for Orders is closed then FrontLine saves this margin value for the particular order.

- Forms for Orders now outputs the order LocationID as a bare LocationID instead of location ExtRef and Name text.

- The Import Quote feature now has a sticky option to Create line item notes if stock item has no description instead of the default behaviour to create line item notes for all lines.

- Order Totals now has Non-Commissionable and Commissionable total rows below the main Total.

The Db Console contains a required backwards compatible update:
ORDERS.PageMargins (6.6.040)

- Fixed: Special ordered and backordered items that were automatically committed to the customer order upon receiving were committed to the Bill-To customer instead of the Ship-To customer, giving incorrect ownership when the customer orders had a redirected Bill-To.

- Fixed: Units committed to repair on an Inventory RA (I-RA) were committed at the order location instead of the unit location when company setting Repair Units in Order Location was selected.

- Fixed: In some circumstances the Price Levels Quick Add feature could generate records that resulted in a primary key violation of the PRICELEVELS table.

- Fixed: A user without the Delete permit could cancel a Physical Count sheet if they opened it by specifying identical criteria for a new sheet.

- Fixed: After using an Inventory Complete order lookup FrontLine could start throwing access violations.

- Fixed: Redo of a Cancelled Quote should not copy the cancelled status to the new quote.

- Fixed: Inventory Valuation did not consider backdated invoices as the event date for inventory movement.

- Fixed: Costing of transfer orders would consume from the source location but not add to the destination location.
This fix is in the CostInvoice db procedure.

- Fixed: Could not open for viewing another user/agent's order from Order Lookup Mode with read-only access to other's orders.

- FrontLine will not raise the WorkStation Computer Name Changed notice on AppStream.

- After sending email from Recurring Billing Output using eMail All FrontLine will no longer ask the user "Did the bills print successfully?" before marking the batch as sent to recipients.

- Last Cost determination for Purchase Order line items is now location-specific instead of most recent cost in any location. Changing the location of an open PO line now resets the cost for the new location in compliance with the Repricing after Location change option in Company Setting Discount Presentation, Quantity Repricing, Cost Pricing, Line Accounts.

- When a Vendor Catalog item with price levels on a customer order has stock (or unidentified units) committed to it by a user FrontLine will no longer ask "Fulfilled from Stock?" before removing the vendor catalog flag on the line item.

- Added a Rental Price Levels entry feature (right-click the Price ellipsis button in Items maintenance) where rental rates can be set for an item at various locations for different periods of fixed days, or Variable to set a default billing rate for bill frequencies like months, quarters, and years.
FrontLine provides notices and highlights of prices that are higher per day for longer periods.

- FrontLine now uses the rental price levels to assign default billing rates for rental items on recurring billing equipment sets if the rental price level has an exact match for the bill frequency.

- Added an Est Rental display column to line items in order entry. This column only appears when the Periods column is shown.
A database update is required.
Forms for Orders output this value as EstRental

If the line item has rental price levels on file, Est Rental shows the price for the number of days entered in Periods, by fitting the line item period into the largest priced periods.
If an item has rental price levels for Daily, Weekly, and 28 Day, here is how various periods would calculate:

The Db Console contains three required backwards compatible updates:
TRX[IP].EstRental (6.6.039) Apply this one first,
File: CommitInvoice v6.6.039 this one second.
File: CostInvoice v6.6.039 Don't forget this one.

- Fixed: Purchase suggestions for items qualified only by Resource Costs Vendor (the item does not have the default vendor or parts vendor chosen) by auto-gen in the Generate Purchase Order window should only be considered for customer special orders.

- Fixed: Line items created with input from the Package Recall feature should all be at the recall location, regardless of the current order location.

- When FrontLine makes a local copy of itself from a shared folder launch, it now also copies the database client libraries (ntwdblib.dll or libpq.dll) and OpenSSL libraries (libeay32.dll and ssleay32.dll) to further reduce the chance of an External Exception C0000006.

- Updated the FedEx integration window trigger for the Ship Manager "Lookup Value" from Shipping to work with Ship Manager version 31.

- In Contacts maintenance the list of contacts now has individual note indicator icons.

- Added an optional Payment Verify Terminal to Locations to override the Current Station "Terminal" of any workstation at that location.
When set per location it is not necessary to set the "Terminal" per workstation.
This revision requires a db update.

The Db Console contains a backwards compatible update that must be applied before standard users can log in:
LOCATIONS.PVT (6.6.038)

- Fixed: Line item identifiers entered for intangible items did not appear on completed orders.

- The last line item modified by the user highlight is now bold text in the leftmost (Line #) and rightmost (Total) columns instead of the gray horizontal border.

- Added an option to specify on the launch command line a file to use for workstation configuration. Example targets:

- Fixed: Customer "Account" was not assigned to On Account tenders that the user did not specify an override account for.

- Fixed: Shipping should not require customer orders to have a TaxGeoCode when using AvaTax.

- Fixed: After shipping a warrantied repair unit to Depot, choosing Warranty from the context menu of the Selected Items list in Line Item Details would open a blank warranty, thus allowing users to add a duplicate warranty that would cause PK_WARRANTIES key violations when the service order invoice was committed.

- Fixed: Address validation submissions to AvaTax from maintenance failed to add a hyphen to Zip+4 entries.

- The last line item modified by the user is highlighted with a dark gray horizontal border.

- Fixed: Purchasing check-ins with AvaTax would raise an AvaTax error when committed or cancelled.

- The Write-Off Date entered in Receivables is now assigned to the write-off records [Applied] date as well as [Invoiced] date, and the Applied list now shows the write-off posted date instead of the invoice posted date. If the user gave no date override then [Invoiced] is left blank and [Applied] is the date and time of the override. [Posted] is always the date and time of the override.

- Fixed: Checking out a mixed (sale and return) customer order tendered by card or On Account with the invoice total more negative than the card/account tender balance should now split the balance on card/account into a positive and negative tender.

- Fixed: Adding a warrantied repair unit to an open service order after adding repair services and parts, then assigning the repair services and parts to the repair unit, could fail to apply the warranty to the services and parts.

- Fixed: A Tax Report for a period with new Tax Write-Offs against earlier period invoices would fail to include these Write-Offs. This bug only affected MSSQL databases.

- When the interface to AvaTax cannot successfully decode the transaction results it now offers to retry the submission.

- Fixed: While fixing a potential Access Denied error, 6.6.032 introduced a bug generating the email attachment file name that repeated the folder path.

- Fixed: The Import Quote feature can now handle hard line breaks in description texts, double-quote doubling, and adds Desc3 to created items.

- Fixed: Reports using .rep Forms should not be fussy about printer capabilities before the user has instructed FrontLine to print the output.

- Fixed: Redirected Bill-To for Recurring Billing was ignored when the equipment set had a Residence assigned to the Ship-To of the bill using the new company option Bills use ESet Residence as Ship-To introduced in 6.6.030

- Fixed: The Ship-To Contact list on Purchase Orders did not list contacts at the destination Location.

- Fixed: When there are Closed Locations on file, the default Return Order Location selected in the Returns might not be the default workstation location.

- Fixed: Upon creating a new Bank Deposit with a batch identification text, FrontLine would display a bogus confirmation date in the order's deposit label.

- Fixed: The Budget Cost summaries shown in Job Details in the Jobs window could double, and thus also miscalculate Budget Variance.

- Fixed: The Import Quote feature did not handle blank unit prices. It now considers them a zero price on the quote line.

- The Import Quote feature now puts the full worksheet Description into the created line item note body, and stock item note if a stock item is created.

- In order entry Return Next Scan is now available even when Isolated Returns is selected in company settings. Note that use of AvaTax effectively turns on Isolated Returns.

- Purchase line items created by auto-gen in the Generate Purchase Order window now use the company Line Increment instead of always 10.

- Added to Generate Purchase Order a sticky option to Copy Customer Special Order Line Notes to the purchase line items created.
Note that PO line items created using this option cannot have demand notes.

- Added an optional AvaTax Company Code per Location. When submitting transactions to AvaTax, if the location of an order or recurring bill has a Company Code specified then FrontLine will submit the transaction to AvaTax using this code instead of the Company Code specified in the AvaTax Configuration of FrontLine Company Settings.

- To extend the reach of the Import Quote feature to purchasing, for customer special orders that trigger auto-gen in the Generate Purchase Order window:

- Fixed: When an alternate ship-from address is submitted to AvaTax for a line item because the line location is not the same as the order location, FrontLine must also submit the ship-to address for the line item because AvaTax will not use the order ship-to address if any alternate address is specified for the line.

- Revised Date submission to AvaTax:
Invoices dates (whether default or user-modified) are submitted as the Doc Date.
Recurring Bills have the Issued date (if specified, otherwise the current date) submitted as the Doc Date.
Invoices of an Order Return have the original order latest invoice date (or original bill issued/placed date for recurring bills) submitted as a Tax Date override.

- Added to Company Setting E-Sets, Rentals, Contracts a new option to have Bills use ESet Residence as Ship-To vs the default behaviour where Recurring Bills have no Ship-To.
This option affects taxes on recurring bills when equipment sets have a Residence address assigned. Note that equipment set member residences are not used.
> For AvaTax users, this residence is then submitted as the ship-to address of the bill for tax calculations. If it is blank then the bill-to address of the recurring bill is sent as the ship-to.
> For non-AvaTax users, the tax geocode of the recurring bill is now from the ship-to address of the bill (which came from the e-set residence), or if that is blank then it is from the bill-to address by default as it has done before.

- Added logging of conversations with AvaTax.
Log files are saved in %LOCALAPPDATA%\FrontLine\AvaTax
Every day uses a different log file, named AvaTaxLog_yyyymmdd.txt
Only conversations for transactions that are recorded in AvaTax are saved.

- Fixed: When using AvaTax, order totals shown in the customer order window did not include order discounts.

- FrontLine now sets the Applied date of an AR credit created during check out of a return order.

- FrontLine now submits a Tax Override Date to AvaTax for:
> Return orders when the original sale order is linked (Return)
> Invoices where the user changed the invoice date (BackDate)
> Recurring Bills where the Issued date is not the date the bill was created (Issued)

- For Tax Exempt customers including SELF, FrontLine now only requires a tax Exempt Category or an Exempt Code, not both.
Note that with AvaTax an Exempt Category may not qualify all item tax categories as non-taxable in some jurisdictions.

- Added an Import Quote feature to the drop-down near Quote for customer orders.

- Fixed: 6.6.026 introduced a bug that disabled proceeding between steps of Recurring Billing at some sites.

- Fixed: Budget summaries per Job and Job Phase were omitted from the Job Details view in Jobs.
Note that budget quantity summaries will assume zero quantity for a line item when neither budget quantity nor budget price has been entered for the line item, but if a budget price was entered with no budget quantity it will assume a budget quantity of 1 for that line.

- Added a Disable Address Validation option to AvaTax Configuration in Company Settings to prevent addresses added or revised by users from being sent to AvaTax for validation.

The Db Console contains a backwards compatible update to fix a potential error on check in of large adjustments.
Note that this revision only applies to MSSQL Server, not PostgreSQL where v6.6.023 is fine:
File: CostInvoice v6.6.027

- Added a Use AvaTax Sandbox option to AvaTax Configuration in Company Settings so the sandbox can be used by any company.
Added a Remove AvaTax Configuration function to AvaTax Configuration.
AvaTax Configuration is now tied to the database name so that a database copy will not accidentally post to a live AvaTax account.

- Added an indicator to the Welcome window near the transactions links when AvaTax is in use.
Clicking the indicator reveals the AvaTax Company Code and options.

- Fixed: The Location selector in Equipment Sets and Returns included Closed locations.

- Fixed: Using Specify Days in a Scheduler Event would upon saving the event incorrectly claim that Recurrence days must be after the launch date.

- Fixed: Return orders with On Account AR credits did not break down the credit to the reduced check-in amount when only part of the return order was checked in.

- Importing web labor, parts, and repair units will no longer tag records with a blank ItemID because it cannot create corresponding line items without an ItemID.

- FrontLine now replaces bare line feeds in database error messages with CRLF pairs when adding them to error report emails.

- Added support for external tax calculations using AvaTax. Implementation is not complete yet.
There is a new Company Setting AvaTax Configuration to enter three key pieces of information.
This integration is tied to a customer's activation key and is only available for one customer at this time.

Code	Exempt Reason	Note
A	Federal government	US only
B	State government
C	Tribal government
D	Foreign diplomat
E	Charitable organization
F	Religious or educational organization
G	Resale
H	Agricultural production
I	Industrial production or manufacturers
J	Direct pay permit
K	Direct mail
L	Other or custom
N	Local government	US only
P	Commercial aquaculture	Canada
Q	Commercial fishery	Canada
R	Non-resident	Canada

The Db Console contains two backwards compatible updates:
JOBS.CommissionPaid
Expand TRXRESOURCE.BudgetUnitCost (6.6.025)

- Fixed: Transfer orders with a destination location what was created in FrontLine could end up with a bogus Bill-To address that is only seen in the transfer Check-In.

- Fixed: Changing the customer of an open order from one tax exempt to another exempt customer did not update the order tax exempt category.

- Fixed: Invoking Transaction Inquiry from an order line item gave unexpected results from changing the inquiry criteria afterwards.

- Fixed: Under some circumstances the order Job Phase list fail to refresh after a job order was deferred.

- Fixed: Batching of a Tax Report included Tax Write-Offs from earlier batched outside the reporting date range when the user chose to merge overlapping batches, and Tax Write-Offs later than the report date range could be included because the batching examined the invoice date instead of the write-off date.
This bug was introduced in 6.6.019

- Fixed: FrontLine raises a warning before checking out a customer order with inventory is received but not yet checked in, however such line items that were unit costed could end up using the cost determined for the prior line item.
This fix is in the CostInvoice database procedure.

- Job Details analysis in Jobs now excludes repair unit line items and depot lines.

The Db Console contains three required backwards compatible updates:
File: TRXTAX.ReceivableID (6.6.023) (contains two steps)
IX_TRXTAX_TaxRpt (6.6.023)
File: CostInvoice v6.6.023

- Fixed: Inventory Valuation failed to use location-specific standard costs, and the unit Details omitted "Committed, Shipped" and inventory sent to Depot.

- Fixed: In Receivables the Applied list omitted payments made by the parent entity.

- In Receivables the Applied list now includes entries where the credit selected above was applied to another receivable.
These are highlighted in the bluish green color for distinction, and show the DocType, Invoiced, Posted, and OrderID of the receivable listed.
Previously the Applied list only showed credits and debits applied to the receivable selected above.

- In Identifier Document History the Value and Edit columns share the extra space when the window is enlarged.

- When FrontLine costs the check-in of a PO or Transfer it now includes services and charges.
Services and charges are excluded from landing costs calculations, and do not record information in ITEMCOST and ITEMCOSTLAYERS.
Part of this revision is in the CostInvoice database procedure.

- Added a Find Launch Event function to the context menu of the Scheduler Board.

- Added a List Event Recurrences function to the context menu of the Scheduler Board to list all events in the recurring sequence, and open one if desired.

- Scheduler Event Lookup now has a special Search By Recurring Completed to Create to find completed events with recurrence plans that may need to be unrolled into the database by creating a new recurring event series.

- FrontLine Images (the internal image viewer) can now decode PNG and GIF image formats in addition to JPEG and BMP.
And double-clicking the image now toggles between the actual image resolution and scale to window size.

- Fixed: Saving a Scheduler Event with an invalid Start date could place an event in year 1899.

- Added security context "Recurrence Plans" in the Scheduler class to control access to recurrency.
ADD allows users to create recurrency for a new or existing event that has no recurrency plan yet.
MODIFY allows users to change the recurrency plan on a scheduler event.

- Adding a line item note to a line where the item has no description now brings the note subject to the line description on screen directly upon closing the note.

- The FrontLine Licenses In Use list now shows the database a user running this revision or later is connected to.

- Fixed: Tax Write-Offs that were in an existing tax report were not included in a new Tax Report when the report dates overlapped and the user chose to merge the batches.

- Fixed: Job Details omitted an entire order when that order was returned even if some lines were not returned.

- Fixed: Scanning a part for a quote with no inventory on hand did not offer the Sell Item Action.

- Fixed: The Receivable Balance shown at the top of the Receivables window did not include tax write-offs from credit memos.

- Fixed: Cancelling a tax write-off using Unapply in Receivables failed to remove the tax details of the write-off.

- Fixed: Job Details analysis in Jobs ignored the line item's Job Phase if the line item's Job ID was not explicitly set, and excluded line items that had been special ordered on a PO.

- Fixed: Following up with the fix in 6.6.017, Provisioning Service Contracts of type "Flat Billing Rate" bill at Quantity 1 with or without consumed meter readings.
Entering meter readings for such contracts now shows a notice with default to cancel.
Flat Billing Rate can now be toggled for service contract set members.

- Fixed: A recent revision caused an SQL error in Scheduler Event Lookup when using Incomplete Past Events or Unassigned Past Events.

- Scheduler Event Lookup now has a special Search By Recurring Open to Unroll to find recurring events that need to be unrolled into the database.
Recurrences cannot be unrolled using a database script, this must be done in FrontLine for open recurring events created in earlier revisions.

- Scheduler Event recurrence expiration (Until date) is now required to be within ten years.
FrontLine asks for confirmation if the recurrence will create more than 40 events,
and will object to creating more than 200 events in one sequence.

- Recurring Scheduler Events are now unrolled into multiple events in a sequence in the database.
In other words, the recurrence plan is unfolded into a tentative reality of actual events.
Some considerations are:

- Order Location Note is now offered as one of the Trailer Notes in the output of Forms for Orders.

- Added a LocationAddress field to custom Reports output if the primary query outputs a LocationID column.

- Step 2 Exceptions and Batch Review in Recurring Billing now reveals equipment sets with members created from orders that are still open.
These equipment set members are not billed in case the order or line items are voided. The order can be viewed using the context menu.

- FrontLine database error emails now use CRLF pairs instead of bare line feeds.

The Db Console contains a required update:
CALEVENTS.EventOrigin (6.6.019)
Although the addition of EventOrigin to CALEVENTS is backwards compatible, after a site has been using the Scheduler with the new Recurring Scheduler Events scheme they cannot revert to a FrontLine version older than 6.6.019

- Fixed: FIFO and LIFO costed items did not appear in the Costing preview that is available before an invoice is completed.
This revision is in the CostInvoice db procedure.

- The email address helper is now available for Packing Slips produced from Shipping.

- The Primary Participant can now be changed in the Scheduler Event window, and all participants can be removed from the event using the new Participants context menu.

- Fixed: Metered Provisioning Service Contracts billed with no new meter readings before the bill date now appear on the bill with a zero Quantity instead of 1.

- The Bin field in Items maintenance now shows the bin at the workstation location in italics if the default bin is not set.

- Restored ability to Special Order the remainder of a line item quantity in Line Item Details after inventory has already been committed for part of the quantity.

- Fixed: In the Scheduler, changing the View Days from Single Day to multiple days after selecting a single other agent in Resource Selection then creating an event would incorrectly assign the event to that other agent.

- A confirmation is now shown when the user attempts to remove the special order flag from a customer Special Order line item that already has a special purchase created.

- The Address Replacement prompt now has no default. The user must deliberately choose between address CORRECTION and REPLACEMENT.

- Added multi-currency output to Receivable Statements. Aging summaries are now broken down by currency and exchange rate.
To use currency formatting output, forms must specify "Data type" Currency for monetary expressions, and leave the "Display format" blank.

- FrontLine now attempts to auto-commit from general inventory qualified package members of a recalled package configuration where the specific unit recalled is no longer available for sale.

- Added Image Folder to Locations. FrontLine looks in this folder for field and repair images, and if defined this folder is also expected to contain item stock images, replacing the ItemImages folder within the Templates folder.

- Added a Image function to Scheduler Event window to show images uploaded on FrontLine Connect for that event.

- Line items created from a scheduler event now include images uploaded on FrontLine Connect for that event.

- Multiple stock item images are now supported by extending the file name scheme to ItemID#########*.jpg
where the # are exactly nine digits and the * wildcard allows optional descriptors in the file name for additional stock images.
FrontLine's internal image viewer can only decode JPEG images, and will not open files larger than 8 MB.
This revision requires a db update.

- The Motorola Sales reporting vendor option Special Reporting introduced in 6.6.010 moves from [VendStatus] value 1048576 to a new field [Reports] value 1.
The option checkbox appears as before in Vendors maintenance.
This revision requires a db update.

The Db Console contains two required updates:
LOCATIONS.ImageFolder (6.6.016)
VENDORS.Reports (6.6.016)

- Fixed: The "Recently Completed" special lookup for orders excluded closed service orders that had been marked Serviced or Ready.

- When Company Setting Invoice Vendors for Warranty Services in Returns, Repairs, Unidentified is turned on, a Unit Warranty now requires a Vendor to make a Warranty Vendor Invoice possible.

- The main datasets from Forms for Orders for customer orders now include a SpecialPO output to show the purchase OrderID (PO) where this special order line was ordered from a vendor.

- The SUMS output dataset from Forms for Orders now offers outputs OrderDiscount and TotalTaxes and for quotes QuoteDiscount and TotalQuoteTaxes.
The TotalTangibles and TotalQuoteTangibles outputs now exclude the order discount.

- Line item Location can now be changed after the order has been invoiced if the line has not been invoiced.

- Web Parts import from FrontLine Connect now uses customer pricing from price levels.

- It is now possible to set a zero Quantity on open line items that are not repair units. Zero Quantity lines:

The Db Console contains two required updates:
File: NewInvoice v6.6.015
File: CommitInvoice v6.6.015

- Fixed: FrontLine would apply the date range previously entered for the Job List when the dates are no longer shown.

- Fixed: FrontLine failed to prorate returns of recurring billing equipment set members that had not been sold in FrontLine.

- Fixed: When a user invoked Scan Match via Lookup in Line Item Details on a Transfer order where the line item is partially fulfilled, FrontLine allowed inventory to be selected from the destination location instead of the source location.

- Fixed: Web data imported to a service order where the repair unit identified in FrontLine Connect had already been added to the service order in FrontLine Desktop are now linked to the existing repair unit line instead of creating a new repair unit line with no unit committed to it.

- Fixed: When an Item with Stock Identifiers was copied the new item shared a reference to the original item's stock identifiers.
FrontLine now creates a new independent document if the users wants it copied.

- On a workstation where the font size has not been set, the default font size is now 10 if the horizontal screen resolution is at least 1,600 pixels, otherwise the default is 8 as it used to be.

- Recurring Billing now ignored unit references from intangible equipment set lines when creating references on new bills.

- Order Totals now has a Quantity column. Note that these are base quantities, units of measure cannot be combined.

- Web labor imported with no reference to a repair unit line in FrontLine Connect now appear on the service order with no link to a repair unit instead of assuming the last repair unit identified by the field technician.

- After an order that is part of the current bank deposit batch is deferred or completed with tenders changed, the bank deposit indicator near the top of the order window now shows an updated batch total.

- Added security contexts "Quote Presentation" for Customer Orders and "Quote Request" for Purchase Orders. Add allows a user to present an open quote.
If the Quote belongs to another agent then the user must also have an Add permit in the Other's Orders security context.
Note that quotes mixed with order line items are treated as orders for security purposes, using the contexts for "Order Check Out" and "Order Check In".

- Search By selector in lookup windows now allow free type-in entry with auto-complete.

- Customer and Purchase Order Lookup now have a Newest First vs Oldest First selector. Previously searches were always newest first.
When searching by customer number, for example, the primary sorting is still customer number, but within a customer's orders newest vs oldest first applies using the order Placed date.

- Added two optional limits to Access Profiles along with the existing Write Off Limit:

- Fixed: Bank Deposit entry hints in the status bar of a customer order window were missing the deposit identification/confirmation text. This was broken in 6.6.012

- Fixed: Showing All similar contracts in the Contracts list of the Service Contracts window now excludes disabled contracts and contracts on voided equipment sets.

- Fixed: Opening an order from Order Lookup Mode, and changing only an order status flag did not refresh the lookup results upon closing the order window.

- Fixed: A recent revision to the vendor performance analysis for purchasing could in some unusual circumstances raise an SQL error:
Cannot insert the value NULL into column 'LeadDays'

- Presented Quotes can now be Cancelled and Restored using the Cancel Quote function in the Quote drop-down menu.
Users must have the Delete permit in the Order Quotes security context to cancel or restore quotes.
If the quote is by another Agent then the user must also have the Delete permit in the Other's Orders security context.

- Forms for Orders now offers Transfer output for Transfer orders, using default form Transfer.rep

- Added a Offer to E-Mail Agents about Shipments of their orders option in company setting Notify Options.
Previously this notification was on by default, now it has to be turned on.
To turn it on without using FrontLine setup, execute this SQL:

- The Job and Opportunity and Manufacturer Representative (MR) menu entries in the customer order window have moved from the Quote button to a separate O.Class button. The O.Class label can be changed in Setup-Labels.

- Added a Non-AR Order Type indicating a customer order is not taxed, should not be on tax reports, can only have charge line items, does not require order identifiers, and does not open the customer's Receivables when it is part of a bank deposit batch. A user must have permissions for the Receivable Payment security context to create and modify Non-AR orders.

- Added a Non-AR Customer entry to Company Settings. This customer is required to enter Non-AR orders.

- The Motorola Sales status option introduced in 6.6.010 for Vendors is now Special Reporting.

- Fixed: Payments on receivables were not fully excluded from shipping charge calculations.

- Fixed: Purchasing manually using a scan code could invoke Scan Match and Item Action with invalid options.
This bug was introduced recently, perhaps in 6.6

- Reduced time Refreshing Costs and Substitutes... upon opening purchasing in large databases.

- The current Bank Deposit batch can now be closed if the current order is blank.

- Upon closing a Bank Deposit batch FrontLine now offers a review of the payment orders in the batch. From this review list the orders can be checked out.

- The Contact Name displayed and used to Search By in purchase and customer Order Lookup now follows the Address selected in the upper right of the window.

- Entering a check number or checking account number in a payment tender line with no amount specified and a positive order balance now sets the check tender amount to the balance.

- Upon starting a new Bank Deposit batch FrontLine now prompts for an optional Deposit Date. This deposit date is assigned to invoices created from orders in this bank deposit batch. The user is asked for confirmation if the deposit date entered is more than four days from today.

- The title of the Customer Order window now changes to Customer Short Term Rental for Short Term Rental orders.

- Except for Purchasing, the transaction Type selectors in Transaction Inquiry are no longer mutually exclusive.

- Fields named Latitude and Longitude with suitable values are now output to reports with text formatted using degrees, minutes, seconds, hemisphere.

- Fixed: Upon entering the Stock number of an item with no identifiers as the scan code on a new Adjustment order, the Adjust In option in the Adjust Action prompt was disabled.

- The customer Orders and Quotes lists from Customers maintenance now allow opening orders and quotes for editing, like Order Lookup Mode from the Welcome window.

- Export now offers a MapLink output column when Latitude and Longitude fields are in the dataset, and the current row has values for both.
When the Spreadsheet option is on the output uses an Excel =HYPERLINK format,
When the HTML delimiter is selected it uses the standard HTML HREF format,
Otherwise it outputs the bare https link.

- Equipment Search now offers a Map option in the context menu when the identifiers selected include Latitude and Longitude, and the current row includes values for both.

- Added a Motorola Sales status option to Vendors. The [VendStatus] value of this flag is 1048576 or 0x100000

The Db Console contains a required update that is not backward compatible:
File: Entity Status Int (6.6.010)

- Fixed: Changing a Quote line Price or Quantity in situations where the cursor does not move off the line item delayed recalculation of quote totals until the cursor moved away from the line.

- Fixed: Upon Receiving items with identifiers but whose primary identifier is not required at receiving, FrontLine now creates blank identifier documents for the received units in anticipation of identifiers to be added later.
This keeps the received event I.Doc in sync with the automatically created special order sales event I.Doc

- Fixed: In Fast POS mode, cancelling Identifier Document entry for an Unidentified transaction resulted in a program hang.

- Fixed: Invoice Costing would include separated discount lines. This revision is in the CostInvoice db procedure.

- Opportunity Identifiers now have a distinct Identifier Document Template from Job Identifiers.

- Transaction Type [TrxType] displays for Payment On Account now exclude the word Sale.

- When a payment tender type is identified that is either a card with a non-zero balance due, or a check with positive balance due, FrontLine now sets the tender amount to the balance due by default if the amount was blank. Previously it only did this for On Account.

- Fixed: It was not possible to Write Off Taxes of a Recurring Bill in Receivables.

- Fixed: Selecting a Location from Scan Match after identifying a stock item with no identifiers on an Adjustment resulted in an adjust-in instead of adjust-out of the inventory.
To adjust in the user should choose Unidentified from Scan Match.

- Costing now processes intangibles: Services and Charges.
Intangibles are costed using Standard cost regardless of the Items record Costing method.
Items maintenance now allows entry of Item Costing per location for services and charges.
This revision requires an update to the CostInvoice db procedure.

- Added a totals line beneath the Costing details available in the Invoice window.

The Db Console contains a required update:
File: CostInvoice v6.6.008 (This entry was removed in 6.6.009)

The Db Console contains a required backwards compatible update:
ORDERS.OpportunityID (6.6.007)

- Fixed: When a Special Order line on a purchase order was not linked to a customer special order line the links FrontLine offered included customer return lines.
Also, now the purchase order quantity is matched to the remaining uncommitted quantity on the customer order rather than the entire quantity on the customer order line.

- Fixed: If columns were added to an Info Sheet table after a user had used the info sheets the new columns did not appear on the info sheet for that user.

- Fixed: Marking a committed return or repair Item in Line Item Details as Defective when the Quantity was greater than 1 resulted in an access violation.

- Fixed: Tenders created using the Payment Undo option of the Returns feature did not copy the ledger Account number of the original tender.
And now when the user chooses All FrontLine chooses the Payment Undo option by default.

- Fixed: Upon opening the Tender Types Company Setting window an error message appeared: SizeOf(TPTL) <> SizeOf(TValueItem)

- Fixed: Changing the Price of a Miscellaneous line item up and down a few times resulted in an incorrect tax valuation of that line.

- Fixed: The [Invoiced] date of a Tax Write-Off in Receivables is now set to the [Applied] date instead of the original invoice date.

- Fixed: The Any Stock Item option in Company Setting Line Unit Identify Options did not indicate the saved value when reopened.

- Fixed: The search type-in box in Identify Unit window is now 60 characters to match potential identifier values.

- Fixed: Under some conditions FrontLine would use the Shipping Charge Calculators on Purchase Orders.

- Forms for Orders outputs now include the Agent indicated in Resource Costs as ResourceAgent.

- When an order ship-to address is changed FrontLine now only assigns the order agent if either:
The order has no agent, or the new ship-to address has an address-specific agent.

- Addition of Conversation Notes now indicates the user who added the note text heading.

- Going forward, regular notes now indicate who last revised a note separately from who created the note.

- FrontLine can now auto-commit package member special order or catalog line items on a customer order when the package itself is not on special order.

- Open customer order Special Order lines that have appeared on a customer invoice but have no quantity committed and no special purchase order can now have Special Order turned off.

- To Be Scheduled options Show on Scheduler Board and Show List below the Board in the Scheduler are now sticky per user.

- The Export Summary from Recurring Billing Output now offers a TotalTaxes "Tax Total" column, and the CExID output is removed.

- The Export Bill Summary by Stock Number from Recurring Billing now offers a TaxTotal column.

- Increased the maximum result rows retrieved in the Identify Unit window from 800 to 1600.

The Db Console contains a required backwards compatible update:
NOTES.UpdateBy (6.6.006)

- Fixed: The SUMS outputs of Forms for Orders introduced in 6.5.030 is now invoice-specific (instead of order total) when in context of an invoice.

- Fixed: 6.6.001 introduced an error in Equipment Search: No argument for format %1:d

- Fixed: When a unit under warranty was identified to use on a service quote the repair unit line was not warrantied.

- Fixed: Toggling Exclude in Step 2 of Recurring Billing Output when there were no real exceptions resulted in an exception message upon proceeding to Step 3.

- Added an Order Lookup Mode from the Welcome window that bases order entry on Order Lookup instead of order lookup as a function in the order entry window.

- Implemented in Company Setting Return, Repair, and Unidentified Options an option to allow Vendor RA from Multiple Locations.
Note that V-RAs do not follow the company setting to "Return Units to Order Location" vs "Return Units to Last Known Location"

- The email address outputs from Recurring Billing Output now combine email addresses of all Invoicing (Billing) contacts indicated on the Bill-To address, delimited by semicolons.
Note that the combination is limited to about 240 characters.

- On a Service Quote, when a quoted part/service/charge is assigned to a warrantied quoted repair unit, the part/sergice/charge line is now automatically warrantied even though the specific part/service/charge warranty expiration dates of the repair unit are unknown.

- Fixed: A Warranty Vendor Invoice would fail to be created when the repair unit was known before the service order but the repair unit warrany was unknown and added on the service order. This fix is in the NewInvoice db procedure that must be applied from the Db Console.

- Opening Jobs from an order that has been assigned to a job now automatically opens that particular job.

- The payment tenders on a customer order now indicate when an On Account tender has been paid in full with a (Paid) text and light green tint in the account number column.

The Db Console contains two backwards compatible updates:
On Acount Tender Paid IX_AR_ApplyTo (6.6.003)
File: NewInvoice v6.6.003

- Fixed: 6.6.001 introduced a bug when a charge or service was selected for an order from Item Lookup the Scan Match window would appear showing Available Inventory.

- Fixed: When a customer order with a ship-to address is changed to POS the customer's default agent is only assigned to the order if the order did not have an agent.

- Outputs from Forms for Orders that have special sorting can now be sorted by line number instead, using the new Sort by Line number option.

- Added three countries to the built in country list: Kosovo (+383, KV), Montenegro (+382, ME), and Serbia (+381, RS).

- Added security contexts Web Scheduler and Other Web Schedules to the Scheduler class of Access Profiles.

- The Order Quotes security context (in Access Profiles in the Customer Orders class) can now be used in combination with the main Customer Orders context to enable users to work on quotes but not modify customer orders:

- Fixed: Recurring Billing using a Bill Frequency of week factors raised an SQL error after Step 1.

- Fixed: Manually entering an TaxGeoCode in address maintenance that is unlisted because it is not relevant to that address could cause an access violation upon saving the address.

- Fixed: Upon deferring a partially Invoiced open order FrontLine did not automatically adjust an open On Account tender to match the order total, instead it indicated insufficient credit.

- Fixed: FrontLine 6.6.000 introduced a bug that left totals incorrect after changing a line item price.

- Fixed: A recent revision broke the launch of Inventory Valuation with an access violation.

- Added import of FrontLine Connect repair units (WEBREPUNITS) and parts (WEBPARTS) and elaborated the labor (WEBLABOR) import.
The import attempts to commit the units specified (repair units and parts) if the customer status is not on hold.
Lines imported from FrontLine Connect show a linked earth icon in the Description column: [TrxStatus] flag value 1,048,576 or 0x100000.
Parts and Charges are added at List Price.
Voiding imported lines reopens the FrontLine Connect data for web modification, and reimport to an order.
Voided imported lines cannot be unvoided.
Administrator is not offered this import.
Signatures are not imported yet.

- Customer Order Lookup and Customer Lookup now show a P indicator in the first column for Prospects.

- The row count display at the bottom of Lookup windows now includes both the number of rows shown and fetched since these are different when a Filter is applied.

The Db Console contains a backwards compatible update required by revised commission processes:
ORDERS.CommissionPaid

- Forms for Orders now includes TotalPaid and LastPaid in the PAYMENTS dataset that output the amount paid on a receivable (On Account) tender and the date of the most recent payment.
Note that invoices created in earlier revisions of FrontLine will not have these new values output.

- Improved consistency in order entry between scanning a full stock number and using Item Lookup.

- The Vendor Number Search By entry in Item Lookup is now Primary Vendor and provides a list of vendors with key input assistance.

- Line numbers in the database have been changed from type smallint to int.
This revision requires updates to the database that are not backwards compatible.

The Db Console contains three required updates:
File: Line type int (6.6) - apply this one first, it can take over a minute in a large database. Upon success then,
File: GetTaxes v6.6 - apply this one next,
PAYMENTS.ReceivableID (6.6) - this one is backwards compatible.
For connected systems this is a connector-related release, the SW Connector Release 4.0.000 or later is required.

- When a unit that was last received, transferred, or returned is identified for sale FrontLine now offers a Package Recall feature to add it to the current order in the same package configuration.

- Upon receiving an identifiable member of a package, FrontLine nows attempts to auto-receive other package members that have no identifiers required at receiving.
Inventory received this way will need to have those identifier values added later, either on the purchase order or a subsequent transaction.

- The toolbar buttons in the forms output viewer now enlarge on high resolution displays.

- Fixed: If a package on a customer order is not marked ready to check out then FrontLine should not expect tangible members to be fulfilled to proceed with invoicing.

- Fixed: If the same ContactID was used at multiple addresses the contact could appear duplicated in the contact selection lists of an order, and order lookups could output multiple rows for the same order.

- Fixed: When a Vendor was copied using the Copy function the Vendor Number should not be copied.

- The VendorNumber expression from Forms for Orders for customer orders now outputs the special order vendor(s) if applicable, otherwise the item default vendor.

- Added security contexts After Check Out for customer orders and After Check In for purchase orders in Access Profiles where the Modify permit allows users to change the Customer PO / Vendor Reference and the order Contacts after invoicing.

- Added a Company Setting Order Discount Item Category so order discounts can be categorized for account assignment.

- Fixed: Purchase suggestions listed by auto-gen in the Generate Purchase Order feature should not consider location Minimums for Package items.

- Fixed: The Quote summary outputs from SUMS and CATSUMS datasets in Forms for Orders did not subtract quoted returns.

- The Sort by Stock option in Recurring Billing Output no longer combines multiple bills to the same customer in the same batch.

- When the Current Station is set as a POS station and a customer order is a POS order (no ship-to address), FrontLine now uses a Fast POS mode:

- Fixed: A later folder revision to the FrontLine executable copy launcher introduced in 6.5.048 made it fail for users or sites that hadn't used FrontLine with the earlier version.

- Fixed: When a metered billing equipment set member is on an open order Recurring Billing does not bill that member, however it would erroneously consume the meter readings anyway.

- Fixed: When Receivables were opened from Customers maintenance, then opened from taking a Payment on a Customer Order, the Pay Now column could fail to appear.

- Fixed: When a fraction of a Payment is applied in Receivables the added payment record now has a copy of the original payment Comments.

- Fixed: Recommitting units when a Service Quote is unquoted could result in error List index out of bounds which then caused an All Generic Qs Active condition that required restarting FrontLine.

- Fixed: Creating a transfer line item on an item with no inventory in the source location was inconsistent between a blank transfer order (the entry was cancelled) and an open transfer order (the line was created with nothing committed). It should now create the line with no inventory committed in both cases.

- Fixed: In Receivables a Tax Write-Off now prompts the user for an Account to use for the write-off. As before, the location discount account is used by default.

- FrontLine can now import WEBLABOR entries for open customer orders.
Field entries from FrontLine Web are imported as one line item per agent per labor entry.
The lines default to zero price and are flagged as No Print.

- The Shipping Charge Calculators rules now Exclude Travel items from the assessed value when ItemType specifies Tangibles, Services, or Charges.

- The Shipping Charge Calculators rules Ship Via can now be Services as well as Charges.
Any charge or service items used in Shipping Charge Calculators "Ship Via" are excluded from Value (Req Value) assessments.

- Forms for Orders now offers a CATSUMS dataset with summaries per Item (Product) Category.
These sums are multiple rows (one row per item category, preceeded by one total row with ItemCatID -1) and are not available in batch outputs.
To use these fields add a CATSUMS dataset to a form in a subreport to provide these values per category:
ItemCatID, ItemCat,
TotalItems, TotalTangibles, TotalServices, TotalCharges, TravelServices, TravelCharges
QuoteTotalItems, QuoteTotalTangibles, QuoteTotalServices, QuoteTotalCharges, QuoteTravelServices, QuoteTravelCharges

- Fixed: The EMail address used for output by Recurring Billing Output is now the billing contact's email address in precedence over the email address of the bill-to address.

- The Task List of events to be scheduled in the FrontLine Scheduler now has a context menu with entries to Map the selected task and Map All Tasks listed.

- Fixed: When non-identifiable members of a package or BOM are auto-committed after adding the package or BOM, the green outline now appears for fully committed member line items.

- Fixed: When there were no Customer/Purchase Order identifiers defined, the Customer/Purchase Order Lookup could trigger an SQL error U.UIValue could not be bound.

- Fixed: Duplicate units Received should not treat Customer Equipment as unidentified sales to back fill.

- Fixed: When customer equipment that was not sold in FrontLine was returned on an order with a different order location and the Company Setting in Return, Repair, and Unidentified Options was Return Units to Order Location the return event and the return line item would end up in different locations.

- In Miscellaneous Purchases there is now an <ALL> entry in the vendor selection list to include miscellaneous customer order lines where any vendor has been specified.

- The Shipping Charge Calculators rules can now be used to calculate other Charges that are manually added to the order.
In Setup -- Lists, other charges can now be selected in the "Ship Via" column to create rules to calculate the value of this charge.
Any charge items used in Shipping Charge Calculators are themself excluded from Value (Req Value) assessments.

- Added a Travel Item Type flag (ITEMS.ItemType value 16777216) to indicate than an intangible item is related to travel. Presently this flag is only used by the Shipping Charge Calculators.

- The Shipping Charge Calculators rules can now qualify the line item totals examined by the new Item Type Travel.

- The Shipping Charge Calculators rules can now examine line Quantity values in addition to Effective (extended price) totals for Application value and Required value independently.

- Fixed: When a received payment that was part of a bank deposit batch is returned, if the bank deposit batch is still open the return order is placed in the same batch.

- Added a Favorites feature to Reports for users to indicate up to 20 reports that they want to see and exclude others.

- It is now possible to set Web User passwords in System Users using the Web Password function in the drop-down on the side of the standard Password button.

- Agents now have a Receive Notify flag to send email notifications to the customer order agent when special orders are received and a Receiving register from Reports for Orders is printed for those special order lines.

The Db Console contains a required update that is backwards compatible: Web Access (6.5.069)

- Fixed: Urgent special order line items did not display the exclamation mark in the Generate Purchase Order purchasing suggestion list.

- Fixed: Opening Service Contracts from the Customer Lookup window could raise an SQL error.

- Added a Points numeric column to the Note Type list.
Non-zero points values are stored in LISTVALS.CalcValue

- Fixed: Defective identifiable inventory can now be committed to (V-RA and I-RA) Return Authorizations.

- Fixed: A few months ago a revision removed the strike-out from the line total of lines covered by warranty.

- Fixed: A scheduler event saved without a customer or vendor assigned would end up assigned the self entity. (Bug introduced in 6.5.065)

- The Shipping Charge Calculators rules can now qualify the line item totals examined: All Lines (as before), Tangibles, Services, or Charges.

- Fixed: Copied Orders and Quotes were missing the original line item Periods.

- Fixed: Quote Totals shown in the order window did not consider rental Periods.

- Fixed: Incoming Adjustments should be costed by FrontLine even when Company Cost Options for "Costing Received Goods" is set to By AP.

- Fixed: Costing in the customer order invoice window displayed duplicate entries when warranty claim was part of the invoice.

- Packages and BOMs can now be added to an I-RA, but in either case only the members are added as in a BOM.

- Added QuickBooks Journal Entry Export to the Third Party panel in the Welcome window. This link launches a Python file in the FrontLine program folder named QBJEExpFLFL.pyw where FLFL is the name of the database in use.

- Customers can now have an Info Sheet - a simple tabular data sheet that is unrelated to FrontLine internally. To use Info Sheets:

- Fixed: Exchanging an unplaced member for a placed Equipment Set member could trigger a database primary key violation on PK_ESDTL upon saving.

- Fixed: Recurring Billing did not assign the customer's tax Exempt Category on tax-exempt recurring bills.

- Fixed: A unit return could create references to the last recurring bill that unit appeared on. This fix is in the CopyLineItems db procedure described below.

- Fixed: Instances of FrontLine that have copied the executable to a local folder because it was launched from a network folder on another computer should now look for the payment integrator (like pcauthor) in both the network folder and the local folder.

- After check out FrontLine now asks the user if an equipment set group should be cancelled because an equipment member of it was returned. If yes, the whole group is removed as before. If not, only the equipment itself is removed and other group members remain in the equipment set.

- Added a Scan Code entry to the Returns window. Here one can enter the primary identifier of a unit that can be returned from the order and press Enter (or click Add) to have it added to the return list without looking for it.

- Added a Tentative type of Scheduler Event.
Tentative events are future events that have not been confirmed and are subject to rescheduling.
The scheduler board now has Tentative Events view options:

The Db Console contains a required update that is backwards compatible: File: CopyLineItems 6.5.065

- Fixed: Scheduler Events created for I-RA line items failed to show the event address.

- Added a Customers vs Prospects security context to Access Profiles with values All Customers vs Prospects Only that makes non-prospect customer records read-only to the user.
When a Prospects Only user opens customer records in maintenance the yellow highlights indicate view-only mode.
When a customer record is in view-only mode due to Prospects Only permit, only Contacts of the User's Agent can be modified.

- Added a Service Bins list to Setup Lists.
If there are any service bins listed then a S.Bin field appears at the top of customer orders.
A service bin is assigned a location and can only be used on one customer order at a time.
if an occupied service bin is assigned to an empty order FrontLine offers to open the occupying order.
If an order was assigned a service bin then this bin is shown in the Order Type field of Order Lookup.
Changing the order location removes the assigned service bin.
Forms for Orders outputs a SBin field.

The Db Console contains a required update that is backwards compatible: ORDERS.SBin (6.5.064)

- Fixed: Filtering by an Agent in Order Lookup did not work properly if repeated after the changing the Search By then using Filter By Agent again without using another filter first.

- Fixed: Creating an order from a completed quote did not copy the alternate bill-to entity correctly.

- Fixed: The iCalendar (ICS) attachment universal time coordinates (UTC) expressions introduced in 6.5.062 adjusted for time zone bias in the wrong direction.

- Fixed: The Scheduler Event function in Line Item Details was sometimes disabled when it should have been available.

- The Start date/time entry box in the Scheduler Event window is now highlighted in yellow when it has no time.

- The Scheduler Event function in Line Item Details now offers to create a scheduler event for an eligible line item (Item Type Scheduled) that is not already on the scheduler:

- Item Categories in Lists setup now have an optional Price Levels Template per category where only relative (percentage) prices can be entered.
This requires the database update below.

- When a Catalog Item with no Price Levels is manually added to a Purchase Order, FrontLine now offers a Price Levels Quick Add feature where one can:

The Db Console contains a required update that is backwards compatible: PRICELEVELS Category Template (6.5.063)

- Fixed: Specifying an Inventory Account criteria for Inventory Valuation could erroneously multiply result quantities due to the Item Category Accounts configuration.

- Fixed: The Allow Third Party Item Status is now verified before receiving special order items in a rental location as third party units.

- Fixed: Dragging the leftmost column to rearrange a lookup window resulted in a List index out of bounds (-1) error.

- The Bin output from Forms for Orders for Transfer Orders is now the source location bin instead of the destination location bin.

- PersonID output from Forms for Orders is now the user name instead of an ID number.

- The iCalendar (ICS) attachment generated when sending email from a Scheduler Event now specifies the event start and end in universal time coordinates (UTC).

- Fixed: After a recent revision clicking Create Order in the Scheduler Event could raise an SQL error.

- Fixed: Technician (limited) users should be permitted to modify orders they open from a Scheduler Event.

- Fixed: Line Item Notes used the same security context as Order Notes instead of their own designated L.Notes context.

- The Sort by Group option introduced in 6.5.057 in Recurring Billing Output now sorts by the first of the Identifiers selected for output before sorting by group. To enable sections in the forms to use this BILL.UIValue1 as a Group Expression this identifier value is copied to the output for all members of the equipment group from a member that has it to those that do not have this identifier type of their own.

- Equipment Search can now be opened directly from Customers maintenance from the drop-down near the Parts button. Equipment Search opened this way has the customer in context already assigned to the search criteria.

- Company Setting New Order Focus is expanded to include a Hide Order Addresses Section option that hides the Bill-To and Ship-To addresses in order entry. The addresses can be revealed on an order using the Zoom function as usual.

- The Unit Price column title in the customer orders window can now be customized using Labels.

- Fixed: Receivable Statements and the list in the Receivable window now calculate days overdue the same way.
Previously having times of day in due dates could make one result a day different from the other.

- Company Setting Order Activity Reactions option Set Order "Fulfilled" Date and Time
now requires line items to be fullly committed and identified, so it is now Set Order "Fulfilled" Date and Time and Prepare to Invoice

- Added an optional Department field to Equipment Sets that is used to assign a department to the recurring bills created.
Note that the header section of the Equipment Sets window has been rearranged.

- The Lookup function in Line Item Details is now available on Quotes.
Inventory selected from Scan Match is not committed to the quote, and the BackOrder, Special Order, and Unidentified functions are not available.

- In the Unit Details list of the Scan Match window the "Sale Price" column is now titled "Last Price" and displays a

icon near the value if it was a purchase or adjustment cost.

- Added a three outputs to Forms for Orders and Recurring Billing Output that reflect the order or bill location:
LocationPhone1
LocationPhone2
LocationPhone3
LocationEMail

- The FrontLine Logon window now uses font size 12 for improved usability on high pixel density displays, and current station setup now offers a font size 16 option.

- Fixed: The Max Past days overdue in Receivable Statements should not consider open credits.

- Fixed: Recurring Billing for Billing Frequencies based on number of days (like 30 Day) or number of weeks would assess a zero quantity for some line item types.

- Fixed: When the workstation has a default Rental Location and the user sets a blank customer order to a Short Term Rental the designated rental location is assigned but the Periods column in the line items did not appear.

- Receivable Statements now output a StatementText field whose value depends on the Max Past (highest days overdue) of the customer. The "Description" column in the Receivable Age brackets in Lists setup is now the "Statement Text" used here. This text is no longer used as the AGE.Description - those texts are now always composed by FrontLine as they were before when the descriptions were blank.

- Added an Inventory Account criteria to Inventory Valuation, and a direct link to Inventory Transactions on the context menu.

- The Void Payment function used to undo collected tenders that have not been applied to an invoice yet now manipulate the PAYMENTS.SyncSet like this:
+ If collected payment had been connected, then it's SyncSet now remains. The new reversal tender line has a NULL SyncSet as before.
+ If the collected payment had NOT been connected, then instead of leaving the two SyncSets blank FrontLine now assigns a SyncSet 32767 to both so the connector skips the pair altogether.

- Fixed: The revision in 6.5.056 to flag a Collected and connected tender assumed the SyncSet would be positive.

- Fixed: Customizations of the Receivable Age brackets in Lists setup could not be saved due to a database error.

- Fixed: The custom Unit Warranty feature added in 6.5.056 broke the recognition of Service Contract coverage on Service Orders.

- Fixed: Packages sold in Package First mode did not process a % (percentage) discount correctly for the initial total package calculated price, resulting in a zero price.

- Fixed: Leaving the Optional Write-Off Date blank upon Write Off Taxes in the Receivables window would leave the Applied date on the write-off record blank instead of using the current date. This caused the write-off to be valued on the original invoice date instead of the date it was written off.

- When an unconnected AR Write-Off is Undone, FrontLine now sets the AR.SyncSet value to 32767 so the connector ignores it.
As before, if the write-off had already been connected then FrontLine clears its AR.SyncSet so the connector includes it.

- It is now possible to edit an order's identifier document after the order is closed.
The user must have full permission (Read, Add, Modify, Delete) to the Order Identifier Document security context.

- Undoing a Write-Off in the Receivables window no longer clears the ApplyToID of the cancelled write-off record.

- The Bank Deposit drop-down listings in the customer order window now show the current value of the batch.

- Equipment Set member lines now display a note icon when the member has a note.

- Notes window title texts are now worded Notes - Context instead of the context first.

- Added a LocationAddress field to Recurring Billing Output to output the address of the bill location, which reflects the equipment set location at the time the bill was created.

- Values for SQL (non-graphic) custom Reports parameters that include 'date' in their name are now evaluated as a date using FrontLine's date format. If the value can be interpreted as a date then FrontLine rewrites it in a YYYYMMDD format in the query text. If FrontLine cannot interpret the value as a date then it places it in the query text as-is.

- Revised automatic order agent changes when User Option User Agent priority on new orders is OFF:
When a customer order's ship-to address is changed, or new customer assigned, the agent indicated by the new ship-to address (or new customer) is assigned to the order even if the order already has an agent assigned.
The situations below remain as before:
If the order already has line items, the agent assigned to the line items is not automatically changed.
If the new customer and ship-to address have no designated agent then the agent already assigned to the order is left unchanged.
If the user has option User Agent priority on new orders turned ON then changing the order customer or ship-to does not change the order agent.

- Fixed: Redo Order of a service order with warrantied parts and services lost warranty coverage on the linked parts and service lines.

- Fixed: A recent revision broke the Details and Export features in Transaction Inquiry for large result sets with an SQL error about P.EntityRedirected missing.

- Maybe Fixed: Potential omission of the main To recipient of emails sent from within FrontLine.

- Export from Physical Count now includes a Part number column of the default vendor.

- Elaborated the sticky Sort by options in Recurring Billing Output to add a Group option to the existing Stock and Default options.

- Line items added to an order as part of a Bill of Materials (BOM) now have a collective reference to allow them to be automatically grouped together as Equipment Set members.

The Db Console contains a required update that is backward compatible: TRXIP.PkSeq (6.5.057)
Note that ESDTL.LineRef now receives small negative values for BOM collections.

- Fixed: Late Fee Billing could include receivables not yet due at the time of assessment due to crossover in timing Credits on the Posted date versus timing Debits on the Due date.

- Fixed: When a partly invoiced order was revised to reduce the total, then checked out, the credit tender was not collected (for On Account that means not posted to AR).
For example, a short term rental where the rental unit is checked out, then returned (perhaps early) on the same order for a partial credit.

- Fixed: The Sort Service Orders by Repair Equipment toggle introduced in 6.4.102 was lost in 6.5.054

- Fixed: The order tax ExemptCategory was not copied by the order Redo, order Return, and order from Quote functions.

- Fixed: The equipment set export introduced in 6.5.050 would output Quantity as currency, and did not title the Id 2 column with the user's selection.

- Fixed: After opening the report, the Export function for the Drawer Reconciliation Report is now available to normal users who have the Modify permit for Drawer Reconciliation Report security context in the Inquiry class.

- The Rental Form Mismatch prompt introduced in 6.5.055 must now be turned on in company setting Notify Options where there is now a Notify user of Rental Form Mismatch in Forms for Orders option.

- Added fields LocationAddress and LineLocationAddress to the output of Forms for Orders.
These are text compositions of the respective location name and address, making it unnecessary to hard code location addresses on the forms.

- It is now possible to assign a custom Unit Warranty at the time of sale from the context menu in Line Item Details. Note that part of this revision is in the database updates indicated below.

- It is now possible to override the standard Warranty in Line Item Details of customer orders before check out. This override is applied to all units committed to the line at time of check-out, instead of the standard warranty indicated for the model, unless they have a custom unit warranty which takes highest precedence.

- Added a security context for Warranty Vendor in the Unit Warranty group of Access Profiles.

- User changes made to a Unit Warranty are now logged. However, the change log is not yet presentable.

- Added an Item Status flag Depot During Warranty to indicate that the depot repair start and end only apply to units still under warranty.

- When a previously Collected and connected (SyncSet has a value) tender is subsequently used during check out (assigned to an invoice) the PAYMENTS.VerifyCode now has flag value 4096 added to indicate that it was a deposit collected ahead of check out.

The Db Console contains three required updates:
Line Item Custom Warranty (6.5.056)
File: ItemDtlDelete v6.5.056
Apply this one after Line Item Custom Warranty:
File: CommitInvoice v6.5.056

- Fixed: The Add Set Member function in the main order window misreported the number of entries added to equipment sets.

- Upon identifying an item to add to a blank PO, the Scan Matches list in the Scan Match window now shows separate rows for each vendor that has a part number on file for the item to facilitate Last Cost comparison.

- Before producing output, Forms for Orders now compares the rental characteristic (rental or non-rental) of the order location to the form file name (should contain rent or not) and prompts the user to confirm the Rental Form Mismatch if they do not match. Note that this does not apply to batch output.
Forms intended for rentals now should include rent in their file name. The text is not case sensitive. For example:
InvoiceOrmandy.rep (for non-rental locations)
InvoiceOrmandyRent.rep (for rental locations)
InvoiceRentFromOrmandy.rep (for rental locations)
InvoiceOrmandyCurrent.rep (unintentionally for rental locations)

- Fixed: When a line item was created from Item Lookup FrontLine failed to ignore the Item's Default Location as it should for a Rental Location or a location with Ignore Item Default Location.

- Improved Transaction ID reference for Credit Card Refunds to reduce refund rejections by the payment gateway.

- Added a New Rental Line waits on Quantity option to Company Setting Line Unit Identify Options to make new rental lines focus on Quantity instead of Price, like sales.

- Added an optional Periods value to line items to indicate how many rental periods to assess at the given price.
The Periods column only appears on customer orders when the order location is a rental location.
Periods is available in the output of Forms for Orders.
This revision requires the database updates for Periods, NewInvoice, and CommitInvoice below.

- Expanded the EntityOrder field (used for Customer PO numbers, for example) from 20 to 32 characters. This revision requires a database update below.

The Db Console contains four required backward compatible updates:
Expand EntityOrder -Customer PO (6.5.054)
Line Item Periods (6.5.054)
Apply these two after Line Item Periods:
File: NewInvoice v6.5.054
File: CommitInvoice v6.5.054

- Added SKU and UPC along with existing Parts. A vendor or customer can have a different Part number, SKU, and UPC for the same stock item.
Forms for Orders do not output SKU or UPC. The primary target of SKU and UPC is to Scan Match.
This revision introduces a Part Type discriminator, and requires a database update.
PartType values are: 0 = Part number (default), 1 = SKU, 2 = UPC.

- Packages now allow the same item to appear in different Groups. This revision requires a group in key database update.

The Db Console contains two required updates: (both are backward compatible)
PARTS PartType (6.5.053)
PACKAGES Group in Key (6.5.053)

- Fixed: The Order Filter type in box in Receivables would appear on top of the grid when Receivables were opened from Customers maintenance.

- Fixed: The Details list in Inventory Valuation could show non-inventory units when the unit location changed unexpectedly in the chain of events. This did not affect the actual count and valuation.

- Fixed: The Third Party launcher revision in 6.5.049 broke launches of Python programs.

- Fixed: A recent revision broke the listing of Group Receivables with an SQL error.

- Fixed: The display of Tax Geo Code in maintenance windows could include extraneous characters for the GeoCode description after the user changes it.

- On Recurring Bill returns, TRXDTL.InvSeq is now set to zero to match the original bills. The prevents duplicate appearance of equipment in Equipment Search.

- The context menu entry to View Order in the Receivables window now includes the Periodic Invoice number, if applicable.

- Added to Company Setting Order Activity Reactions an option Do not show Forms for Orders after checking out only Payments.

- Added Bank Deposit entry to the POS drop down in the customer order window.
Here the user can choose to begin a New Deposit Batch or continue an open batch.
A user can add to another user's batch if they have a permit to do so. (Permit described below.)
When the user chooses to begin a new batch they are are given an opportunity to close all their own open batches, if any, and can enter some identifying text.
Bank deposit batches can also be closed individually from the Close Deposit Batch list. Here the user has an opportunity to revise the identifying text with confirmation information provided by the bank.
An order that is part of a bank deposit batch opens Receivables expecting to take payments as line items. However, it is possible to cancel and enter a regular line item if desired.
An order that is part of a bank deposit batch displays a light green bar near the top of the window indicating the Bank Deposit ID, when it was created, and by whom.
There is a new Bank Deposits security context in the Customer Orders group where:
+ Add permit allows a user to create and handle to their own batches,
+ Modify permit allows a user to add to other user's batches,
+ Delete permit allows a user to close other user's batches.

The Db Console contains a required update: File: Bank Deposits (6.5.052)

- Fixed: FrontLine ignored Scan Code input to commit Assembly components to an existing line item from Line Item Details.

- Check Number or abbreviated Card Number is now shown in the FrontLine Payment Verification with the tender Type display text.
And the OK button is now default instead of Cancel. This change of default button (activated by Enter or Space bar) may be significant to users.

- Added Order Filter to Receivables that appears when a numeric digit is pressed while focus is in the Order ID column of the receivables list.
The number entered in this box is used to filter the receivables displayed using trailing digits.
For example, 504 matches 101002504 and 827040504 but neither 504012345 nor 101504321.
Receivables that are currently active for "Pay Now" or write-off or viewing the "Applied" list are exempt from this filter to avoid perplexing a user who is performing those activities.

- Added a BillToName output from Recurring Billing Output to combine Name1 and Name2 without a blank line when one of the names is blank. This is similar to the output available from Forms for Orders.

- Added to Company Setting Order Activity Reactions an Entity Note Popups option to Suppress All on Payments.

- Added Note Type assignment and filter to customer Conversation Notes. The list of types can be customized in lists setup.

- After completing a check out that contains only Payments for Receivables the Forms for Orders window no longer appears.

- Fixed: Packing Slip output from Shipping had the ship-to address of the order instead of the shipment. This affected packing slips for Depot Repairs from customer orders.

- Fixed: When an order was opened for editing from a scheduler event, after adding one line item the scan code entry ignored further input texts.

- Fixed: When there are Closed Locations on file, Physical Count could record and display the wrong location in the Physical Count Events list.

- Receivables now includes Days Overdue for Closed receivables based on the date the last payment was applied. Because these receivables are no longer due they are not highlighted in yellow as overdue.

- Added highlights to Import Customer Equipment to indicate information required to perform the Import step.

- FrontLine now ensures that a customer order is tendered when the user chooses to Ship directly from the open order.

- Added basic Export This Set and Export All Sets functions to the member context menu in Equipment Sets. There is a new security context ESets Export to restrict access.

- Added a Show Payments option checkbox to the lower section of Customer Order Lookup. Orders with payments are now excluded from the results unless this option is on.

- Payment line items now have the read check-box preset to facilitate check out.

- FrontLine now uses only TLS version 1.2 for encrypted connections to mail relays.
Please ensure that the OpenSSL libraries libeay32.dll and ssleay32.dll are dated year 2014 (product version 1.0.1j) or later.
Use of libraries from before year 2009 can cause access violations when attempting to send email.
Mainstream email providers support TLS 1.2 however there are a few providers out there like "Opt-in Wireless" (relay host oiw6.optinwireless.com) running old unidentified mail relays that do not support TLS 1.2

- Fixed: Payments from Customers On Hold can now be taken and posted to AR. Part of this fix is in the NewInvoice db procedure.
Note that if the self entity customer is closed or on hold then Purchase Orders and Adjustments can no longer be checked in.

- Fixed: Costing of sales did not identify the specific unit when the cost source (a Purchase Order or Transfer) had multiple units on the line item with varying unit cost, instead it used the highest unit cost on the source line checked in.

- Fixed: Import Customer Equipment enhancement in 6.4.072 failed to identify Serial numbers in the data about to be imported that are already in the database when the Stock number specified in the import file is different from the Default Stock Number specified in the import window.

- Fixed: Unvoiding an order with package lines of multiple quantity (as when the user changed the number of packages sold on the line item from one to many) would miscalculate taxes on the packages by losing the line quantity multiplication on the line total taxed value.

- Fixed: If an order tender "Payment Type" is preselected to a custom type then the "Account Number" entered should not be interpreted as a standard type.

- Fixed: Write-Offs made at the time of taking a payment now use the Payment line item's Cost of Sales Account, with the location Discount account only as a default if the line COS is blank.

- Fixed: When the order is still open, the Remove Payment function now only posts to AR the amount that has already been invoiced.
Examples:
a. If a deposit was taken on an open order and either not invoiced or checked out on a zero dollar invoice, removing this payment does not post anything to AR.
b. If a $100 deposit was taken on an open order and checked out on a $25 invoice, removing this payment only posts $25 to AR.
c. If a $100 deposit was taken on an order that is now closed, removing this payment posts the entire $100 to AR.

- Added an optional non-unique Additional Identifier to Import Customer Equipment. The values imported for this identifier are not validated.

- Added a Department filter to the Category and Location filters for Item Category Accounts lists setup.

- Added a basic Change Log viewer to the drop-down menu next to the Parts button in Customers maintenance.

- The member Residence and ESet Bill To address drop-down lists in Equipment Sets now include all three fields specified in Company Setting Address Menu Texts instead of omitting the first.

- Added to Company Setting Order Activity Reactions an Equipment Set Note Popup option to Show Equipment Set Note when an ESet is viewed.

- Added to Company Setting Discount Presentation, Quantity Repricing, Cost Pricing, Line Accounts an Department-specific customer orders cannot use unspecified department option to prevent use of non-department-specific Item Category Accounts on department-specific customer orders when there is no department-specific match.

- The Department display in the header section of the main order window is left aligned instead of centered, and the hover hint now includes the department.

- In Receivables, the default height of the Applied list now shows 4 rows instead of 3, and texts in the Tender Type column of the Applied list now include the last four digits of the tender Account Number for non-check tenders.

- In Receivables, when Closed receivables are toggled on, the Applied list below is now also shown.

- Added a Balance Due toggle button in Receivables to show balances due instead of Total Paid values.

- Updated the shipment tracking URLs sent to the web browser to the newer https addresses from UPS and FedEx.

- Added Commission Paid Update to the Third Party panel in the Welcome window. This link launches a Python file in the FrontLine program folder named CommissionPaidUpdateFLFL.pyw where FLFL is the name of the database in use.

- Links in the Third Party panel of the Welcome window now attempt to launch from an ACC\ folder beneath the main FrontLine folder, and the .pyw links are .exe when used from the ACC\ folder. If the ACC\ folder doesn't exist, or the linked program does not exist in the ACC\ folder, then FrontLine will look in its main program folder as before.

- Added a new security context Cash Tenders under both Customer Orders and Purchase Orders of Access Profiles to restrict user access to tenders that are not On Account.
~ Lack of Read permit obscures the Account Number, Expiration, and Check Number of tenders that are not On Account.
~ Lack of Add permit prevents manual addition of tenders that are not On Account.
~ Lack of Modify permit prevents changes to existing tenders that are not On Account.
~ Lack of Delete permit prevents user removal of existing tenders that are not On Account.

For sites that do not require any restriction, one can give all users who have access to customer orders and/or purchase orders the same access to Cash Tenders without editing access profiles in FrontLine by executing this SQL:

The Db Console contains two required updates:
File: NewInvoice v6.5.049 This db update is backward compatible
File: CostInvoice v6.5.049 This db update is backward compatible to 6.5.033

- Fixed: Depot repairs did not update equipment set membership with the replacement unit. This revision is in the CommitInvoice db procedure.

- Fixed: Dropping an unplaced Equipment Sets member into a set using Group Together.

- Fixed: Adding multiple similar packages with set eligible members to a customer order could result in the Equipment Sets members from different instances of the package (different line groups) mingling groups.

- Fixed: A recent revision made Equipment Search miss customer equipment that was not sold on a FrontLine order.

- Fixed: A recent revision disabled the eMail sections per recipient unattended function in the report output preview window.

- Fixed: Return from depot of a depot repair unit that was send out on line 10 of the service order created a line zero for the receive from depot line item.

- Fixed: In Transaction Inquiry the option for Type Sales did not exclude Payments.

- Fixed: Tax Write-Offs were not included in Tax Report batches as intended in the 6.5.040 revision.

- Added a WorkStation List Filter to help find entries in the WorkStation List. This filter will match values in any of the five columns, the left three by complete value if a number is entered, and the right two by partial text.

- Added a Company Setting ItemDescription on Forms to elaborate the revision made in 6.5.044. The default value is restored to only Miscellaneous Items.

- The Cardholder Information window no longer brings in the bill-to address by default. Instead there is now a button to do this explicitly, if desired.
Street Address is no longer required.

- To prevent External Exception C0000006 FrontLine now copies itself (the executable) to a local folder and relaunches from this folder when it detects that it was launched from a network share on another server:

- Added three limits to Item Categories in Setup Lists. Rentals and Returns are exempt:

- Fixed: Deferring an open order with no payment tenders where the tenders had not be viewed could result in an error "qrPmt: Cannot perform this operation on a closed dataset"

- Fixed: Purchase Orders did not always assign the purchase location's default ship-to address to the PO by default.

- Fixed: The prorate revision in 6.5.046 did not work on a new order when the Placed date was still blank.

- It is again possible to edit external invoice numbers and dates of the Costing records in the check-in/out window per the 6.1.063 revision.
Note that changes made here are not logged yet.

- Added an Address Mapper to show address locations using Google Maps. It is available on some context menus as Map and Map All in maintenance windows that include addresses, the scheduler, and using Alt-M in other windows such as orders, transaction inquiry, and equipment search.
There are two aspects of this feature:

The Db Console contains two required updates:
ADDRESSES Coordinates (6.5.047)
TRXINV.CommissionPaid

- Fixed: Inventory Valuation for a past date produced incorrect quantities when the same unit had multiple separate lives.
For example, it was adjusted out then adjusted back in.

- Fixed: Removal of line items from Periodic Invoices on customer orders that were sold and returned in the same batch did not work in some circumstances.

- Fixed: The Remove Payment function is now disabled on orders that tendered payment for receivables.

- Fixed: Return lines within a Quote could cause incorrect sums in Quote Totals.

- Up to 3 additional orders can now be viewed in floating read-only order windows.
These orders can be opened from the Refers to... entry of another order, Unit Tracking, etc.
The floating order windows close when the user returns to the Welcome window, or the user can close them manually when they are no longer needed.

- Unit Tracking now shows when an event was committed as a separate date from when it was checked in or out if there is a significant difference.
Previously it only showed the committed date, which could be days apart from the check in or check out.

- When there was neither a Line Scheduled date nor Order Scheduled date, FrontLine did not prorate line items that were members of billing equipment sets.
Now it will prorate them using the Order Placed date. (If the order has no scheduled date then the order placed date is assumed to be the scheduled date.)

- Added a sticky Sort by Stock option to Recurring Billing Output to output line items within a bill by stock number to enable the form to summarize by stock item per bill.

- Recurring Billing Output now includes summary outputs StockTotal (total charged for this stock number on the bill) and StockQty (total quantity of this stock number on the bill) to summarize per stock item by bill (per OrderID).

- Fixed: The Returns feature now excludes depot return line items as not applicable.

- Fixed: The Remove Payment function did not use the current AR account specified for the order Location.

- Fixed: In some windows, moving the OrderID column to the leftmost position did not stick for the user after logoff.

- Fixed: The Historic option in the Identify Unit search window did not find old (replaced or deleted, not current) identifier values.

- Transaction Inquiry now includes an Invoiced column that shows the last time the line was invoiced. If it was invoiced more than once the latest date is shown, preceeded by an asterisk.

- Transaction Inquiry now includes a Sort By selector. Sorting can also be accomplished by clicking column headers. Note that not all columns can be used for sorting.

- Added a LineRefTotal field to the output of Forms for Orders.
For ordinary lines it simply reflects that line item's total.
For package lines and repair units lines that have other lines refer to them, LineRefTotal is the line total of all lines that refer to this line, including itself.
LineRefTotal can be useful to show the total costs assessed for repairs of a unit, or for package totals especially in package as discount mode.

- Increased the number of batches shown in the drop-down list for Recurring Billing Output to 200.

- The locations offered in drop-down lists of order windows now exclude Closed Locations.

- Fixed: Receivables would show a number of days overdue for receivables that were paid, although they were not highlighted in yellow.

- Receivables now highlights the OrderID and InvSeq parts of invoice rows that are part of a periodic invoicing batch in light blue/cyan.

- Within constraints of the customer credit limit, FrontLine will now automatically adjust an open On Account tender upon deferring an open order when the order total has increased.

- Physical Count now remembers the last count sheet sorting per user, and the quantity Unidentified is now shown in a separate column.

- Added an Item Status flag Distinct PO Lines to prevent the output of Forms for Orders for Purchase Orders from combining line items of the same stock number in the output to forms.

- The ItemDescription output from Forms for Orders now contains the Note Subject when the stock item description is blank for any item. Previously it only did this for miscellaneous items.

- Unquoting an entire Service Order quote with company setting Disable Auto-Commit under Line Unit Identify Options did not bring back the repair unit assigned before making the order a quote.

- Fixed: Bugs in the running Quote Totals calculated and displayed in the footer section of the main order processing window.

- Added two new optional criteria to Periodic Invoices: Ship Via and Order Identifier. Using either of these eliminates recurring bills from the batch.

- Fixed: Changing an order's bill-to (redirected billing) could raise an error about ChangeBillTo - Dataset not in edit or insert mode.
This bug was introduced in one of the multi-currency revisions.

- The main order processing windows now has running Quote Totals (Total Quote Items, Total Quote Taxes, and Total Quote) calculated and displayed in the footer section that appear when the quote total is not zero. Order totals also disappear when quote totals are non-zero and order totals are zero.

- Unearned Revenue disparity on Item Category Accounts exception in Recurring Billing has been restored to an all-or-none check (as it was before 6.5.041), and FrontLine now requires all potential recurring billing line items to have an Income account or it will indicate Income missing from Item Category Accounts.
Late Fee Billing now also requires all potential lines to have an income (revenue) account.

- Recurring Billing now posts Receivables with a due date based on the issued (placed) date of the bill rather than the billing period start (scheduled) date.

- The optional length limiting feature to the Excel expressions from Forms for Orders can now specify date output formats for date/time values.
Example to format a date output to "mm/dd/yyyy" style: ORDER.OrderScheduled;mm/dd/yyyy
Note that Excel will transform input text it recognizes as a date, so although the above expression writes "08/24/2015" to the cell, Excel recognizes this as a date and applies its default format, which is typically "8/24/2015" in the USA. Even a very different format like "yyyy-mm-dd" which has FrontLine output "2015-08-24" to the cell will still end up with Excel changing it to "8/24/2015" on the sheet.

- Fixed: Last Lead time (days) in the Vendor Performance available in Generate Purchase Order requires the vendor to have a part number for this stock item. However, for the default vendor the stock number can be considered the part number.

- When an equipment set location used in Recurring Billing was missing item category accounts altogether, FrontLine intentionally did not indicate an Unearned Revenue disparity on Item Category Accounts exception in the Exceptions and Batch Review step, to facilitate early AR transitions.
This exception is now triggered if any line or all lines on the bill would be missing the unearned revenue account,
so it is now Unearned Revenue missing from Item Category Accounts.

- It is now possible to preview Costing during customer order checkout when the invoice is created but not yet committed.
These cost details in the invoice window cannot be edited, and are outlined in yellow to emphasize that they are estimates.
They are estimates because there is a chance that costs can change between the time of the estimate and the final time of costing.
Part of this revision requires an update to the db procedure CostInvoice.

- Receivables now offers a Write Off Taxes function on the context menu.
The user is prompted for an optional Applied date override.
The account used in AR is the same as for ordinary write-offs.
A user must have the Modify permit for the Receivable Payment security context to use this function.
A tax write-off can be either a credit (DocType=15) or debit (DocType=14) with the distinct DocType flag 8.
A tax write-off creates tax return details in TRXTAX similar to a return. The TRXTAX.InvSeq is the original InvSeq plus 65536 to make a distinct key.
New Tax Report batches will include unreported write-offs from the past even before the date bracket.
A tax write-off cannot be undone after it has been included in a tax report.
A tax write-off marks the invoice as having taxes written off, using INVOICES.InvStatus flag value 8192.
Returns of items whose sale had taxes written off should return no tax.

- Fixed: Choosing to Create Order from a Scheduler Event raised an SQL syntax error.
This bug was probably introduced in 6.5.036

- Added a CM_=Commissions Report Group. The standard report groups are now:

AR_=Accounts Receivable
S_=Sales
SE_=Service
CM_=Commissions
P_=Purchasing
F_=Fulfillment
T_=Taxes
R_=Recurring Bills
I_=Inventory
C_=Customers
V_=Vendors
Z_=Diagnostic

- Fixed: A recent revision caused the posting of receivables during invoicing to fail on PostgreSQL databases with an error:
Data conversion is not implemented for datatype Date to DateTime

- Fixed: Lookup column arrangements did not always save correctly when Save Arrangement was used.
This fix will throw off existing saved arrangements, so columns will have to be rearranged and sized once more then saved.
This fix also affects the column arrangement retention in Transaction Inquiry.

- Fixed: Opening a line note for a line that doesn't have a note, then closing the note without saving it could leave FrontLine indicating the presence of a line note. This bug was probably introduced in 6.5.025

- Fixed: FrontLine excluded equipment set members that are on open line items of origin from recurring bills, however this exclusion did not cover intangibles - services and charges.

- Unquoting an open Job quote will now attempt to create Resource Costs Job Budget numbers as 6.4.052 did for presented quotes. Note that if resource costs already exist for a line item they will be left as-is for that line

- Added a Sequence column to the Equipment Sets member list. This sequence is used to sort the lines created on recurring bills.

- Fixed: 6.5.035 introduced an error when entering an application or write-off date override in Receivables that is more than 14 days from present as it attempted to ask for confirmation.

- Fixed: When Item Quantities were displayed with the Inventory and Committed tab in sync with Item Lookup, the inventory and committed details did not update when scrolling through the list of items in the Item Lookup window.

- Added an ability to change the "Unit Cost" of the costing assigned to an Invoice.
To do this a user must have the Modify permit for access context Invoiced Unit Cost in Class "Purchase Orders" found in Access Profiles.

- Technician (limited) users are now allowed to create an order in Scheduler Event for events that have no order associated with them.

- Fixed: When a credit in Receivables was written off entirely, then the write-off cancelled (Unapply) the credit could not be applied to other receivables because the Application command was disabled.

- Receivables now have an Applied date that defaults to the posted date but can be overridden by the user at time of application. This revision requires a database update.

- If a user has a Special permit to change an Order Agent they can do so after the order is invoiced or closed using the drop-down entry on the order header Agent title. Assign the Special permit to the Order Agent context in Access Profiles by typing in an S for the Access Level.

- The list of orders and line items offered in a Scheduler Event to create a line item for the event now has a More... entry when there are too many candidates to list at once.

- The Refers to, Reference Orders, and Redo Order drop-down has been moved to the OrderID column title of the order header display to make it more accessible.

- If FrontLine lists completed orders with the "In Use" status flag set when Order Lookup is used, FrontLine now removes the in-use flag from all orders it finds in this condition.

- Fixed: Returning a partial quantity of a non-identifiable item that was on a customer's equipment set would remove the equipment set member in cases where it should have reduced the member quantity instead.

- Fixed: Inventory Valuation could not distinguish between the varying costs of unit-costed units checked in/out together on one line item. This fix also requires the database updates below.

- The S.Find function in Equipment Sets now includes the ESet ID in its display grid and will match IDs to Search Text entered.

- 6.5.001 introduced to Company Setting Order Activity Reactions an option to Immediately mark All Units "To Repair" as "Repaired" When user indicates Order is Serviced or Ready.
Now when this option is on and a service order is marked as no longer Serviced or Ready FrontLine sets committed Repaired units that have not been shipped back to To Repair status.

The Db Console contains two required updates:
TRXINVCOST.DtlID (6.5.033)
File: CostInvoice v6.5.033

- Fixed: Unit Tracking could raise an access violation when there were event notes.

- Fixed: If the location of the receivable is known, write-offs made in Receivables should default to the Discount account from that order location instead of the workstation location.

- Fixed: A recent revision caused an Ambiguous column name OrderStatus error in Purchase Order Lookup for Pending Orders.

- Setup Identifiers now has a !Rent flag to indicate that the identifier is required for rental transactions. Rental transactions still require identifiers that are required for sales.

- Added an option to Company Setting E-Sets, Rentals, Contracts to Zero-Price Rentals that are added to Equipment Sets (as an alternative to Pro-Rate Rentals and Post-Rate Rentals) that will pro-rate both the outgoing rental and the rental return order line at zero.

- Added a Refers to Order nnn function below Redo Order to open the order or quote that this order refers to.
This function only appears when there is a reference, and is the reverse of Reference Orders that lists orders that refer to this one.

- Added some highlighting to Discontinued items listed in the Scan Match window.

- Fixed: Entering an Order Scheduled date before the order was created would raise an SQL error upon creating the order.
This bug was introduced with a recent logging enhancement in 6.5.027

- Fixed: The optional Stock number column in the Import Customer Equipment feature was not applied to the equipment.

- Depot return line items are now added using line numbers close to the original (+10 or -10) if possible, when line increment of 100 is used.

- In Customer Lookup, Closed customers (included on demand) are now highlighted in the void pink color.

- Miscellaneous purchase lines added to a PO from Miscellaneous Purchases now merge the customer order note body text with the Source Part as subject from the customer order Resource Costs into the PO line note. Previously only the Source Part was placed in the PO line note subject.

- Fixed: Order Status display texts erroneously included Hold when the order was Submitted.

- Fixed: Changing Scheduler Event details then Mailing the event before saving it would send the previously saved details in the iCalendar (ICS) attachment.

- Added contact phone number and event street address to the iCalendar (ICS) attachment, and moved some information between the Location (Where) and Description (contact info is now here instead) to better suit calendar event mapping services.

- Added an event status As Unidentified that applies when a sale or rental unit was committed before it was known in the system. Inventory Transactions shows units that were committed unidentified but are now identified with the unidentfied icon with a green check on top of it.
Note that events committed unidentified using prior releases do not have this flag, so they will not have the indication in Transaction Inquiry if they are now identified.

- Added a SUMS dataset to the outputs of Forms for Orders to provide subtotals of line item types. Note that these sums are not available in batch outputs.
To use these fields add a SUMS dataset to a form to make available:
TotalTangibles, TotalServices, TotalCharges, TotalPayments, TotalQuoteTangibles, TotalQuoteServices, TotalQuoteCharges, TotalQuotePayments

- Fixed: Presenting a Quote removed the Prospect customer flag introduced in 6.5.028

- Fixed: Receiving partial quantity of an inventory member of a package purchased in quantity greater than one by clicking the ready checkbox, then responding Yes to the question "Do you want to indicate that this line is ready to check in before receiving the ordered quantity?" resulted in the wrong package member being marked ready.

- Purchase suggestions listed by auto-gen in the Generate Purchase Order and Miscellaneous Purchases windows now show an icon for customer special order line notes, and provide a means to open those line notes.

- Added a light green highlight to Receivables assigned a Pay Now amount when receiving a payment.

- Rentals returned via the Returns window now omit line items where no previously rented units can be committed to return.

- The order location display in the order entry window is now highlighted when the user has option New line items to workstation Location and the workstation location differs from the order location.

- Added Delivery Status Import to the Third Party panel in the Welcome window. This link launches a Python file in the FrontLine program folder named DeliveryStatusImportFLFL.pyw where FLFL is the name of the database in use. See the Telus integrations release notes and the .pyw revision in 6.4.042

- Fixed: The timing and Invoiced date of write-offs made at the time of taking payment now matches the payment itself in receivables.

- Fixed: The change log enhancements in 6.5.027 exposed a bug that could cause key violations upon saving a new address for a new customer.

- Fixed: As of 6.5.023 the line ready checkbox on Purchase Order package lines did not become ticked when clicked. This made it impossible to check in a received package until the entire PO was marked Complete.

- Added a Prospect flag to Customer Status.
When a customer order is invoiced this flag is removed from the customer record.
If desired, use the customer template to make new customers prospects by default.
Customer Lookup results can be filtered by Prospect, and there is a special lookup to list all Prospects.

- Elaborated the iCalendar (.ICS) email information for scheduler events introduced in 6.4.090 to include names and email addresses of all recipients as participants.

- Added a Technician Count Key to Company Setting, and both technician (limited) and standard (full) licenses can now have expiration dates up to August 1, 2026. After an expiration date has passed FrontLine displays a warning upon login. Licenses are no longer valid a week after expiration. Users under a technician (limited) license can now modify orders opened from scheduler events.
Note that Count Keys generated in FrontLine after this revision may not be recognized by older revisions of FrontLine.

- Fixed: After changing a service order's agent and responding Yes to the prompt asking to change the agent of all existing lines, a user's Show Identifiers when unit is committed option stopped working until the order was deferred.

- Fixed: Unquoting a repair unit line item (or service order) did not recommit repair units whose last event was shipped with a shipment tracking number. This fix is in the quoting process, orders quoted with prior releases may still unquote without recommitting the unit to be repaired.

- The Change Log for Items now logs changes users make to Purchasing Quantities and Item Costing, excluding the layers.

- The payment remark text when a customer has insufficient credit is now different when the customer is already over their credit limit. This way the monetary number shown is always positive.

- Added an ability for custom reports to list values from Lists. Example to use the ShipVia list:

- Fixed: A recent revision made an order in use that is taken over remain read-only.

- Fixed: A bug in the analysis of a customer's available credit before accepting on account tenders during order entry.

- Fixed: Warranty Vendor Invoice prices on returns should use the original invoice price instead of the current price. This fix is in the NewInvoice db procedure.

- The Rental line items Price Levels value is now used to price and pro-rate rental units on Equipment Sets. This revision also requires a database table update.

- Output of line items from Periodic Invoices excludes customer orders that sold and returned in the same batch for the same price.

- Output from the Print All as regular invoices function in Periodic Invoices now uses the BillToContactEMail field as a MailTo address to enable the eMail sections per recipient unattended function in the output preview window.

- Added an option New Customer Order defaults as Quote to the User Options available in System Users. The user must have permission to create quotes.

The Db Console contains required updates File: NewInvoice v6.5.026 and TRXIP.RefPrice (6.5.026).
Both of these db updates should be backward compatible all the way to 6.4.064

- The green (committed quantity equals ordered quantity) and red (overcommitted) outlines in the quantity column of line items in order entry now fill the cell.

- Added Conversation Notes to the Notes window for entities (Entity Notes). Multiple conversation notes can be entered for an entity. The list of notes can be filtered by who entered them and the leading note texts and subjects. The text filter examines the complete subject (up to 80 characters) but only the first 240 characters of the note body text. Beware that the filters can be set such that a note just added doesn't appear in the list, for example if one has it filtered for another user or a text fragment that doesn't appear in the new note. See the Note Groups section for data keys.

- Fixed: Returns of Warranty Vendor Invoices now post Credit Memos instead of negative Invoices to AR.

- Fixed: Analysis of a customer's available credit before accepting on account tenders during order entry failed to consider AR payments covered by the customer's parent.

- Fixed: Another case of Equipment Search showing multiple rows for the same customer equipment when that equipment was on a recurring bill credit.

- Fixed: When using Font Size 14, the header and footer section of order windows had insufficient vertical space, so character tails of data texts were cut off.

- The Unit Warranty window now includes a button to assign the default vendor as the warranty vendor. This can also be accomplished by entering a hyphen into the vendor number or name field.

- Recurring Billing Output now includes ESetID in the output data available on the bill forms.

- After completing a shipment from FrontLine Shipping, if a tracking number was assigned and a mail relay configured, FrontLine opens an email composition to the relevant agents. The email address helper is available in context of the order if Order Combination was not used.

- All outputs from Forms for Orders now include the PROBLEM dataset, enabling the use of problem codes on invoices, etc.

- Added a Set All Mail Logins function to the System Users window to simplify assignment of identical mail relay login credentials to all users.

- Rental line items will now use a price from Price Levels that matches the rental location.

- The WorkStation List in FrontLine Setup now has a Rental Location column to optionally indicate the default rental location when Short Term Rental is selected on a blank customer order.

- Fixed: Moving an equipment set member from one set to another then invoking the context menu could raise an SQL key violation of PK_ESDTL.

- Fixed: Repeated Order Lookup by an order identifier using a different value did not update the results to use the new search value.

- Fixed: A recent revision could cause SQL errors on Customer Lookup, for example when invoked by typing into a customer order's Ship-To address.

- Fixed: Warranty Vendor Invoices used the line quantity unequal once too many times to figure the effective total. This fix is in the NewInvoice db procedure.

- Fixed: Warranty Vendor Invoices now only attempt to use the item's generic standard cost, no attempt is made to use the item's last cost or a location-specific standard cost. (If the item's generic standard cost is missing then the line price on the service order is used.) This fix is in the NewInvoice db procedure.

- Unused Billing Frequencies can be disabled in Setup--Lists by assigning them Display values starting with a hyphen.

- A Write-Off performed in Receivables in a customer context (not from an order) now prompts for an Amount to write off.

- The drop-down menu under AR in Customers maintenance now has Orders and Quotes functions that provide lookup lists of this customer's orders and quotes, which can be opened from the list to view in detail.

- When a customer order's Scheduled date is changed and it has set eligible line items without independent scheduled dates, FrontLine can now update those ESet members' initiated date and re-prorate if the user confirms.

- Purchase Order check-in now uses the ready/complete status of the order or line items to skip line items not ready. This allows intangibles (like services) to be omitted from a check-in when necessary.

- In Shipping, the icon shown for repair units now also indicates if they were under coverage using the umbrella icon, as they would appear on the service order.

- Searching by Event Category in Scheduler Event Lookup now lists events with most recent begin date first.

- Elaborated the Transact Unidentified security context to limit specific Item Action choices for Unidentified:
~ Lack of Read permit disables the Repair (aka Service) option.
~ Lack of Add permit disables the Sell option.
~ Lack of Modify permit disables the Exchange option.
~ Lack of Delete permit disables the Return option.

- Added Vertex Standard Catalog Update to the Third Party panel in the Welcome window. This link launches a batch file in the FrontLine program folder named VXCatUpFLFL.CMD where FLFL is the name of the database in use. See the MOL Catalog Update release notes.

The Db Console contains a required update for warranty vendor invoices File: NewInvoice v6.5.023.

- Fixed: When company settings had FrontLine check item category accounts as a repair unit line item was created, it failed to change the location checked to the order location beforehand when the company setting Repair Units in Order Location was selected.

- FrontLine will no longer overwrite assigned line item Accounts after the user has set any of them on that line.
These line items have a new status flag Custom Accounts Assigned (CAA) in TrxStatus when the user chooses an account.

- If a Total Paid amount is entered in the Receivables window before choosing Any for a non-specific payment, FrontLine now creates a payment line item for that amount instead of the total receivable balance.

- Added an Optional Write Off Date prompt in the Receivables window when writing off a receivable or credit. If entered, this date is assigned to the Invoiced date of the write-off. FrontLine prompts for additional confirmation if the date entered is more than two weeks away (past or future) from today.

- Added an optional Write Off Limit to Access Profiles to limit how much a user can write off per receivable.
The write off limit is evaluated in base currency. Blank is unlimited. The system administrator's write off limit is 1.

- Returns of entire unreturned customer orders now offer a Payment Undo option to return the tenders.

- Added a Remove Payment function to context menu of order payments to indicate that a Check or Card payment was rejected after invoicing.
This function adds a payment for negative amount and same type as the original tender, and adds an equivalent On Account tender to take its place.
Notes can be added to the original tender even if the order is closed.
The new receivable is posted right away, using the original invoice date.
The records created in PAYMENTS by this process have their InvSeq inflated in a recognizable pattern*, and the original rejected tender has its VerifyCode modified for recognition.
* To match or join these records to the original InvSeq, mask out the inflation bits with an expression like this: (PAYMENTS.InvSeq & 65535) = I.InvSeq

- The information bubble that appears upon pointing to a Scheduler event on the scheduler board now includes a list of Participants starting with the primary participant.

- Notification When and EMail To are now available in the Scheduler Event window to enable the auto-mailer for scheduler events.

- Added a basic Change Log viewer to the drop-down menu next to the Parts button in Items maintenance.

- Fixed: Vendor Warranty Invoices on warrantied service order returns were not negated. This fix is in the NewInvoice db procedure.

- Fixed: Changing set eligible line item quantities on a customer order that was unquoted did not synchronize the equipment set member quantities correctly.

- Maintenance windows with addresses now have a Find All References command in the address list context menu to find all (Customers, for example) who have this address record associated with them.

- The Print All as regular invoices function in Periodic Invoices now provides an email address helper for the invoice output if the periodic invoice batch included only one entity.

- Added a Company Setting for AutoMailer Configuration to enter information required by the new auto-mailer feature. Note that the auto-mailer can use a different mail relay from location users, and all the email it sends uses the one return address.

- There is a new FrontLineAutoMailer program that sends Notes with suitable Notification information.

The Db Console contains two required updates:
NOTES AutoMailer (6.5.020) and File: NewInvoice v6.5.020.

- Fixed: Equipment Search could show multiple rows for the same customer equipment when that equipment was on a recurring bill return, or was the repair unit on a service order return.

- Fixed: Inventory Valuation on a Date in History between a sale unit's committed date and invoiced date considered it sold instead of inventory.

- Fixed: After setting Base Currency to Canadian dollar (CAD) in Currency Options, then reopening the Currency Options window, it would then incorrectly select Australian dollar (AUD) as Base even though CAD had been correctly saved.

- The warranty sum outputs to Excel worksheets (TotalPartsW, TotalServicesW, and TotalChargesW) from Forms for Orders now use list prices instead of order prices.

- Fixed: Top bar buttons in maintenance windows could respond incorrectly to click position.

- Fixed: Clicking View Jobs on an empty customer order would assign an OrderID unnecessarily.

- Forms for Orders for Customer Orders now has a facility to Select Order Identifiers to appear as columns in the output data.
Four identifiers can be selected, their outputs named OUIValue1, OUIValue2, OUIValue3, and OUIValue4.
These values can be used in batch outputs, and the selections are sticky per user.

- Fixed: Customer discounts are not applied to intangibles (services and charges) on vendor warranty invoices. This fix is in the NewInvoice db procedure.

The Db Console contains a required update File: NewInvoice v6.5.017 to implement the vendor warranty invoice intangibles cost fix.

- Fixed: Voiding (reversing) a collected payment could result in incorrect payment list output to forms.

- Fixed: The Sell Items On Hold security context Modify permit implemented in 6.5.015 to restrict Exchanges did not prevent an exchange that began by pressing the Exchange button before entering a Scan Code.

- Fixed: When the repair part was simply consumed from inventory, FrontLine failed to mark a warrantied repair part line on the service order warranty invoice as ordered on a Warranty Vendor Return Authorization to inform the Warranty Vendor Return Authorizations generator not to suggest ordering it again.

- Fixed: Transaction Inquiry now only retrieves Resource Cost for line items that are services, charges, or miscellaneous.
And because the Cost and Ext Cost columns are based on inventory costing, they have been relabelled Inv Cost and Ext Inv Cost.

- Added a simple Cost to outputs from Forms for Orders that contains one of the following in order of preference:
Location Last Cost, Location Standard Cost, Item Standard Cost.

- Added an optional length limiting feature to the Excel expressions output from Forms for Orders by ending the expression with a semicolon followed by the maximum length desired. Example to limit to 12 characters: I.Desc1;12

- Fixed: Identifying customer equipment for repair on a blank order using Scan text where the equipment owner's customer status only allowed quotes did not record the equipment identification on the service quote.

- Fixed: The Item Action prompt for Discontinued or On Hold items now handles the user's Sell Items On Hold security context permit more elaborately:
~ Lack of Read permit disables the Repair (aka Service) option.
~ Lack of Add permit disables the Sell option.
~ Lack of Modify permit disables the Exchange option.
~ Lack of Delete permit disables the Return option.
The four consequences are written as negatives because other conditions can also disable various actions.
Even if the user's permission allows it, the Item Status Check prompt requests confirmation before adding the line item.

- The Destinations list in Shipping now considers the Include Parts option: When off the list of destinations is now likely to be shorter.

- Added a Repair Units in Detail Lines option to Periodic Invoices to keep repair unit line items and not transfer their identifiers to individual parts and services linked to them.

- Added a Stock Identifiers tab to Items maintenance. There is a corresponding Stock Items template where the individual identifier types are assigned in Setup Identifiers.
Unlike Preset Identifiers that may be automatically copied to Unit Identifiers at time of sale, Stock Identifiers are simply additional information about an Item on file.
Stock Identifiers can be assigned to inventory items, services, charges, catalog items, etc.

- Fixed: Periodic Invoices batches for customers could include the related warranty vendor invoices when a Customer Number Pattern was used.

- The context menu for the Bill To list in Periodic Invoices now has an option to Remove the selected Invoice or Bill from the batch.
This function is secured by a Modify permit for the Periodic Invoices context.

- The Scan Match feature for Customer Orders how has a Service Quotes option to list service quotes on which as unit has appeared when the scan code matched a unit identifier.

- Added a Last Received column to the main listing in Inventory Valuation. Unit received dates are shown as before in the Details listing.

- Added a Show Identifiers when unit is committed option so Identifiers in Line Item Details are presented when a unit is committed for sale to a customer order to User Options.

- Equipment Sets and Service Contracts can now be priced in their own currency. Billing Currency can be assigned per Equipment Set.
Equipment Sets with no currency specified are assumed to be in Base Currency and will be billed in base currency.

- Fixed: Rates displayed in the Currency Exchange Rates window showed only two decimal places.

- Fixed: Lack of a "Delete" permit for Items Physical Count did not prevent a user from cancelling a physical count sheet.

- Fixed: In the Quantity of the Receive window for the first receiving after login, the first two digits entered were transposed.

- Fixed: A recent revision allowed a closed line item's Special Order property to be changed in the Line Item Details window.

- Fixed: A user without Customer Orders Equipment Owner Modify permit could change the customer of an open order with customer equipment already committed to it.

- Lower case coordinate parts output that includes values after the decimal point can now specify inclusion of leading insignificant zeroes (left of the decimal point) using a format mask like %2s (seconds with fractions) similarly to how this could (and still can be done) for upper case (no decimal fractions) using a format mask %.3D (degrees without fractions) (notice the case difference and the inclusion/exclusion of the period).

- Fixed: Order Lookup for Orders Completed Today did not discriminate between customer orders and purchase orders.

- Fixed: Taxes calculated by Late Fee Billing did not round the Taxed Value correctly.

- Fixed: Periodic Invoices did not always sort correctly for the Sort by OrderID option.

- Fixed: The year long calendar shown in the Scheduler Event window did not shift display to the starting month of the event when the event did not already indicate Specify Days recurrence.

- The Units of... grid in Physical Count now shows an estimated unit cost if the user has permission to see Cost in the Items section of their Access Profile.
This Cost is available in the export and report.

The Db Console contains a update required for Physical Count File: Physical Count Unit Costs (6.5.010)

- Periodic Invoices now has an option in the context menu to Consolidate Repair Consumption.
The line detail rows output for repair parts, services, and charges to "Details with Identifiers" in the window and the INVOICE dataset for the report are consolidated per repair unit line per type - Inventory (Part), Service, and Charge.
Consequently details about those parts, services, and charges are lost. They are simply described as their type, and identifiers output belong to the repair unit.

- Fixed: Entering a specific tender amount on a foreign currency order did not convert the underlying value to base currency.

- Fixed: The Item Status Check did not allow a user to sell Discontinued items even when the user had permission to Sell Items On Hold.

- When a time is entered without a date in a datetime field, FrontLine now assumes the intended date is today instead of a fixed date in 1899.
See more information about relative date entry in the 5.5.0220 release notes.

- Added a StockCE (where CE stands for Contract Equipment) output field to Recurring Billing Output to provide the stock number of equipment covered under a contract recurring bill line.

- Fixed: Receivables posted by Recurring Billing did not use the customer currency.

- Periodic Invoices now has a Vendor Invoices option to collect warranty invoices to vendors from customer orders.
The output uses a form PeriodicInvoicesVendors.rep in place of the standard PeriodicInvoices.rep form but all the data output is the same.

- Fixed: A recent revision broke the display of options previously selected in some Company Settings.

- Recurring Billing and Late Fee Billing now use and output customer currencies.

- Recurring Billing now copies the equipment set member Group [ESDTL.ESGrp] to the bill line item LineRef [TRX.LineRef], and Recurring Billing Output sorts by this value so member groups appear together and can be grouped on billing forms.

- Receivables now display and handle multi-currency input. FrontLine does not yet handle the closure of receivables paid off after exchange rates change.

- Added a new Item Status flag Simple PO Cost to indicate that when the item is place on a purchase order, FrontLine should not look for the vendor-specific last cost. Instead it will simply use the location last cost, or standard cost if no last cost is on record. This flag affects assigned PO line cost entered either manually or by auto-gen, and the Last Cost shown in the Generate Purchase Order window.

- The OrderRef output from Forms for Orders in Purchasing now indicates if the referenced order is Voided or a Quote.

- Fixed: FrontLine will no longer commit inventory Received for a Customer Special Order to the customer order line item if the customer order has been voided.
The inventory can still be received, but the Receive window will indicate the Voided status in a yellow highlight.

- Fixed: Physical Count failed to adjust unidentified on both ends of the chain of events when the count entered required it to do so.

- Fixed: The Warranty Vendor Return Authorizations generator ordered parts used under warranty as returns.

- Enhanced the Destinations label in Shipping to offer a drop-down list of Ship Via methods to filter the list of destinations.
The list can also be activated using the F2 key.

- Fixed: SQL error opening purchasing from the introduction of multi-currency support in 6.5

- Fixed: Physical Count handles unidentified quantities better will less confusing presentation to the user.

- Company Setting Order Activity Reactions now has options for When user indicates Order is Serviced or Ready:
Immediately mark All Units "To Repair" as "Repaired" (new)
Set Order "Fulfilled" Date and Time (introduced in 6.5.000)

- Company Setting for MOL Vendor can now select either an individual vendor or a Vendor Category.
If a vendor category is chosen, then the Third Party Export MOL feature provides a drop-down list of the vendors in this category to start a new export batch.

- Fixed: FrontLine now inspects Receivables when checking if a customer can be deleted.

- Fixed: Order Returns from an earlier rental order would also return units that had been returned and subsequently rented out again.

- Added to Company Setting for Order Activity Reactions a new option to Set Order Fulfilled date+time when user indicates Serviced (Ready).

- Fixed: A recent revision made the Company Setting for Shipping Charge % displayed the description where it should display the actual percentage. Data on file was unaffected.

- Fixed: Toggling on POS for an order in a location flagged Tax On Location GeoCode used the wrong Tax GeoCode if the order location differed from the workstation location.

- Fixed: Changing the price of a company Shipping Charge ID return line item would result in taxes calculated with the wrong sign.

- FrontLine now encrypts connections to email servers using only TLS, older (SSL) encryption protocols are no longer supported.

- Fixed: A recent revision could make FrontLine miss the warranty status of a repair unit when assigning repair parts and services to it.

- Date Range in the Tax Report log is now recorded in a standardized yyyy.mm.dd format regardless of the company date format.

- Fixed: A recent revision broke the Price Levels copy that is offered when an item is copied in Items maintenance.

- Fixed: When an unidentified unit was used to create an inserted line item, the identifiers entered in the Identifier Document window were lost to the unit.

- Fixed: Reopening a first service order after login then closing it without viewing a repair unit's Repair Codes could result in a loss of the Repair Codes assigned.

- The email address helper is now functional in context of a Receivable Statement when only one customer is listed for statements output.

- Fixed: The Reference Orders function introduced in 6.4.012 could list orders unrelated to a return order in view.

- Fixed: An assertion error occurred saving a user's Print Options as an administrator from the System Users window.

- Fixed: An inserted repair unit line item was not offered in the repair assignment menu until the order was reopened.

- Added a + Recurring Bills and Late Fees option to Transaction Inquiry to include recurring bills and late fees as desired so they don't always clutter the output.

- Added an <All Cash Equivalents> option to the Tender choices for the Drawer Reconciliation Report to output all but On Account tenders.

- The rental Reservation feature now has options for [Cumulative] Reserved quantities in the Projected Quantities list and an [All] toggle for the Projected Period Details list. These options are toggled by clicking the colored titles above the lists. When active, relevant information is highlighted in color for distinction from the other information listed.

- In the rental Reservation feature, late pick-ups that are past the end of their reservation are now excluded altogether, while within their reservation period they are included and shown in Projected Period Details with a clock icon. Late returns still rented out past their scheduled return date are also indicated with a clock icon, and it is now possible to directly view the relevant Equipment Set.

- Fixed: The Projected Period Details listed in the rental Reservation feature did not change for the Period selected in the Projected Quantities list.

- There are new separate security contexts for Miscellaneous Purchases and Warranty Vendor Return Authorizations in the Purchase Orders section of Access Profiles. An Add permit is required to use these PO line generators.

- Added a Warranty Vendor Return Authorization function to the autogen menu in purchasing, to open a new Warranty Vendor Return Authorizations window.

- Fixed: The recently introduced Order Status update bug now affected orders after check through.

- The Item Image line item context menu entry has been replaced by an Item Info entry that opens a submenu with Item Image and item specifications entries that provide links to file or web pages that can be opened.

- Fixed: A recent revision disabled removal of Order Status codes (like Quote) from the database record.

- For addresses in countries outside the USA and Canada, FrontLine will no longer prefix the current location's 3-digit area code to phone number entries when only 7 digits are typed in.

- Items maintenance now has a Specs tab where multiple ad-hoc specifications can be listed for an item model. Each entry can be one of:

- Fixed: Recurring Billing did not exempt recurring bills to tax-exempt customers.

- Fixed: Delivery Tickets were missing the SigInvoiceName output for invoice Signatory Name.

- Fixed: The Only Service Orders option in Periodic Invoices did not conform with the 6.4.089 revision to qualify service orders.

- Fixed: When the same unit was adjusted out then back in, Inventory Valuation did not stop at the adjustment for unit cost assessment.

- Customer Special Orders checked out with option Cost Special Order sales by special Purchase Cost in Company Setting Cost Options will now use the cost on the PO line item itself when the PO has not yet been costed instead of defaulting to the item's costing method in this case.

- Printing an Invoice during check out of a customer order with vendor invoices now offers a choice [Customer vs Vendor (W)arranty] like it does when printing existing invoices.

- When an order is Unquoted, the question to unquote lines has been replaced with a simple confirmation. When the order is unquoted, all of its lines are also unquoted.

- When a customer order not flagged a quote but with all quoted line is checked out, the order itself is now flagged as a quote. This revision is in the CommitInvoice db procedure.

- Unit Price of Warrantied line items can now be changed. The line effective amount remains zero.

- Added a context menu with a Restore function to the Identifier Document History window to put back an identifier that has been deleted from the current document. This feature is available when the user is allowed to edit the identifier document but is not in edit mode.

- Added an Item Status flag Warranty V-RA to indicate that this item is sent back to the vendor for warranty claims. Otherwise the warranty vendor is invoiced for the cost of the item.

- Warranty Invoices introduced in 6.4.064 now apply to all tangibles and intangibles. See the 6.4.064 release notes for conditions. On the Warranty Vendor Invoice:

The Db Console contains three required updates:
File: NewInvoice v6.4.106
File: CommitInvoice v6.4.106
File: CostInvoice v6.4.106

- Fixed: The addition of Desc1 to Equipment Search in 6.4.091 broke the display formatting of identifiers in the results.

- Fixed: Return lines with a reference to the sale would miscalculate return taxes when the return price was changed.

- Fixed: The default Cost assigned to PO lines should ignore PO returns and adjustments.

- Fixed: When the Shipping function added a freight charge to an order it did not consider whether that order was tax exempt.

- Fixed: 6.4.064 broke collection of subsequent invoice tenders on a customer order where the bill-to customer changed between invoices.

- Fixed: Item Category Accounts assignment to a Line Item did not reject when a Department was specified on the order but there was no match in the accounts list.

- Fixed: If repair parts and services linked to a repair unit line were not checked out when the repair unit line checked out, they could end up impossible to check out. This fix is in the NewInvoice db procedure.

- Revised the Company Setting introduced in 6.4.097
Do not warn users when an address has no matching Tax Geocode
to Do not warn users when an address has no Tax Geocode assigned
Remember that when using this option, all locations where customer transactions take place should be flagged Tax On Location GeoCode.

- Added Rentals Third Party at Customer Site to Customer Order Lookup to find customer orders with subrentals still at the customer site.

- Added Open Third Party Rental Orders to Purchase Order Lookup to find open orders to vendors intended to fulfill subrentals.

- Added Third Party Rental support, for subrentals from a vendor to fulfill customer rental needs.

The Db Console contains required updates File: CostInvoice v6.4.104 and File: NewInvoice v6.4.104
These updates are compatible with earlier versions of FrontLine.

- Fixed: Recurring Billing and Late Fee Billing did not consider a location's Tax on Location GeoCode option.

- Added an Event Categories column to the Scheduler Event Lookup result list, and activated this field for Search By and Filter By.

- Added a Sort Service Orders by Repair Equipment toggle to a drop down from the Line # column title on Customer Orders.
The default value after login is determined by a new Lines sort around repairs on Service Orders option added to Company Setting Return, Repair, and Unidentified Options.
The line view sorting introduced in 6.4.099 can now be toggled on and off at will, and when off lines can be inserted on service orders.
When on, Charges not linked to a repair equipment line are now listed last.

- The Print Summary output in Receivable Statements now follows the sort order chosen for the statements in the upper right of the Print Options section.

- Added a Customer and Purchase Order Lookup Unfulfilled Lines On-Hold to find orders with open tangible lines that are on hold and not completely fulfilled.

- The BoxQty output to Packing Slips is now a total quantity packed in the box for the line item.

- Fixed: Under some circumstances, after entering a new line item on a new order, and changing its price, then changing the order customer, the line item's price would erroneously revert.

- Fixed: FrontLine now refuses to insert a line on a Service Order because the line view sorting introduced in 6.4.099 could make the insert reuse a line number, resulting in a key violation.

- Fixed: The Jobs window did not accept letters I or P for text input due to the hot keys for Job Identifiers and Job Phases lists. These shortcuts have been removed.

- Fixed: After Shipping before printing Packing Slips, an empty customer order window could appear, obscuring the Packing Slip: Shipping window.

- Added an On Hold toggle for line items on customer orders that excludes the line from purchasing demands. The flag is indicated on the line by a Zzz icon. This flag affects auto-gen in the Generate Purchase Order window, it does not prevent fulfillment and check out of the sale line itself.

- When a customer has more than 40 addresses and a user chooses the Lookup address... context menu entry (on an order's ship-to address, for example) the Search By in the Lookup window is initially City but now remains on the user's selection for the duration of a session.

- Fixed: Recent versions of FrontLine caused some versions of PostgreSQL to raise an error upon opening the System Users window in FrontLine Setup - Security.

- Added a Special Order column to the Generate Purchase Order window to show the source OrderID of special orders directly on the purchase suggestion list generated.

- Line items on Service Orders in FrontLine are now sorted similarly to the output of service orders from Forms for Orders: Line items unrelated to the repairs are first, then come the repair units, each followed by the lines attached to it. This sorting occurs when the order is opened, assigning a repair on the open order does not resort the view immediately.

- Fixed: Indicating a Retired GeoCode in Tax Detail did not save if the Description was blank.

- Ship Via is no longer required on Customer records, but is instead required on Customer Orders with a Ship-To address.

- Added a Rental Items Search By to Item Lookup to list all items in rental locations.

- Fixed: When an uninvoiced order's Ship-To address is changed to an address with no custom ShipVia, FrontLine now changes the order's ShipVia back to the customer's default ShipVia.

- Fixed: Tax Summary output from Forms for Orders did not summarize uninvoiced taxes by Tax Type.

- Fixed: Unquoting a line item would attempt auto-commit even when company setting Disable Auto-Commit was active. This bug was probably introduced in 6.4.085

- Fixed: Saving changes to entries in Setup Lists for many of the lists did not record the date of the change.

- Added a Company Setting Do not warn users when an address has no matching Tax Geocode in Notify Options that should only be used when Origin State Taxes apply to all locations. This option does not apply to Location Addresses, and all locations should be flagged Tax On Location GeoCode.

- Fixed: Tax Rates in Tax Detail setup only displayed up to 3 decimal places even with 4 decimal places on record.

- Fixed: The automatic Shipping Charge Calculator could add a negative shipping charge when a partially quoted open order was fully quoted.

- Fixed: Under some circumstances, the lists of Ship-To addresses in Equipment Sets did not build completely.

- Fixed: Receivable Statements run for a past date with open credits posted later using an invoiced date within the end date did not show the open credit.

- Fixed: Creating a new Equipment Set with a Bill Frequency shorter than Monthly using Company Setting Next Bill defaults to 1st of next period would set the Next Bill date to the first of this month, which is in the past and thus triggers a warning.

- Fixed: FrontLine could add new entries to a Voided Equipment Set behind the scene.

- Fixed: Searching with a blank Scan text for ANY identifier in Identify Unit could raise an SQL syntax error.

- Fixed: Access violation after the Warranty pop up from clicking the leftmost column of a warrantied repair unit line item when multiple warranties are in effect.

- Fixed: The Third Party group in the Welcome window now has its own security context below Purchase Orders in Access Profiles.

- Fixed: Miscellaneous Purchases generation did not exclude voided and fulfilled lines.

- Fixed: Purchasing auto-gen did not exclude Discontinued items with Minimum inventory levels.

- In Generate Purchase Order FrontLine now removes a package line suggestion from auto-gen when the package is a special order that brings no members with it.

- Added Remove Special Order to the line item context menu for packages on customer orders, to take all open members off special order.

- FrontLine now warns a user if an Item is Discontinued or placed On-Hold while it is on open line items.

- Added a Customer and Purchase Order Lookup Open w/Items Discontinued / On-Hold to find orders with open lines whose items are discontinued or on hold as seen in Items maintenance.

- Added an Order Lookup Rentals Short Term To Return to find short term rental orders that are completely fulfilled and checked out but still open to accept returns.

- Added a Receive Payment function next to the Exchange pre-scan toggle on the lower bar of the order processing window to receive a payment without typing into the line item Scan Code.

- Searching for an OrderID in the Receivables window using the Find function now searches for fully applied credits if there is no match in the receivable list.

- Exports from the custom Reports feature now recall export configuration per report.

- Added a Equipment Owner security context under Customer Orders. A user must have the Modify permit for this context to repair equipment sold to one customer in another customer's service order because doing so changes the equipment owner. Before FrontLine simply asked for confirmation.
To give users who have access to customer orders the same access to Equipment Owner without editing access profiles in FrontLine, execute this SQL:

- Added an AR.Invoiced field to the AR table to facilitate analysis. This change affects Receivables and Statements, customer order check-out, and recurring billing. A database update is required.

The Db Console contains a required update AR.Invoiced (6.4.094) to add a column to the AR table, and set its value from existing invoices. Note that the MSSQL version must be executed in two steps.

- Fixed: An SQL would occur upon activating the Group feature for a Parent customer in Receivables when using a MSSQL database.

- Added a Include Items Already Picking option to Forms for Orders. Previously, items already in picking (already printed on a pick ticket) were included by default.

- In custom Reports, a .rep form label named ReportParameters will now be set to a composition of the report's parameters specified at run time.

- Added two special searches to Scheduler Event Lookup: Incomplete Past Events and Unassigned Past Events. Both ignore background events.

- Added a View Today entry to the Scheduler board context menu to make it easier to return to a current date view.

- Added a special lookup Inventory Complete to Order Lookup for both customer and purchase orders. It lists orders with open tangible line items where all are committed to ordered quantity.

The Db Console contains a recommended update INDEX TRXINV.ItemID that is compatible with earlier FrontLine releases.

- Fixed: The Explode Quantities option in Forms for Orders had broken in a recent release.

- Added a Del Mail Creds function to the System Users window to facilitate removal of a user's mail relay credentials.

- Added a Return Next Scan option next to the Exchange pre-scan toggle on the lower bar of the order processing window. This pre-scan modifier can be turned on before scanning for a new line item to assume a return (if possible) where a sale or rental would otherwise have been assumed. This facilitates refunds of intangibles (services and charges) and returns of unidentified rental units. This option only appears when in the Returns, Repairs, Unidentified Company Setting Mixed Orders are selected, not Isolated Returns.

- When an unidentified unit of an item that usually carries a warranty when sold new is brought for repair, after prompting for identifiers, FrontLine now allows for entry of a unit warranty that takes effect immediately.

- Added a member agent Synchronize Change feature for when the Agent of an Equipment Set is changed and members have other agents assigned (from the agent assigned to the orders they originated from). The default option is to release the members to use the agent indicated in the Equipment Set itself.

- Fixed: Returns of lines with many individual units per line could cause an access violation.

- The Warranty information pop-up that appears from clicking the line number column of a covered repair unit line item now includes the Stock number of a Service Contract.

- Fixed: CheckNumber expansion in 6.4.086 broke some Drawer Reconciliation functions.

- Fixed: Identifier documents of units Committed for Rent could not be modified in Line Item Details.

- In Generate Purchase Order, the On Order quantity is now also broken down into On Order Regular and On Order Special.

- In custom Reports, a label named CompanyName will now be set to the value of Company Name from Company Settings.

- Setup Lists now has a Repair Code Classes list whose (up to 15) entries can be used to binary filter (by the new Classes column of the lists) Problem Codes, Solution Codes, and Peripherals shown in the Repair Codes window.
The Class and Classes values are in hexadecimal, number base 16.
If Class filters are used, and a Problem or Solution or Peripheral code should qualify for any Class filter, simply assign it a Classes value of 7FFF

- Sending an email from the Scheduler Event window now includes iCalendar (.ICS) data with the email composition.

- Customer, Vendor, and Location addresses can now be assigned their own Ship Via to override the main Ship Via when this address is selected for an order's ship-to. This revision requires an addition to the database, see below.

The Db Console contains a required update ADDRESSES.ShipVia (6.4.090).
The addition of this field does not break earlier versions of FrontLine.

- Added a context menu to the System Administrator link that appears on the Welcome window for administrator logins, with an entry to list Recent Orders Taken Over.

- Services and Charges flagged with the new Item Type Service Order (value 2048 or 0x800) are considered repair services (or charges) on an order even when unrelated to a repair unit. Their presence on an order also qualifies the order as a Service Order in order lookup.

- Batch Picking now has an Inventory Committed date option in addition to Order Placed and Order Scheduled, and an Export function.

- Projected Period Details for a Reservation now show rented quantites with an undefined return date with a question mark instead of assuming a default return date.

- Changing or adding only the +4 part of an address Zip code no longer triggers a search of GeoCodes for City and State.

- Scheduler Events can now recur on a random selection of days.
The Recurs selector in the Scheduler Event window now has a Specify Days option that provides a year calendar where one can click days while holding down the Ctrl key to select multiple recurrences.

- Added individual AgentPhone1, AgentPhone2, and AgentPhone3 to outputs from Forms for Orders in addition to the existing AgentPhone which contains the first non-blank phone number of the three.

- Fixed: The company Cost Option Use Special Cost for Commissions, when available alone caused purchasing check-in to skip cost accumulators even when the Cost Special Order sales by special Purchase Cost option was off. This fix is in the database procedure CostInvoice, and must be applied to each database.

- Expanded Company Setting "Scan Auto Lookup" into Lookup Options, with the addition of a "Include Separate fields with Search By Combinations*" option to enable searching by the individual fields merged into Name*, Address*, Phone*, and Description* in the Search By selector.

- Added a Show Contract Units option to Forms for Orders. This option applies to service contract line items: When on, units covered under the contract are output to the contract line item as if they were units committed to that contract line item.

- Removed the Alt letter key shortcuts in Tax Detail maintenance and improved Tab key navigation.

The Db Console contains an update File: CostInvoice v6.4.087 required for the fix above. This update is compatible with earlier versions of FrontLine.

- Fixed: Sorting of events in the Unit Tracker could show recurring bills before the rental event.

- Fixed: Manually entered purchase order line items now default to the vendor-specific last cost.

- Fixed: Opening Customers maintenance without access to Other Agent's Customers could raise an access violation loading a customer template.

- Fixed: The equipment identification recovery for unquoting introduced in 6.4.085 does not apply to voids.

- Fixed: FrontLine included provisioning contracts in the opportunity to add equipment coverage in the Service Contracts window for unidentified units brought in for repair.

- Fixed: For order tenders, it is now possible to enter check numbers up to 15 digits long. Part of this change is in the database, see CheckNumber expansion below.

- Fixed: Having read-only access to customer orders caused problems processing purchase orders.

- The ReceivableComment output to Receivable Statements forms now includes the DocType text for Finance Charge if the receivable comment text is blank and the document type is a finance charge.

- Repair Units entered directly on a Quote using an identifier are now recorded like those entered on a Service Order that is then turned into a Quote.

- Added a Reservation feature for rentals. Rental line items are reserved starting at the (existing) Scheduled date for a (new field stored as minutes in the db) Reservation time span. Both are visible and can be edited in the Line Item Details window. There is also a Reservation function available by context menu or the shortcut Ctrl-' that opens a Reservation window where one can select a Period of days to view Projected Quantities in a selectable rental location. The Projected Quantities list shows reserved quantities, expected returns based on reservation time spans, and shortages to fulfill the desired quantity (if any). A single range of days can be selected for the reservation, reflecting the line item's Scheduled and Reservation values. The Projected Period Details on the right shows projected outgoing and incoming rental order line items for the day selected in Projected Quantities to the left. There are some requirements and consequences of these revisions:

In Company Setting Equipment Sets, Rentals, Contract Options there is a new option Orders Seek Equipment Sets with Own Lines in contrast with the prior default where New Orders may Share Equipment Sets. Enabling the new option makes FrontLine find an Equipment Set suitable for the new member that also has existing members from the same order. If not, a new suitable set is created. If a user does not move members manually, this option effectively creates a new ESet for every order. It could also create more than one ESet for one order, for example if the order adds both billing and non-billing members.

The Db Console contains three updates to be applied in this order:
Rental Reservations 6.4.086
File: CommitInvoice v6.4.086
CheckNumber expansion 6.4.086 (this data type change breaks earlier versions of FrontLine)

- Fixed: FrontLine allowed a depot repair unit line item to be quoted after the unit had been sent to depot.

- Fixed: Returning a payment that included a write-off did not break down the two receivables correctly.

- Fixed: It was possible to lookup and commit inventory to lines on a voided customer order.

- Fixed: Unfulfilled Transfers marked as Special order could create purchasing demands.

- Clicking the warranty icon on a line item now offers to show the unit warranty record.

- Upon unquoting, either an open quote or creating a new order from a presented quote, FrontLine now attempts to recommit repair units that were assigned to a repair unit line item then turned into a quote.
If the repair unit was previously unknown (unidentified), then when the line is turned into a quote the unit is kept on record as a "Sold, To Repair" event unrelated to an order.
Upon detaching the event from the quote, the identifier document key is assigned to the line item's UI so it can be found again without re-entering identification.
Quoted repair parts and services can now be assigned to quoted repair unit lines.
For recommit to work on an open quote, the Company Setting Disable Auto-Commit in Line Unit Identify Options must be turned off.
For recommit to work on a presented quote that is turned into an order, the Company Setting Auto-Commit Order created from Presented Quote in Quote Options must be turned on.
For service quotes, or orders that contain quoted repair service line items, there is a new Service Quote available for printing in Forms for Orders. Service Quote forms follow the same scheme as Service Order forms.

- Fixed: Transaction Inquiry did not always list problem/peripheral/solution codes.

- Added Auto-Commit Order created from Presented Quote to Company Setting Quote Options.
Note that this setting does not override the global option to Disable Auto-Commit in Company Setting Line Unit Identify Options.

- Fixed: Late Fees Billing could omit some customers with overdue receivables. One omission was customers with a non-blank Statement Category.

- The Unit Warranty window now displays and accepts input for both Vendor Number and Vendor Name.

- Fixed: Changing a package member Group ID in Package maintenance could cause a stack overflow.

- Fixed: Solution and Peripheral codes did not translate on Inquiries and Reports.

- Fixed: Adding an address for a customer while having an open order of theirs on display would add it to the order's Ship-To selection list with a name and address text.

- Added Shipping Charge Calculators to Setup -- Lists. Together with an assignment of Company Setting Shipping Charge ID, shipping charge calculators enable automatic assignment of freight charges to orders and quotes based on order totals and specific vendor item totals, using fixed values or percentages, cumulative (added) or replaced.
Note that these shipping charge calculators are not related to shipping events where actual shipping charges can be determined and a percentage added to the order.
A sequence of rules are assigned to ShipVia codes. The columns to set up Shipping Charge Calculators are:

The Db Console contains entry CALCRULES (6.4.082) to create a new table.
Note that FrontLine 6.4.082 will not function without this new table.
Log in as system administrator and proceed directly to the Db Console to add it.

- When a unit that was sold in a package is returned by scan code, and brings in the entire package for return, package members can now be voided individually.

- Increased the size of the Mail Relay field for Locations from 40 to 80 characters. This revision requires a database update.

The Db Console contains a required entry Expand Location Mail Relay (6.4.081) to implement part of the last revision above.

- Fixed: Vendor RA orders were missing the Bill-To if the Location had no Sold-To assigned.

- Fixed: A recent revision broke opening prior invoices from the yellow list in the Check Out/In window.

- Fixed: A recent revision added a bogus number to the default subject line of email for forms.

- Fixed: A potential access violation printing a Vendor RA from Forms for Orders.

- Fixed: If a custom payment tender type is indicated before a tender account number is entered that doesn't fit a standard tender type profile, non-numeric characters are retained.

- Vendor RA output from Forms for Orders will now output all line items for a completed V-RA.

- Fixed: Identifiers for package member line items did not appear using the Details option in Transaction Inquiry.

- Added an Invoiced column to the Applied list in the Receivables window, and a non-sticky sizer to increase vertical space for the Applied section.

- Forms for Orders now outputs a single AgentName field instead of AgentName1 and AgentName2 for the order agent.
AgentName contains Name1, or Name2 if Name1 is blank. Forms that use the old field names will need a simple revision.
Added fields AgentPhone and AgentEMail for the order agent.

- A user who has Modify access to recurring billing can now change the Customer PO values in Recurring Billing Output.

- A plain click on the System Administrator link in the Welcome window now shows a simple list of FrontLine Licenses In Use.

- Fixed: Bill Of Materials components were prorated as if they were package members instead of indepent line items when initially added to an order.

- Fixed: FrontLine did not log the creation of a Depot return line item, resulting in an incomplete Line Item Change Log for depot return lines.

- Fixed: Recurring Bills Items that were members of a non-billing package were correctly placed in a non-billing equipment set, but should not be prorated.

- Fixed: Package members sold in Package First mode where the package had a non-zero price were correctly priced at zero, but failed to generate $0 tax details.

- Fixed: For a Payment line item, FrontLine now assigns the revenue account from the receivable itself (if there is one) and the location from the order where the receivable was incurred (if the order is on record, otherwise the current order location is used as before).

- Added a Other Agent's Customers security context in the Customers class. A value of None or NULL will:

- Fixed: Changing multiple of Print Template Folder, Report Folder, and SD Folder in Locations maintenance then saving could raise a key violation in the log table due to a shared security context. There are now separate security contexts for these two folder fields that were introduced in 6.4.070

- Fixed: A recent revision broke the use of Bill[...]Credit.rep form names for Recurring Bill credits.

- Fixed: Pick Ticket and Vendor RA output from Forms for Orders should only include open line items.
This bug was probably introduced in 6.4.069

- Fixed: It was possible for standard tender types to be listed twice in the drop-down of an order's payment tenders.

- Fixed: The Sales Orders for Invoicing Order Lookup included Ready orders that had been completed.

- Fixed: Miscellaneous line items on a customer order are costed at check-out (in TRXINVCOST) using this order of preference:

- Changed the Zoom function in Equipment Sets to a drop-down list of View options that are stick and initially all on by default:

The Db Console contains an entry File: CostInvoice v6.4.073 to implement the miscellaneous costing fix in this release.

- Fixed: Sending an email without an attachment would raise an SQL error after sending upon logging the transmission.

- Fixed: Printing from Forms for Orders then changing a bill/ship-to address and reprinting would output the old address.

- Added a Bill History context menu function to the Db Console that appears when the results have an ESetID column. It opens Order Lookup to show recurring bills for the equipment set in context, with most recent at the top.

- Added an optional Stock column to the Import Customer Equipment feature. A default stock number must still be selected before the import because it serves not only as a default item (a stock number is not required in the import file) but also as a model for the identifier documents to import for other stock numbers specified in the import file.

- Late Fee Billing now has context features in the Batch Review stage to view only exceptions, and exclude individual customers from the batch.

- Added Report Folder and SD Folder to go along with the existing Template Folder per Location. These allow for more specific folder contents. The new folders are optional, if left blank FrontLine will continue to use the templates folder as before.

The Db Console contains entry Location Folders (6.4.070) to add two columns to the LOCATIONS table.
Note that FrontLine 6.4.070 will not function without these new columns.
Log in as system administrator and proceed directly to the Db Console to add them.

- Fixed: Purchase Order Lookup by Scheduled date raised an ambiguous column name error.

- Fixed: A revision after 6.4.065 introduced missing line items from printing Sales Order output customized for Red Deer.

- Fixed: It was not possible to check in (out) specific line items on a Vendor RA using the line checkboxes, all lines were checked through.

- The Order Totals window now summarizes in rows, by basic Item Type (Inventory, Service, Charge) and overall totals (Quotes separate).

- Added a Company Setting Order Status Hold Purchasing to indicate Custom Order Status flags on a customer order that should exclude that order from purchasing suggestions in autogen.

- Fixed: A new assembly assembled on a work order can now be cancelled before it is checked in.

- Added a Font Size 14 (found in Current Station setup) for small high resolution screens such as the Surface.

- It is now possible to select a specific receivables Account when producing Receivable Statements for a single customer. This enables the use of an account-specific form for single customer output, and will output only the customer's receivables marked for that account.

- Recurring Billing Output produces Late Fees forms output using a form named LateFees.rep (plural because a late fee bill can have multiple late fees on it) and includes a new field ReceivableOrderID to identify the order that created the receivable that is overdue.

- Added a No Late Fees option for customers to indicate that this customer will not pay late fees, so exclude them from late fee billing.

- Added a Late Fees Setup to the Company Settings, where the late fee charge item is indicated along with optional Grace Period and Minimum Charge entries.

- Added a Late Fees Billing feature to the Accounts Receivable group. Late fee bills are created in a similar sequence of steps to recurring bills. The late fee bills created are similar to recurring bills, except that they have only late fee line items:

The Db Console contains entry Late Fees (6.4.067) to add two columns to the AR table required for late fee billing.

- Fixed: When a package member was returned without the rest of the package, the return line item now has its package references cleared so it can be manipulated independently. A similar situation occurs with repair parts.

- Fixed: A recent revision resulted in an SQL error about P.Account in Receivable Statements when an Account was specified in the Criteria section.

- Fixed: Scrolling lookup results with a mouse wheel only worked on the visible rows.

- The Serviced function on the top bar of the order processing window reverts to Complete on service order returns.

- Added a Parent indicator for Customers. Customers under a parent are considered members of the parent group for payment purposes, and can have their receivables paid for by the parent. There is a new security context to control access to the customer Parent field.
The Receivables window now has a Group function to show receivables of all members of the group, and apply parent payments to members. When applying a payment with all members of the group displayed, a payment from the parent customer or non-payment credits from a member can be applied to any member, but a payment from one member can only be applied to receivables of that member.
Member (child) receivables are indicated by a head icon in the Customer Number column that appears at the far right of the row.
Parent payments shown in the Applied list are indicated by a hand and pencil icon on the far right.

The Db Console contains entry CUSTOMERS.Parent (6.4.066) to add a required column.

- Fixed: The Summary feature in Receivable Statements excluded customers that did not accept statements. Those customers should be included in the summary but excluded from the statement output. And the ...Now outputs have been renamed ...All to reflect that they include receivables that could be posted with future dates.

- In Receivables there is now an Applied... feature that lists payments applied to the selected receivable in a grid below, with functions to view the orders, etc.

- Fixed: 6.4.059 introduced an SQL error exporting the Tax Report using By Location.

- Fixed: Email records introduced with the email address helper would, after sending the email, raise an SQL error on MSSQL when single quotes were used in the email subject.

- Clicking a column header in Recurring Billing Output now sorts the list, and print output attempts to mirror this sorting. Default sorting is restored whenever a batch is retrieved.

- Added a sticky option Exclude Cash Invoices to Periodic Invoices. This option affects the Periodic Invoices output but not the batch inclusion, so it can be toggled on an existing batch.

- Added an indicator for the location Mail Relay to initiate TLS encryption before the SMTP greeting process, instead of waiting to find STARTTLS in the response to the EHLO greeting.
Add a ~ to the end of the mail relay property to turn on this "TLS Wrapper" (SMTPS) mode.
When sending via a Google account, Google says use port 465, or port 587 if the client begins with plain text before issuing the STARTTLS command.
For example smtp.gmail.com:465~ vs smtp.gmail.com:587

- Added a Customer function to Vendors maintenance that offers to create a corresponding customer for dual role entities, or opens the existing corresponding customer. This customer and vendor share the same ID and address list because they are the same entity, but the customer needs to have default addresses (like bill-to and ship-to) assigned by a user, and any customer-specific information needed.

- A Unit Warranty can now be assigned a Vendor who pays for warranty repair services performed in house.

- Repair services performed under warranty at no charge to the customer can now be invoiced to the warranty vendor indicated in the repair unit warranty or the repair item default vendor. A receivable is posted for this vendor. The conditions to produce a warranty vendor invoice are:

The Db Console contains four entries. These updates make a database incompatible with checkout in older versions of FrontLine:
File: Warranty Service Claims v6.4.064
File: NewInvoice v6.4.064
File: CommitInvoice v6.4.064
File: CostInvoice v6.4.064
to implement parts of the warranty vendor invoicing revision.

- Fixed: Sorting of members of packages used for repairs on output of Forms for Orders.

- Fixed: Erasing an identifier value on a committed unit in Line Item Details did not save.

- Fixed: Overriding the price on a package return would recalculate taxes with the wrong sign.

- Data entry enhancements to Parts Cross-Reference, which now has Entity name instead of ID. An Entity ID can still be entered in this name field.

- Added a Disable Auto-Commit option to Company Setting Line Unit Identify Options to disable auto-commit altogether.

- Fixed: The Show Credits posted after End Date option for Receivable Statements did not work on applied credits.
Note that the AR.BalanceEnd or AR.BalanceNow form expression should now be replaced by AR.Balance because the balance shown is determined by the option Show Credits posted after End Date.

- Fixed: 6.4.060 broke the output sorting of Service Orders from Forms for Orders.

- Added a Do not verify Item Category Accounts until check through option to the Company Setting Discount Presentation, Qty Repricing, Cost Base, Line Accounts to defer verification of line item accounts.

- Added a pop up notice about lack of automatic repricing when the entity is changed on an order with line items.

- Added a Summary (Print or Export) feature to Receivable Statements that outputs a summary for internal use.
Print requires forms named ReceivableStatementSums.rep and uses Different forms when Account specified, and output is affected by the Show Credits after End Date option.

- Fixed: Recurring Billing could raise an SQL error when listing Exceptions and Batch Review.

- Fixed: Members of packages used as repair parts were not sorted with the package in the Service Order output of Forms for Orders.

- Added an All function to the Recipients section of the Scheduler Event window. Note that the primary participant should be selected first.

- The Tax Report now excludes lines where both the Tax Amount and line Effective amount are zero.

- An interactive email from Receivable Statements output for one customer will now use the same recipient email address that the batch process uses: The E-Mail address directly on the BillTo address.

- If there is a floating Scheduler window concurrent with order processing, then when Forms for Orders opens the Scheduler window is hidden, then shown again upon return to the order window.

- FrontLine has begun logging user field value changes on order headers.
The Db Console now transates the ObjectID field of the log tables MNTLOG* to meaningful text, and can open the Item/Entity/Order in context of the log record.
Note that FrontLine has been logging whenever an order was opened by a user for possible changes, but the logging context always indicated a customer order.
To fix the log to indicate purchase orders, execute this SQL:

- Fixed: The signature printing revision in 6.4.056 broke output of graphics by file name.

- Elaborated the Company Setting for Discounts, Repricing, Cost, LA (Line Accounts) to add options for Location for Item Category Accounts - Revenue and Cost of Sales Line Location (default) vs Order Location. When set to Order Location and the order location differs from the line location, the Revenue (Income) and Cost of Sales accounts are taken from the order location.

- Tablet PC signatures can now output to Forms for Orders, and both signature types now appear in PDF files output.

- In Recurring Billing, FrontLine now refuses to continue with bill creation after Exceptions and Batch Review if there are critical exceptions outstanding.

- Customer Returns of non-rental items now apply the line item's C.Cost (if entered by the user) to inventory costing: Layers, and Location Average Cost.
The return invoice cost method indicates Trade-In
This allows a return unit to be devalued for inventory based on wear.
This revision is implemented in the CostInvoice database procedure.

The Db Console contains entry File: CostInvoice v6.4.056 required for the custom return costing.

- Fixed: FrontLine should not change the warranty coverage on a repair part based on the part unit selected. This bug was probably introduced in 6.4.013

- Fixed: The All function in the Service Contracts window would show contracts that belong to other customers.

- Fixed: In the Service Contracts window, adding an equipment unit to a contract, removing it from the contract, then adding it back to the same contract within the same session did not save the coverage.

- Fixed: Alpha characters entered in account numbers of custom tender types were discarded. The follow up the revision in 6.4.051

- Fixed: Added an AR_=Accounts Receivable Report Group and fixed the report group guess for when an AR report file is manually added to the list.

- Receivables now shows Due and Invoiced dates, and the Unapply function entries show their Order ID.

- Receivables now has a Convert Type context menu function that appears for negative amounts to change the DocType and make the Amount positive.

- Recurring Billing now checks for Unearned Revenue disparity on Item Category Accounts and indicates them in red in the Exceptions and Batch Review step. This exception means that some but not all line items on the bill have the Unearned Revenue Account defined for their Item Category.

- FrontLine can now accept a digitizer pen Signature on a Tablet PC such as a Microsoft Surface Pro. These signatures cannot print on forms yet.

- Fixed: Adding a service contract to a customer order then opening the contract details while another user concurrently processes an order for the same customer could raise an SQL key violation on PK_ESDTL.

- It is now possible to assign a presented quote to a job. The Job entry in the main orders window is now under the Quote menu.

- The Item Quantities window now shows On Hand and Open PO (PO'd - Received) quantity per location.

- Added a Notify user when Line Quantity is increased over Committed Quantity option to Company Setting Line Unit Identify Options to notify a user when they increase line quantity over previously fulfilled quantity for an item that cannot be auto-committed.

- Added a User Agent priority on new orders option to User Options. This option gives the user's agent (if assigned) precedence over the customer's agent when a customer is assigned to an order.

- Order and PO Lookup now display the search identifier matched in the column that otherwise shows Order Ext Ref when non-identifier searches are performed.

- Fixed: Multiple concurrent users attempting to view Job Details could raise an SQL error about PK_JCS.

- Added a Job List Criteria feature to Jobs. Click the job list section heading or use shortcut Ctrl-F1 to open it.

- Creating a job order from a presented job quote now creates Resource Costs Job Budget numbers even if the quote didn't have explicit budget values:

- Fixed: Under some circumstances, printing an open service order could raise all flags on that order status.

- Fixed: Line items at rental locations on POs, Adjustments, RAs, and Transfers should not be marked with the Rent transaction type indicator.

- Fixed: Changing a user's Role in System Users for a long user name in a MSSQL database raised an SQL error.

- Fixed: Changing flags for multiple entity addresses then saving would raise a key violation on PK_MNTLOGI.

- Fixed: Returning an open Payment (where no receivable was specified) did not apply the negative to the payment in AR, so while the account balance was correct both entries appeared and could not be applied manually.

- The Scan Code display on open orders where the line was created from an identifier is now Identifier » Stock instead of only the Identifier.

- For custom tender types, an Account Number of any format can now be input, and the numbers are not obscured like card numbers.

- To help a user resume working on their last order after a connection loss to the database server, FrontLine now saves the recently opened orders list right after opening an order for editing instead of waiting for logoff.

- Enhancements to Job Cost including a Details feature to provide summaries and context links to customer orders, POs, etc.

The Db Console contains three entries:
TRXTAX[IP].Account
File: GetTaxes v6.4.051
File: CommitInvoice v6.4.051
to implement parts of the Tax Account revision.

- Fixed: Returns of a rental repair service order resulted in the rental repair unit returning to stock. It now goes back to being rented.

- Fixed: When the E.Set identifier document template was undefined, using the S.Find function in Equipment Sets raised an access violation.

- Spaced embedded in the middle of field names output on reports are now ignored better for code translation purposes. For example, and of these will now match OrderStatus: "Order Status", "order status", "ord ers tatus" but leading and trailing spaces will still cause a mismatch such as "Order Status " (this can be used to deliberately avoid a translator).

- Added a Repricing after Location change section to Company Setting Discount Presentation, Quantity Repricing, Cost Pricing to disable repricing a line item after changing line location.

- Resource Costs now has a Budget section for Job line items, and next and prior buttons to scroll through line items on the order without having to close and reopen.

The Db Console contains an entry File: Job Cost Data (6.4.050) to add Job Cost tables and fields required.

- Fixed: Upon creating a Vendor RA by scanning an identifier of a unit in stock, the Ship-To address was assigned but not displayed until the order was deferred and reopened.

- Typing into a Bill-To field on an order to lookup an alternate billing address (from any customer) now only lists addresses that include the Bill To attribute.

- The By Date option in Transaction Inquiry now lists the most recent orders first instead of last.

- Fixes and minor revisions to the email address helper in the E-Mail composition window.

- Fixed: Could not commit inventory to a special order line item with no identifiers from Scan Match invoked from Line Item Details.

- Fixed: Voiding an open package line item could void its completed member items.

- Added an email address helper to the E-Mail composition window. Currently it is limited to email sent in the context of an order. It lists all email addresses related to the order and order entity, with the order contacts first and preselected. Checking an email address adds it to the last selected (and indicated by a bold label) recipient list: To, or CC, or BCC. Unchecking an address removes it from wherever it appears in the recipient fields. Typing into a recipient field seeks a match which is highlighted in yellow, and pressing Enter selects that recipient without further typing. If no email addresses are found, the blank list is hidden. There is a proportioning splitter to adjust space usage in the header section of the window.

- Fixed: The contract coverage umbrella in Customer Lookup appeared even if all contracts were cancelled or terminated.

- Fixed: Order line items sold and checked out at $0, then returned and manually repriced at non-zero would result in missing taxes on the return. This was due to the all-zero tax details being discarded upon completion of sale check-out. The fix is in the CommitInvoice database procedure, and must be applied in the Db Console.

- Open Transfer requests are no longer added to the Allocated quantities in auto-gen, and thus do not trigger purchase suggestions.

- Restored the Include Discontinued Items option in Physical Count with a workaround for the PostgreSQL problem it triggered before.

- Added a Tenders field output to Receivable Statements that lists the payment tenders on the payment order where a payment was received. Use this expression in the Detail section of the receivable statements form, and set the section to both Auto Expand and Auto Contract.

- Setup Lists now provides a Delete button for all lists, however it is only enabled when applicable.

- Added a LineLocation field to the outputs of Forms for Orders. LocationID (Order Location) and Line Location output are now distinct.

-When the Quote function is used on a closed order that contains both quote and non-quote line items, FrontLine now displays a selector for Order from Quote lines vs Quote from All lines.

The Db Console contains a procedure update entry File: CommitInvoice v6.4.047 required for the return tax fix above.

- Fixed: Inventory RAs should always ship from the inventory location regardless of the order location, and depot repair returns should go back to that inventory source location.

- Fixed: The doubling of quotes for Export of text fields failed on trailing quotes.

- The last custom order note context (if used) is now also a follow-up conversation note, like receivable notes. This note is not available for output to Forms for Orders.

- Fixed: Reappearance of the Item Quantities window introduced in 6.4.044 is now stacked correctly just beneath the Items maintenance window.

- Fixed: Periodic Invoice for regular invoice lines that have multiple units assigned could inflate the line Quantity output to the form.

- Fixed: 6.4.044 introduced a bug where a $0 check-out with no tenders could not be completed.

- Added a Collected function to the context menu of customer order payments to process a cash/check/card tender ahead of invoicing.

- In Items maintenance, added an ability to change the width of the Item Information section by grabbing a sizer between it and the right window sections. If the result cuts off the check boxes on the right then the window is widened to accommodate. The result is sticky per user, within reasonable limits.

- When a floating Item Quantities window is opened from Items maintenance, then Items maintenance closed and reopened, Item Quantities reappears when an item record is opened.

- Added a Separate Returns option to Item Quantities. With this option off, return quantities are merged into available. Previous releases always separated returns.

- Fixed: Changing a line location from a location where there is an applicable price level to a location with no applicable price level did not reset the line price to list price.

- Fixed: Setting the line price of a miscellaneous item to zero right after creating the line raised a Quantity Tracker error.

- Fixed: Changing the quantity of an Adjust Out line item that could be auto-committed resulted in the commits becoming available instead of adjusted.

- Elaborated the Company Setting for Line Unit Identify to add options for Only Items with Identifiers vs Any Stock Item.
This makes the revision for Seek Id made in 6.4.040 optional.

- Fixed: Receivable Statements used the application date of fragmented payment applications instead of the payment date.

- Fixed: Intangibles (Services and Charges) with a default vendor on file were not included in purchasing auto-gen unless they were special ordered.

- Fixed: Adding purchase order line items to an existing PO from auto-gen with demand notes could cause a key violation.

- Vendor RA is now a separate form in Forms for Orders, with data output like a Pick Ticket.

- Added an item-specific Last Lead value (in days) to the Vendor Performance of the Generate Purchase Order function. Last Lead is the numbers of days between the PO placed date and the item receive date, however it is not evaluated here until the PO line item is checked in and final cost recorded.

- Returning an item using Scan Code or Customer Equipment that has been repaired since the sale now returns the equipment alone for $0. Override the return price to provide a refund.

- Purchase Order output from Forms for Orders is now like a Pick Ticket so identifiers can be included. Some expressions have changed, such as Quantity to LineQuantity.

- The Scan Code field in Line Item Details now works to commit inventory to a line item of a Transfer Order.

- The Telus third party links in the Welcome window now invoke .pyw programs instead of .py programs.

- Recurring Billing Output now sorts output of multiple bills by Bill-To name first, then the first Equipment Set Identifier (if selected), then OrderID.

- When viewing Customer Equipment in the Scan Match window, there are now two options to "Include Equipment with no ID" and "Include Out Of Service". Previously, these were always included.

- Receivable Statements output with an End Date now have a sticky option to Show Credits after End Date. Prior releases always showed such credits and payments, and the output field PaymentPosted is now PaymentDate to reflect when the payment was received rather than when it was posted to a receivable.

- FrontLine now logs basic information about emails sent, such as recipients, subject, and OrderID. Multiple Recipient EMail of reports are not logged.

- Added an eSignature feature for email composition. Set user E-Signatures in User Options. The signature text is added to .eml templates using <FLF>eSignature</FLF>. FrontLine converts signature line breaks to <br> if the email has HTML formatting. If there is no .eml template then the eSignature becomes the default email body.

The Db Console contains entries Widen UIPRESETS and UILISTS and EMail features 6.4.042 to make required changes.
Note that FrontLine 6.4.042 will not function without the EMail features db update.
Log in as system administrator and proceed directly to the Db Console to apply them.

- Fixed: Again, an item with no event history could not be adjusted in with Company Setting Line Unit Identify set to Seek Id.

- To complement the equipment set identifier documents introduced in 6.4.025 two Equipment Set Identifiers can now be output to forms from Recurring Billing Output as SUIValue1 and SUIValue2.

- The [Stock] field text output from Forms for Orders for Payments On Account now includes a reference to the order being paid for, like shown in the payment order Scan Code.

- FrontLine now uses an order's Customer PO as the default Comments on AR records it posts for this order.

- Fixed: Returning a package using a member identifier as scan code did not link the member line items on the return to the package return, causing check out problems. This bug only affected MSSQL dbs and is fixed in the CopyLineItems db procedure.

- Fixed: Applying a credit towards Receivables might not be committed correctly.

- Fixed: Choosing BackOrder or Special Order from Scan Match for a customer order now assumes a Sale, so no Item Action is raised.

- Company Setting Line Unit Identify set to Seek Id now only applies to items with identifiers.

- When Scan Match shows customer units of an item for repair when the unit wasn't previously identified, the "Scan Matches" and "Available Inventory" tabs are not shown.

- Added a Miscellaneous Text feature to Receivable Statements. Activating this option displays a type-in box for miscellaneous text that will appear on the output if a form has a label named MiscellaneousText. Although the option is sticky, the miscellaneous text entered is not saved.

- Added to Company Setting On Account Tenders & AR an option to Print Sales and Service Orders without Tendering. When this option is not set and a customer has no credit, an explanation now appears before printing.

The Db Console contains an entry File: CopyLineItems 6.4.040 for the first fix above.

- Fixed: Opening Transaction Inquiry from Items maintenance, then reopening it from the Inquiry group in the Welcome window, then clearing the Stock number criteria might not clear the criteria internally.

- The [EntityOrder] output field from Periodic Invoices has moved from the INVSUM dataset to INVOICE for better correspondence.

- Added output fields INVOICE.OrderNote and INVOICE.LineNote to Periodic Invoices.

- The [InvDate] output field from Receivable Statements now contains the receivable's Posted date if there is no corresponding Invoice.

- No customer Forms for Orders can be printed without sufficient credit, a credit override, or cash tenders on the customer order. Previously, the sales order form could be printed.

- Fixed: Inventory units with status Defective, In Use, In Shop, or Out Of Service can now be adjusted out.

- Fixed: If none of the the Unit Id (1,2,3) were selected, opening a Periodic Invoice batch could raise a missing SQL error.

- Added these sticky option to Periodic Invoices, accessible in a context menu of the Open button. A batch does not have to be regenerated to change them:

- Added fields [Quantity] and [Description] to the output dataset INVOICE in Periodic Invoices.

- Added display of cost based calculations in Price Levels: Cost based Price Level calculations shown within the Items maintenancce window all use the base standard cost seen directly on the Item record, while cost based calculations shown in the Price Levels window are location-specific using the Display price calculated from Cost at Location selector. A price level Price display that was calculated using the base standard cost (not location-specific) is indicated by a trailing asterisk.

- Added a User Option User can only use the Scheduler. Such a user can use the scheduler board, manipulate scheduler events, and view orders related to events. Such a user does not consume a FrontLine user license upon login, and is taken to the scheduler board directly.

- Fixed: A recent revision caused the Item Action prompt to appear twice during line item entry under some circumstances.

- Receivable Statements now have a sticky option to use Different forms when Account specified. There are now two possible variables in the form file name, determined by Statement Category and Account in the Criteria section:

- Fixed: Taxes on Quotes had the wrong sign. This bug was introduced in a recent tax sign fix.

- Fixed: When an Item's Minimum Price was left blank, FrontLine assumed it was zero thus not allowing negative price overrides.

- Fixed: FrontLine had assumed that the default Due date of a receivable would be calculated when needed using the Terms of the receivable. Instead, it now assigns Due dates to AR posted from Invoices (reference date is the invoice date [Created]) and Recurring Bills (reference date is the bill period begin date [Scheduled]). Receivables are made Due on the reference date plus the number of days in the Terms, while Credits are made Due on the reference date itself.

- Fixed: Assigning multiple Participants to an unassigned event in the Scheduler Event window would save them all as the primary participant. The first assigned when the participant list is empty is designated primary.

- Fixed: Recurring Scheduler Events assigned to multiple Participants were not consolidated in multi-day views.

- Fixed: A revision in 6.4.034 made the Item Action prompt appear for services and charges.

- Added Microsoft-specific locking hints to AR functions to prevent MSSQL Server from using table locks and thus potential deadlocks between FrontLine clients during customer order credit check and posting AR after check out.

- Fixed: Credits and Payments in Receivables that had been Adjusted out appeared to be open.

- The [Account] and [Comments] columns in Receivables now widen at the expense of [InvSeq] and [Line] when the cursor enters them to improve reading space.

- Fixed: The shortcut to sales auto-commit with Company Setting Line Unit Identify Seek Id introduced in 6.4.028 made some transaction types impossible to achieve, such as inventory Adjust Out and Returns of non-identifiable items from a Scan Code.

- Fixed: Application of an open payment to multiple Receivables in one pass created the wrong DocType on the application records.

- Return orders can now be turned into quotes. However, such a quote cannot be unquoted.

- Fixed: When a voided order was opened, then unvoided, it was not marked as In Use. Consequently, another user could open the same order and modify it at the same time. The In Use warning prompt has also been enhanced with the name of the last user who opened the order.

- The Received Inventory Check In prompt upon deferring an open PO is no longer displayed for RAs.

- Fixed: The Add Event function on the Scheduler board is now disabled for users without the Add permit for the Scheduler context.

- Added a Discountable property to Item Categories in Setup - Lists.
Items in discountable categories can have a customer's overall Discount percentage applied.

- Tax Exempt Vendor RAs are free of the return order constraint that does not allow the Ship-To address to be changed.

- Added the primary participant (Agent) to Scheduler Event Lookup and enhanced display text of the Event Status.

- Miscellaneous items now raise the Item Action prompt when added to a customer order, even when they have no identifiers.

- Fixed: The file names for Telus third party links were not revised correctly in 6.4.028

- Fixed: Receivables posted by Recurring Billing were not assigned the location's AR Account.

- Fixed: Scheduler Event Status dynamic visual layout in the event window had bugs.

- Added an optional Account criteria to Receivable Statements. Selecting an account here retrieves only receivables (and payments if unapplied) assigned this account. The drop-down list shows only accounts selected for AR at any location, but other accounts can be typed in.

- Added a Include Zero Price Line Items sticky option to Periodic Invoices, accessible in a context menu of the Open button. A batch does not have to be regenerated to change this option.

- Fixed: Signatures output to Forms for Orders would repeat the first signature instead of drawing the unique signatures.

- Stock selection on a customer order from Item Lookup is now consistent with the 4th revision in the last release about Line Unit Identify.

- Fixed: A collation error upon opening Tender Types from Company Settings when the Microsoft SQL Server default collation differs from the collation used in the FrontLine database.

- Added No Form Selection to User Options, separating form selection lock down from Fixed Print Options lock down.

- Added a Periodic Invoice filter to Receivables. This filter only appears if periodic invoicing is enabled by presence of the PVIDS table. When a periodic invoice is selected, the total of the receivables listed is shown.

- Upon entering a new non-identifiable line item using company setting Line Unit Identify Seek Id the Scan Match window does not prompt the user to identify the inventory. Consequently, auto-commit can be attempted for inventory at the selected location.

- On the Scheduler board, an Agent with no Category now qualifies for any Resource Category. Note that the uncategorized agent is still subject to Resource Certifications selected (if any).

- The Print options for the Scheduler have been moved from the context menu to the board options panel, and a By Agent option has been added that sorts the output primarily by Agent.

- There can now be up to 15 Event Status choices for Scheduler Events (see Setup - Lists: Scheduled Event Status) with the first eight mutually exclusive and colored (see company setting: Scheduler Options), and the last seven optional. Except for the first two (Open and Completed), the rest are omitted from the event window if their list display text is blank. The status checkboxes are now arranged more dynamically in three columns to fit the display area.

- Package First sales with a positive package price now consult price levels and customer discounts.

- Periodic Invoices now has an option to only include Service Orders in a batch.

- Revised the third party entries for Telus in the Welcome window (see 6.3.003 for original implementation notes) as follows:

The Db Console contains an entry Minumum Price (6.4.028) to add columns required for the minimum price revision.

- Fixed: A rental exchange should not be prorated, and the corresponding equipment set member should not be terminated because the exchange replacement (outgoing unit) takes the place of the incoming unit.

- Fixed: Credits that were adjusted out appeared as open items in Receivables.

- Fixed: The 6.4.026 fix (first listed) for Receivables broke Payment collection.

- When a repair part or service is linked to a repair unit line item, the agent of the part/service line is now only set to match the repair unit line if the part/service line has no agent assigned yet.

- Added a check and notice for overcommitted line items before check-out or check-in.

- Added a Unassign Event command to the context menu on the Scheduler board to detach the event from all agents it is currently associated with. Completed events cannot be unassigned.

- Fixed: Open a customer's Receivables from customer maintenance, change Account or Comments on one or more receivables, then close the window and there was no prompt to save the changes.

- The Equipment Sets window now has an S.Find feature to find an equipment set of the current customer using Equipment Set Search Filters Bill Frequency and/or any Search Text found within the set Customer PO, Bill To Name, and Identifiers. The F3 key can also be used to toggle S.Find on and off.

- Fixed: Print All from the Scheduler could output events outside the days displayed on the board.

- Equipment Sets can now have Identifier Documents. To use them, configure an identifier document template for UISet ESets. This makes a new function S.Doc appear in the Equipment Sets window to edit the identifier document of the current equipment set.

The Db Console contains an entry ESETS.UI (6.4.025) to add a column required for this revision.

- Scheduler Board options Auto Refresh interval, View Days, and Board Hours are now all configurable in an option panel that can be shown and hidden using the board context menu entry Show Board Options, and all of these options are now sticky past logoff per user. The board hours end times are an hour later than begin times to allow a 24 hour view.

- Fixed: Assigning an order Agent by typing into the order header could give erratic results.

- Fixed: Applying a Write Off in the Receivables window raised an SQL error.
This bug might have been introduced in 6.4.015

- Fixed: Australian telephone numbers output from Forms for Orders are now formatted correctly with the country code.

- Fixed: Print output from the Scheduler for recurring events now outputs the first occurrence date shown on the board for EventBegin and EventEnd dates.

- Fixed: Scheduler event print output did not translate a participant's name when the participant was not shown on the board.

- Fixed: Scan Match tab for Available Inventory did not refresh after switching back to the Scan Match tab within the window and selecting a different stock item for Available Inventory.

- Scan Match now eliminates the Part number match when a Part number is identical to its reference Stock Number.

- It is now possible to Return a customer Payment order. In the Returns window, push the Payment Undo option F10 before proceeding. Upon check-out of a payment return, a matching negative payment and adjustment are posted to AR. It is possible to see both the payment and payment return in the Receivables window by viewing the Unapply list in the context menu. A payment return can create an unusual negative check tender (Check Return) on the return order.

- The Scheduler now has separate Print All Events (print all in the board time span) and Print Visible Events (print all shown on the board) functions.

- The Return Lines to Original Location option in the Returns window is now sticky per user.

- Fixed: The special order line item type flag appeared on lines returned by scan code when the sale was a special order.

- Fixed: Repair parts returned using an identifier in the Scan Code were added to the return order with the linked repair unit.

- Fixed: Repair parts returned using an identifier in the Scan Code that were provided under warranty did not have their Price and Total struck out, despite having zero $ effect.

- Fixed: Adjustment line items with line numbers ending in non-zero could not be voided.

- Added a field RefTrxStatus to outputs from Forms for Orders to enable analysing the status of a referenced line item. For example, to show a section only if the order is ready (serviced) or the line has the ready checkbox checked, or if the line refers to another (like a repair part or service) then the referenced (repair unit) line is ready, use an expression like this in the Print condition:

- To better handle multiple users entering events concurrently, the Scheduler now performs an additional check for conflicting events in the database when an event is added to a specific agent on the Daily view. This check does not detect conflicts with recurring events added by another user.

- The Scheduler board's auto-refresh now resets the interval when a manual refresh occurs.

- Added an optional Issued date to Step 1 of Recurring Billing to override the bill issue date.

The Db Console contains an entry RBILLING.Issued (6.4.021) to add a column required for this revision,
and File: CopyLineItems 6.4.021 for part of third fix above.

- Fixed: eMail All from Recurring Billing Output sent the same attachment to all recipients.

- Voiding or Completing an order now clears all the custom Order Status flags.
To clear in one sweep all custom Order Status flags from orders already closed or voided, execute this SQL in the Db Console:
UPDATE ORDERS SET OrderStatus = OrderStatus & ~ 2146435072 WHERE OrderStatus & 2146435072 <> 0 AND OrderStatus & 32769 <> 0

- Fixed: If in single Day View the primary participant was assigned to an unassigned event in the Scheduler Event window, the event box did not move accordingly on the scheduler board.

- Scheduler Event Lookup can now search for events by note contents, and displays the first 80 characters of notes in the results. Notes are searched for the search term anywhere within the note text, it is not necessary to add a preceeding % character.

- Added refresh options to the Scheduler board context menu: Refresh Board Now F5, and Refresh every 1, 2, or 5 minutes. Note that the board cannot auto-refresh while editing an event. A clock icon appears on the upper left of the board title to indicate auto-refresh is on.

- Added week day selection to Scheduler Events that recur on a Weekly frequency. If no week day is selected, the week day of the initial occurrence continues for recurrences.

- Fixed: Parts and Services assigned to a repair item under warranty were not warrantied. This was broken in 6.4.015

- Fixed: Orders created for Scheduler Events at an event address with a Bill-To Other now redirect the order's bill-to.

- Fixed: Completing check-in of a Transfer could result in an SQL error. This bug was introduced in the 6.4.014 revision of CostInvoice.

- Forms for Orders now outputs ItemImage that can be used as the expression for an Image element on forms.
Example expressions: ORDER.ItemImage or INVOICE.ItemImage (without quotes) depending on the form.
Set the Resolution(dpi) of the image element to 150 or 300.

The Db Console contains entry File: CostInvoice v6.4.018 to implement the third fix described above.

- Added an Item Image viewer to the context menu of order line items and Item lookup rows, and there is a new Item Image tab in Items maintenance that displays an image of the item in context.
Item Images are expected as follows:

- Fixed: Received inventory on an open PO could not be undone. This was broken in some past revision.

- Forms for Orders now outputs line item identifiers for intangibles: Services and Charges.

- FrontLine now checks for and warns about duplicate key texts in Setup Lists.

- Fixed: The Invoice and Check-In cost display revision in 6.4.014 for Landing cost separation multiplied by Quantity twice.

- Added ongoing Notes to Receivables. Multiple note entries on the receivable are collected in the note body.

- Recurring Billing can now redirect bills. A redirected bill has the Ship-To address set as the Service Address. The conditions for this to occur are:

- Fixed: 6.4.011 added a bug to tax calculations on packages sold in Package As Discount mode.

- Fixed: When an item was returned that had multiple recurring bills to the customer at different rates, the return value did not necessarily show the most recent bill rate.

- Added a No Shipping flag for Locations. This flag affects the Destinations and line items listed in Shipping. The location that the unit is shipping from is examined for this exclusion.

- The default Next Bill date calculated for Equipment Sets with bill frequency periods longer than a month should now be correct for both Next Bill defaults to 1 period from now and Next Bill defaults to 1st of next period company setting in Equipment Sets, Rentals, Contract Options. For example, assuming today is February 9 2013, the default next bill date calculated for Next Bill defaults to 1st of next period is:

- Added security contexts for Contacts in four groups: Agents, Customers, Vendors, and Locations. There is one context per group, as for Addresses. To give users who have access to these groups their contacts access without editing access profiles in FrontLine, execute this SQL:

- FrontLine has begun logging field value changes in maintenance windows: Agents, Customers, Vendors, Contacts, Locations, and Items. There is no facility to view this change log yet.

- FrontLine now records landing costs separately from unit costs. This enables revisions to landed costs of special orders without affecting last purchase cost. In the Costing grid of a PO CheckIn, the landed cost can be seen by turning on the Include Landing Cost menu option. If there is a landing cost not shown, a + (plus) sign trails the unlanded cost displayed.

The Db Console contains entries LandingCost (6.4.014) and File: CostInvoice v6.4.014 (superseded by 6.4.018) as a required part of the costing revision,
and File: MNTLOG (6.4.014) as a required part of new logging features,
and File: CopyLineItems 6.4.014 for the last bill return price fix.

- Detaching and reassigning repair units from their line item (new in 6.4.012) now declines with a notice if repair parts or services are assigned, and re-evaluates warranties upon unit reassignment.

- Unit Tracking now allows viewing event orders even when it was opened from an open order.

- Fixed: Credit Limit check should consider Recurring Bills as already posted to AR.

- Fixed: Service Orders for Invoicing customer order lookup did not include partially invoiced service orders.

- Repair unit line items can now have equipment detached and reattached before the repair is complete or the unit has been shipped. This makes service orders created from repair quotes functional.

- Added a Reference Orders function below Redo Order to lookup any orders that were created in reference to the order in view.

- The balance summary line in the Receivables window now also shows amount Open On Account, which is the total tendered "On Account" but not yet invoiced.

- When a customer has insufficient credit for an order, FrontLine now offers to put the order on hold upon deferring instead of making it a quote. Orders On Hold do not create open demands to generate purchase orders.

- Fixed: Upon creating an order from a Scheduler Event, the Item Action prompt could become inaccessible.

- Fixed: A recent revision had the green fulfillment box on line items not reappearing until line item details where opened after the order was reopened.

- Fixed: Saving an ordinary note right after saving a template note in the same window raised a primary key violation on the NOTES table.

- Fixed: Returns of special orders from the Returns window would have the return line items marked for special order, and appear as demands in purchasing auto-gen.

- The Credit Balance check for placing orders On Account now includes open (unposted) On Account tenders in the balance calculation.

- Duplicate ship tracking confirmation warning message in Shipping elaborated with consequences.

- System Administrator can now print and defer orders without entering required order Identifiers, Agent, or Customer PO.

- Added a Redo Order function for closed customer orders and presented quotes, available on the drop-down beside the Returns function.
Redo creates a new order with nearly identical line items except that taxes are re-evaluated.
Where possible, FrontLine attempts to recommit the same inventory and customer units by tracing their event history and analyzing their current status.
There is a new security context to enable this function for users, without permission the function is invisible to a user.

- Fixed: Purchase Order Ship-To address selection list did not exclude retired location addresses.

- Fixed: Unit Tracking did not sort and correctly indicate user and date on groups of recurring billing events.

- Fixed: Package member lines in Package As Discount mode are exempt from the No Taxes warning.

- Payments and Credits on Receivable Statements are now output as negative values.

- Quantity in Line Item Details - Selected Items for Repair Unit line items where there is no unique identification can now be typed in, subject to the usual constraints.

- If a plain SQL report query text begins with /**/ (an empty comment in SQL) FrontLine will open the results in a grid like a diagnostic report.

- Fixed: Bugs related to Invoice Credits. Part of this fix is in two database procedure: NewInvoice and CommitInvoice.

- Fixed: Receivable Statements with no end date now includes open receivables due in the future in the Due Now total.

- Fixed: Receivable Statements only included overdue amounts in Due End sum. Any amount posted by the End Date should be included.

- The Receivables window now shows Totals and Balances above the grid instead of below, and the rows are initially sorted to show Payments and Credits first.

- When invoked for a Payment from a customer order, the Write Off function in the Receivables now prompts for an amount to write off, permitting a write-off of only part of the balance.

- Added an Export function to the Receivables window, available on the context menu, and the Line column is now named PLine.

- Added a Find function, and sorting by clicking column titles in the Receivables window for most columns.

- Receivable Statements are not output for customers who specify No to Statements, unless the customer is specifically identified in which case a confirmation is raised.

- Line item accounts are now assigned for Payments: Revenue is assigned the location's AR account, and Cost of Sales is assigned the location's Discount account.

- FrontLine now attempts to apply a credit from a return order or invoice credit towards the original receivable if the return credit is less than or equal to the receivable and no other payments or credits have been applied towards the receivable yet.

The Db Console contain procedure update entries:
File: NewInvoice v6.4.007 and File: CommitInvoice v6.4.007 (superseded by 6.4.047) required to complete the first fix above.

- When the scheduler board is opened and in focus as a floating window from an order, Ctrl-F6 brings the order window back in focus without attempting to open an order in context.

- When viewing multiple days, the scheduler board now sets column widths to fit in the window.

- When a line item is created from a scheduler event where the customer unit is not identified, FrontLine now includes the Item Action prompt when creating the new line for a tangible.

- Added a Resource Selection block enclosing the Certificates and Categories selector in the Scheduler, adding three new options available in multi-day views:

- Fixed: An old bug resurfaced where a customer template supplied all the data for a new customer, and the user entered nothing in the Customer block on the left side of maintenance, saving created the new address without a new customer.

- Web updates for order status changes were suppressed after a Shipped event was sent for the order. Now they are also suppressed for the order after an Out Of Service event. In other words, after a unit Shipped or unit Out Of Service web update is sent, no more order status updates are sent for the order.

- The Scheduler now has a Week and 5 Day view. The view can be selected from the context menu, and pressing F2 toggles between the single Day (multiple agent) view and the last multi-day view used.

- Scheduler event All Day option has been moved to the Duration selector.
All Day duration sets the event start time to 6am and end time to 6pm.

- Scheduler events now have a Background option. Background events are transparent to normal events on the scheduler board, and can only be manipulated using the right-click context menu.

- When an entity or address is assigned to a scheduler event, matching entity and address notes are shown to alert the user.

- The Quote function is now active on completed customer orders introducing an ability to create a new Quote from a completed customer order. Quote life indicated in company settings is applied to the age of the completed order.

- Scheduler print output for events now has address fields, including a combined field Address.

- Fixed: Excluding an equipment set from Step 2 of Recurring Billing did not untag the meter readings used for the billing upon proceeding to the Step 3.

- Fixed: Parts and Services used for a Repair that is covered by warranty or service contract did not produce tax details, and thus triggered the No Taxes warning.

- Implemented a Corporation Vendor status flag that affects the output format of Vendor EIN like the corresponding customer flag.

- ItemDescription output from Forms for Orders for Miscellaneous lines items now only uses the line note subject if the miscellaneous item description is blank.

- When a line item's identifier document template contains an airport identifier, a two line Airport Info display in Line Item Details now appears below the unit Identifiers list, with information about the last airport identifier encountered above by the user.

- Fixed: Typing in a customer number on a new order header that matched both a customer number and a Customer ID could randomly select one of the two instead of consistently selecting the customer number match.

- Fixed: Special order demands listed in detail in the purchasing auto-gen floater for partially fulfilled customer special orders would start the subtraction with the quantity already reduced by quantity fulfilled. This was a display issue, the quantity suggested to purchase was correct.

- Changing a customer order department on the header now re-evaluates the accounts of all line items that do not have a department override specified.

- When a customer order only has payment line items, Department and Customer PO requirements are not enforced.

- The UIType field output from Forms for Orders is no longer translated since IdentifierName provides the translation.

- Receivable balances can now be written off while taking a payment. In the Receivables window, choose to write off a balance when selecting receivables to pay for using the button above or the context menu. The total selected to write off appears in the lower right of the window.
A receivable balance can also be written off in this manner without paying a part of it, the payment will appear on the order at zero price.
Note that the amount written off appears on the order payment line item's C.Cost field.

- Fixed: Rentals should be excluded from costing. This fix is implemented in a database procedure update.

- Fixed: Discount line items should be excluded from the missing tax check introduced in 6.4

- Fixed: The last default account for payment tenders from the location record is now AR for On Account, and Cash for the rest.

- Fixed: A couple of interactive bugs in the Tender Types configuration window.

- In Customers maintenance, the functions for Receivables and Receivable Statements now drop down under an AR button instead of the Parts button. The POS button to toggle the POS vs OE template is replaced by a context menu available by right-clicking anywhere on the toolbar.

- Bill-To redirection of customer orders now also occurs when the customer is selected by entity lookup, by typing a customer number directly into the header, and by returning or repairing a customer unit on a blank order. Previously, it only occurred when a ship-to address was selected by typing into a field of the Ship To address and choosing from the lookup triggered.

- When a Total Paid amount is entered for Receivables payment, and a Balance remains unapplied, Apply now creates a non-specific payment for the balance.

- Added Category and Location filters to lists setup for Item Category Accounts.

- Added a New function with a Copy option to lists setup for Item Category Accounts.

- Added a Department list, along with with department qualifiers on Item Category Accounts, Orders, and Line Items. Adding entries to the Departments list makes a Department field appear in the header of customer orders, and in Line Item Details. A line item's department defaults to the order department. When it is the default, the display in Line Item Details is in gray italics. If a line item's department is overridden, changing the order department does not affect it.
Item Category Accounts assigned by sales and returns are now sensitive to department, agent, and customer discrimination. Physical counts are not. Recurring bills do not assign accounts yet.

Selection of item category accounts with discrimination is weighted by a sum of:

The Db Console contains entry: File: CostInvoice v6.4 (superseded by 6.4.014) to implement the backwards compatible costing fix above,
and entry: File: ItemCats + Depts v6.4 required for the extensions added to Item Category Accounts,
and entry: File: CommitInvoice v6.4 (superseded) required to forward departments to completed line items.
Note that FrontLine 6.4.002 will not function without these database updates.
Log in as system administrator and proceed directly to the Db Console to apply them.

- Implemented some additional checks to prevent users invoicing over each other when they take over an order inappropriately.

- Payment line items on customer orders now display the OrderID that incurred the receivable. This display only works on payments created with the company setting Enable application of Payments to Receivables turned on.

Microsoft SQL Server database Compatibility level note:

FrontLine requires that it's MSSQL databases have their compatibility level set to SQL Server 2005 or later, otherwise some features like the Receivables window will raise an error about an Ambiguous column name.

This revision can be made in SQL Management Studio. Right click the FL database, choose Properties. Then Select a page Options, and use the compatibility level drop-down, then OK.

- Fixed: The Resource Categories selection in the Scheduler did not work after Agent Categories were customized.

- Fixed: The Address type mismatch revision in 6.3.036 broke default contact assignment on a new order.

- Fixed: Changing a Zip (postal) code in maintenance could result in an SQL error.

- Fixed: Disabled Agents could be assigned to Customers using Agent Lookup from customer maintenance.

- Fixed: When deferring a customer order where the customer had some credit available but not enough to cover the order, the deferred order credit check could fail.

- Fixed: On a Tax Report generated with the Recurring Bills by Scheduled date option, Recurring Bill returns are included by refund date rather than the recurring bill scheduled date.

- Special customer order line items now list corresponding voided special purchase orders in the Special Order context menu, with a (/) indicator.

- Agents can no longer be saved with blank Initials, and if one is on record with blank initials it is displayed on orders as {id} instead of blank.

- When a customer with a Closed agent is assigned to an order, the closed agent is not assigned to the order, as if the Customer had no agent.

- Added a Include Non-Identifiable Items option to the Equipment Search feature. If this option is not selected then items with a blank identifier document template are excluded from the search.

- Added Signatory Name text outputs to Forms for Orders, including PDF. The form expressions are SigLineName for the SigLine image, and SigInvoiceName for the SigInvoice image.

- Added a Company Setting Enable application of Payments to Receivables under On Account and Receivable Payment Options (12th from top On Account Tenders & AR) to activate some of the new AR features below.

- Inventory units marked In Use can now be committed to line items on Adjustments.

- Added a security context for Tax Detail Maintenance to give regular users access to tax setups.

- When a customer order has a redirected bill-to, the title of the Bill To address section is now boldfaced.

- If a customer order has a missing or invalid TaxGeoCode, the warning is now repeated whenever the order is opened, and the order cannot be checked out, shipped, or have delivery ticket or ship ticket printed.

- If no taxes are found for an item's Tax Category in a customer order's TaxGeoCode, a warning is issued when the line item is created and the order cannot be checked out.

- The Tender Types configuration in Company Settings has been elaborated to define an Account for each tender type (including On Account) at each location, as well as a default for all locations. Defaults for a location are shown in light italics.

- The Payments list on customer orders now has an Account column. Defaults are shown in light italics, it is only necessary to enter overrides. There is a new security context Tender Account to give users access to this information.

- Implemented Cash Application in Receivables. From Customers maintenance, the drop-down menu beside the Parts button on the top bar now has entries for both Receivables and Receivable Statements.
To apply credits, open Receivables here and:

The Db Console contains two entries: AR rev (6.4) to add new columns to the AR and PAYMENTS tables, and PTL (New in 6.4) to create a new table.

- Fixed: SQL error in Purchase Order Lookup when Lookup By is a PO I.Doc member.

- Fixed: The deferred order credit check introduced in 6.3.018 could raise its prompt when the order was already covered.

- If an address assigned to an order's x-To is the default x for the order entity, the Address type mismatch confirmation prompt introduced in 6.3.030 does not appear.

- Added Curação to the built in country list, using TLD cw and telephone country code 599.
Note that Curação is the same country as Netherlands Antilles, which has TLD code an.

- Fixed: Equipment shipped to depot should not appear in the Service Contracts window to add equipment to a service contract after invoicing.

- Fixed: Equipment received from depot should inherit the unit warranty of the unit that was sent to depot upon invoicing if a new warranty wasn't entered. Part of this fix is a revision to the CommitInvoice stored procedure.

- Fixed: FrontLine now uses a more pertinent date to determine warranty status.
Instead of using the current date, it now uses the repair unit line item scheduled date (if any), or the order scheduled date (if any), or the repair unit line created date.
Limitation: Changing the scheduled date of a repair unit line or service order after assigning parts and services that might be covered by the warranty does not change the coverage status of those assigned parts and services. To re-evaluate coverage, the parts and services have to be reassigned to the repair unit.

- Fixed: Order lines created from miscellaneous line items on presented quotes started out on the new order with no tax details.

- Receivable Statements can be opened directly from Customers maintenance using the drop-down menu beside the Parts button on the top bar.

- Shipping now puts the actual shipping charge in the freight line item's C.Cost [CCost] column.

The Db Console contains entry File: CommitInvoice v6.3.035 to revise the CommitInvoice stored procedure.

- Fixed: Sale return line items created from the Returns window could be returned to a rental location if requested by user override.

- Fixed: Return lines items created from the Returns window could be returned to a location where the item category accounts were missing.

- Added an aging summary to the Receivable Statements feature. The data is available on the report form as a separate dataset named AGE. The default brackets are 30, 60, and 90 days, which produces up to five subtotals. Age brackets can be customized using the Receivable Age List, with any number of ages at desired numbers of days. Current and Beyond brackets are automatically added to the report. Correct use of the aging on a form is to put it in a separate subreport, and make this the child subreport of the entity footer from the main report. A sample report is provided to illustrate.

- Fixed: The Customer Equipment list in Scan Match did not show the contract coverage umbrella when the equipment was committed to a service order.

- Added a Statement Categories List, a new St.Category field for customers, and a Statement Category selector to the Receivable Statements feature. Statement Categories segregate customers for statement output, and allow different statement forms to be used per category. The Statement Form column in the category list is appended to the standard SchedulerEvents form name. Example, if the statement form is ATL then the form file used would be ReceivableStatementsATL.rep

The Db Console contains an entry CUSTOMERS.StatementCat (6.3.033) to add a column required for this revision.

- Fixed: Return line items had their Created and Scheduled dates copied from the prior transaction. This fix is in the database procedure CopyLineItems.

- Added a Retired GeoCode option to Tax Detail maintenance to indicate that this TaxGeoCode should no longer be used. Retiring a Tax GeoCode does not change data on existing addresses, instead it allows an old Tax GeoCode to remain on file for history and reporting purposes without allowing users to assign it to addresses.

- Added a Receivable Statements feature to the Inquiry group. There is a new security context to grant users access to this feature. A summary of receivables per customer is shown in the window for perusal before reporting. Options provided include:

The Db Console contains an entry File: CopyLineItems 6.3.032 to implement the fix above.

- Fixed: Signature output missing from invoices.
Note that for a line item signature image to not occupy space in the form section when there is no actual signature, the image property Draw Style should be set to Full.

- Fixed: Return line items created by the Returns feature now use the inventory account at the destination (if found) instead of copying the inventory account from the sale line item.

- Fixed: The Import Customer Equipment feature could miss the last column header of the import file.

- Fixed: The very first time a service order invoice was printed in a FrontLine session directly from the Invoice window, the output was sorted like a sales order instead of a service order.

- Fixed: In some circumstances, clearing the Stock or Customer criteria in Transaction Inquiry did not reset the inquiry filters.

- Fixed: A service contract coverage umbrella was shown for customer equipment in the Scan Match when when it was a provisioning contract.

- Added an Address type mismatch confirmation prompt when an address selected for a specific purpose on an order is not designated for that use.

- Added an ability to render line item and invoice signatures on Forms for Orders. The form expressions are SigLine and SigInvoice, on an image component.
Example expressions: ORDER.SigLine and INVOICE.SigInvoice without any quotes. Note that order forms cannot display an invoice signature.
Limitation: The signatures are drawn on screen and on printer output direct from FrontLine, but not in PDF files.

- Fixed: When an order is created from a presented quote, contacts, customer PO, and order I.Doc values assigned on the quote are now copied to the new order created.

- Added a green checkmark to the upper right of selected options in the package model option selector.

- Item Types Miscellaneous and Charge can now be set together in Items maintenance. Miscellaneous Charge line items receive a default non-zero price, unlike miscellaneous stock items.

- Items must have at least one identifier in their doc template to be sent to depot. Otherwise, FrontLine now disables the Send To Depot function in Line Item Details, displays the Depot Repair Start / End fields in Items maintenance in gray, and excludes such items from the All To Depot order function.

- Added an Import Customer Equipment feature, accessible from customer maintenance. This feature allows importing data from a delimited file, performs checks and validation, and allows the user to review and correct the data before importing. Warranties can be provided in the import file, calculated from the imported sale date, or entered manually during review. Imported equipment appears like previously unknown equipment that came for repair, except that the unit event has an additional DtlStatus flag. See DtlStatus code table for Customer Equipment.

- Fixed: Error about not a valid integer value when order lookup was scrolled to the Country column. This bug was introduced in 6.3.027

- Fixed: The batch review step in Recurring Billing now calculates flat billing for item types Recurring Rental and Service Contract as well as item type Flat Billing. This is consistent with the actual bills generated in the next step.

- Dates in the Scheduler Event window now have a month calendar available, and times are included with the date.

- When a customer order is opened for read-only viewing from a purchase order, or vice versa, the read-only order window now floats beside the open order window so both can be seen and used concurrently on screen.

- Fixed: The deferred order credit check introduced in 6.3.018 should not apply to Inventory RAs.

- Fixed: Introduction of report access groups in 6.3.017 put the file name list in the wrong column.

- Fixed: Occasional junk characters at the end of menu entries in contact selection lists on an order.

- The Ctrl-Alt-R keyboard shortcut that opens Repair Codes from line item details now also toggles back to the unit identifiers from the repair codes.

- Added a provision for up to five custom Scheduler Event Status codes. Custom event status codes are not mutually exclusive, and do not create color differentiation on the scheduler board. They appear as checkboxes alongside the mutually exclusive built in status selectors in the Scheduler Event window, and when checked, also appear in text at the top of the event hover hint.

- Added a drop down selection of several identifier documents related to the event that can be viewed from the Scheduler Event window.

- Added to company setting Quote Options a Location of orders created from quotes. Orders from quotes can now be created always at the quote location instead of workstation location. Additionally, even when workstation location is chosen, if the workstation location and quote location do not match on rental, the quote location will be used to preserve rentals vs non-rentals.

- Added an Agent field to System Users to associate an agent with a user. Set this value by typing agent name or initials into the field. When a user is assigned an agent, and that agent is assigned to an order, the order is considered this user's order for security purposes. Additionally, when this user assigns a customer or vendor with no associated agent to an order, the order is assigned this user's agent.

The Db Console contains an entry required for this revision: PEOPLE.AgentID (6.3.026).

- Fixed: When customer templates were used and a user saved a new customer without adding any information on the left side of maintenance, the new customer did not receive a good CustomerID.

- Fixed: When a payment amount was entered with tender type not identified, FrontLine defaulted to Cash even if cash is not accepted in the company setup. Now if cash is not accepted it will use On Account, and if that is not accepted either then it will notify the user to identify the tender type first.

- Added a Scheduler Event Lookup function to the Scheduler accessible using the context menu or the F3 key.

- Added a Note field to the export from Equipment Search containing the first 255 characters of the note body.

- Added an Open Scheduler command to the drop-down from the Scheduled field of an order processing window.

- Added a Historic mode to the Identify Unit window when it is invoked from Unit Tracking. Activating this search mode will find units using identifiers of prior units that have been replaced by events like depot swaps.

- When a special or miscellaneous purchase line item is received with company Cost Option "Cost Special Order sales by Purchase Cost" enabled, a resource cost is created on the corresponding customer order line item if it was missing.

- FrontLine script and executable files retrieved by the Db Console are now hosted at r.ormandy.com instead of www.ormandy.com

- Fixed: Negative line item price override on a miscellaneous item with a blank price was ignored.

- When card tender account numbers are not required by company setting, it is now possible to enter only the four digits preceeded by an 'x'. If the tender has no card type indicated, FrontLine defaults it to VISA.

- The FrontLine Scheduler can now be used alongside Order processing. Open the scheduler in this mode by invoking it from Line Item Details.

- Fixed: Voiding a purchase order with miscellaneous purchase line items that were not voided individually did not make those purchases reappear in the Miscellaneous Purchases window.

- Fixed: A recent revision broke the order Ready/Serviced function on sales orders.

- The ContractExpiration output by Forms for Orders now reads the Equipment Set's Contract End date when the contract's Terminated date is blank.

- In file maintenance, when an address matches multiple tax geocodes but has not been assigned one, FrontLine will now prompt the user to select one from the list instead of automatically assigning the first geocode listed.

- International phone numbers entered with a leading + (indicating a country code) are saved with hyphens and spaces intact, and not formatted further during output. This allows the user to provide a custom readable format using embedded spaces and hyphens. Beware that to find such numbers in a lookup one must include any such plus signs, spaces, and hyphens in the search text.

- In the Scheduler Event window changed the Title field to Subject to reduce confusion.

- Added a Scheduler Board Event Caption Text option to the Company Setting for Scheduler Options with options for Event Subject vs Entity Name vs Event Time. This setting only affects the title text of the event rectangles on the board.

- Fixed: Miscellaneous line items added manually to an order should have a blank price.

- Fixed: Miscellaneous line items added to a purchase order after changing the location in the Miscellaneous Purchases window be ordered at the initial location instead of the new location.

- Fixed: Adding line items to a purchase order from auto-gen could trigger an error about the dataset not in edit mode.

- Fixed: In some unusual circumstances, the State entry field in an address maintenance feature could move off the right edge of the window.

- When an item's primary identifier is not required at receiving, FrontLine now receives it as a non-identified item with only quantity input, even if that primary identifier is unique.

- Added an optional new List Package Member Groups that can serve two purposes:

- Added a Notify Option to Company Settings to Notify user when they have no cash drawer assigned. FrontLine will no longer warn the user about no cash drawer assignment at their location unless this uption is turned on.

- Added basic recurring events to the FrontLine Scheduler. In the Scheduler Event window there are now these fields:

The Db Console contains an entry required for this revision: CALEVENTS.EventExp (6.3.020).

- Fixed: The Order Serviced (Ready) function bypassed the order credit check introduced in 6.3.018

- Orders with a negative total are not subject to the deferred order credit check introduced in 6.3.018

- Closed (Retired) Agents are no longer shown on the scheduler board. Events where they were the primary participant now appear as unassigned.

- Added color differentiation of event status on the scheduler board. There is a predefined set of subtle colors which can be customized from the Company Setting for Scheduler Options. The predefined colors are:

- Fixed: Sometimes when an order was opened with blank prices and FrontLine asked if they should be repriced, no price was assigned.

- Standard Cost is now used as a last resort when adding line items to a PO from the Generate Purchase Order function.

- Ticking the boxes in the Receivables window no longer allows Total Applied to exceed Total Paid.

- Added a special order lookup "Orders In Use" to list orders FrontLine has flagged as in use.

- Demands and special order line items from orders that are In Use or On Hold are now disqualified by the Generate Purchase Order function.

- Elaborated the Company Setting for On Account Tenders (tenth from top) to add a group for Deferred Customer Orders that must be Tendered or On Account. Sales Orders and Service Orders can be selected independently.

- Added scheduler event printing functions. On the scheduler board, the context menu for Print has been elaborated, and in the Scheduler Event window a Print function has been added. The form used is SchedulerEvents.rep
Note that printing from the Scheduler Event window saves any changes made to the event before printing.

- Resource Categories on the Scheduler board are now sorted by category name instead of category ID.

- In the Scheduler Event window, Participants who have all the Certifications checked now have a trailing asterisk beside their name.

- Order lookup now hides totals of other users' orders when a user does not have a Read permit for the Other's Orders context.

- Changed the Search By labels for two entries in Order Lookup:
"Open Quotes" became "Quotes, Open"
"Quotes (recent complete)" became "Quotes, Presented"

- Added two key words to SQL texts in Reports: MyPersonID and MyLocationID. When these are found in the SQL text of a .sql or .rep report, FrontLine replaces them with the PersonID or LocationID of the current session.

- Added a security context for Report Access Groups (A-H) and a corresponding Access Group column in the Reports window during report maintenance to restrict user access to specific sets of reports. Report Access Groups A to H can be used. Each report can be placed in one access group, a security profile can grant a user access to multiple report access groups.

- Fixed: Since the Line Item Details toolbar reorganization in 6.3.013, the special order and backorder buttons would stay down after first use.

- Added a Find function to a context menu, and sort by clicking column titles in the Identify Unit window.

- Increased the maximum result rows retrieved in the Identify Unit window from 200 to 800.

- Added a Link from Clipboard function to the equipment list context menu of the Contracts maintenance window. This function uses the text in the Windows clipboard to identify equipment to add to the current contract. Only equipment listed are searched, it may be desirable to make sure the Show other customer equipment option is on. A tab delimited report of the changes made is put back on the clipboard, replacing the source text. Paste into a notepad or spreadsheet to view the result details.

- Signatures can now be collected for Invoices as well as Receipts (POS) before they are confirmed.

- Signatures can now be collected for open line items. Line item signatures are stored with an [ImgItm] key of the line number plus 1,000,000.

- Line item Created date and time is now displayed as a read-only field in Line Item Details.

- The toolbar in Line Item Details has been moved up and rearranged to occupy the full window width for more horizontal button space.

- Added spell checking to notes.
Stock numbers that have no punctuation characters or spaces are also recognized as valid words, and corrected for character case.
There are three dictionary files that need to be added to the main FrontLine folder (where the executable is) for spell checking to work.
These three files can be found in the Dictionaries folder that is in the Testers folder on my.ormandy

- Fixed: The Customer Equipment list did not appear for customer orders without redirected billing. This appears to have broken months ago.

- FrontLine should now prevent Windows 7/Vista/2008 from altering its scaling calculations and font rendering when display DPI is over 100%.

- Improved enforcement of the Isolated Returns company setting by disabling Exchange, Sell, and Repair actions in Item Action on a Return order.

- Added security contexts "Order Check Out" for Customer Orders and "Order Check In" for Purchase Orders. The permit effects are:

- Added a boldface highlight of days with events in the month calendar of the FrontLine Scheduler.

- Scan Match will now match part numbers for any vendor or customer, even after the order has been assigned to an entity.

- Added sticky minimum text box dimensions to the Package Content Selector, accessible using the drop-down menu found on the edge of the Alt button.

- Identifier value storage expanded from 30 to 60 characters. A corresponding database update is required.

The Db Console contains an entry required for this revision: Widen Identifiers: UIDS.UIValue (6.3.012) to increase identifier storage space in the database.

- Fixed: The quantity text output by Export MOL could overrun the new line and thus run two lines together when the UOM factor division produced a long stream of digits after the decimal place. Now the output is limited to 4dp.

- Added fields INVSUM.Scheduled and INVSUM.Fulfilled to Periodic Invoices output. These can be used to indicate the billing period of a particular recurring bills within the periodic invoice, but note that these fields can also be used on orders that are not recurring bills.

- Added an optional default billing frequency [BillFreq] to ITEMS records to indicate the target billing frequency when this recurring billing item is automatically added to an equipment set. There is a new security context to allow access to this field. A database update is required:

The Db Console contains an entry required for this revision: ITEMS.BillFreq (6.3.011) to add a new column.

- Added an Import feature to the Receive window to read a list of primary identifiers from either a text file or the clipboard:

- Fixed: The User Option New line items to workstation Location should only apply to Customer Orders.

- The Received Inventory Check In notice introduced in 6.3.005 for costing layer consistency is no longer shown for Transfers and Adjustments.

- Implemented vertical scrolling for the Package Content Selector. If the package contents cannot fit in the window with a least four text lines for each member, a vertical scroll bar appears.

- Fixed: The purchase order drop-ship address fix in 6.3.007 broke the display of current location as ship-to on a new regular PO.

- Fixed: Another situation where a unit event record was not released upon voiding a customer line item.

- Fixed: FrontLine should now correctly prorate members of equipment sets with Bill Frequency shorter than monthly.

- Recurring Rentals are now treated as flat billing rate items, like service contracts.

- Fixed: The Price column in Service Contract maintenance only showed 2 decimal places.

- Fixed: A purchase order drop-shipped to a customer address would have the ship-to address revert to a location address upon reopening the PO.

- Fixed: Saving Resource Costs with an Item Price upon creating the first order or quote of the session would raise an error "Data conversion is not implemented for datatype DateTime to SmallInt (FieldName='UOM')".

- Purchase Order line item prices can now be changed after the line has been partially checked in.

- Added a Service report group for use in the Reports window.
SE_=Service is the file prefix FrontLine uses to guess the report group.

- Added Contact Name to the Search By and results of Order Lookup for customer orders and purchase orders.

- Added Contact to the Search By and results of Customer Lookup. Note that Contact Name is only shown in the results when Search By Contact Name is used.

- Typing into a Contact field of a new customer order address now invokes customer lookup by contact name.

- Added a green check icon to Meter Readings when a reading has been used on a bill.

- Added support for Topaz SigLite signature pads. FrontLine's support for Topaz signature pads is through their SigPlus interface software, which must be installed on the PC. This software is available from the Topaz web site here. FrontLine should detect the presence of this software and attempt to use the pad automatically. The implementation is tested with a signature pad connected to the PC running FrontLine.
When FrontLine runs in a RDP session see the Topaz Signature Pad from a Remote Desktop section below.

Topaz Signature Pad from a Remote Desktop

The SERVER needs two files in the Windows folder:
SigPlus.OCX (registered with REGSVR32, users need read+execute access)
SigPlus.INI (with a suitable configuration for the signature pad model in use)

A Client PC that has a signature pad plugged into a USB port requires some configuration in Windows and the Remote Desktop Connection:

- Group Policy on the client PC needs one setting changed. Launch GPEDIT.MSC and navigate to:

- Computer Configuration
- - Administrative Templates
- - - Windows Components
- - - - Windows ComponentsRemote Desktop Services
- - - - - Remote Desktop Connection Client
- - - - - - RemoteFX USB Device Redirection
Enable Allow RDP redirection of other supported RemoteFX USB devices from this computer for Administrators and Users

A reboot of the Windows client PC is required after changing this policy.

Then after a reboot, on the client's Remote Desktop Connection, Edit properties:
- Local Resources (tab)
- - More (button)
- - - In the Other supported RemoteFX USB devices node enable USB Input Device (HID-compliant vendor-defined device)
Save the remote desktop connection for future connections, connect to the server and attempt to capture a signature in FrontLine.
Note that Windows may change USB names between connections and reboots so after disconnecting from the remote desktop where FrontLine is running then reconnecting the signature pad may stop working for FrontLine in the remote desktop.
To avoid this snag, users should close FrontLine completely on their remote desktop before disconnecting or leaving for the day.

- Fixed: Placing <FLF>OrderNote</FLF> in an email template would cause an error when composing an email for that form.

- Added an Item Status flag Bill Of Materials that can be set in Items maintenance. The BOM flag qualifies a Package as a simple collection of line items added to an order with no relationship after the selection. The Bill Of Materials (package) item itself is not added to an order.

The Db Console contains an entry required for this revision: ITEMS.ItemStatus int (6.3.006) to revise a column data type.

- Fixed: If the order customer was assigned, Scan Match did not find equipment that belongs to other customers. This was broken in release 6.3

- Fixed: Closed locations are now excluded from the Unidentified location selection list in the Scan Match window.

- Due to costing layer consequences, FrontLine now raises a warning about leaving received goods not checked in on an open PO, and checking out received goods on a customer order that have not been checked in on the PO.

- There is a new Cost Used option in the Order Totals window for calculating margins: Company (Last) where the Last part reflects the company setup shown above, and could instead be Std or Avg or Inventory, and note that closed line items have their cost recorded so this choice does not affect closed lines:

- There is a new function on customer orders to show a C.Cost column, seen via the drop-down arrow beside the Costs function in the lower bar. Typing into the C.Cost column of a special order or miscellaneous line item sets the Item Cost value in Resource Costs. Otherwise, commission cost overrides entered in this column are stored in TRXIP.CCost, and recorded on the line item change log, and shown boldfaced in FrontLine. Line items with this override are tagged with a TrxStatus flag for Custom Commission Cost, abbreviated CCC, decimal value 131,072.
This flag can be used on reports, and is used by FrontLine costing procedures to avoid changing override costs.
If company Cost Options indicate the use of Inventory Cost for C.Cost and an item uses the FIFO or LIFO costing method, FrontLine estimates the unit cost on open line items using a single layer, and adds Fi or Li to the C.Cost column text.
All C.Cost values in gray (instead of black) are estimates that can possibly change at time of invoicing, but only lines item with quantity greater than 1 using Inventory C.Cost by FIFO and LIFO are likely to change due to the estimate based on a single layer where invoice costing uses as many layers as necessary.

- There is a new security context under Customer Orders for C.Cost. If a user has no permission for this context, they will not see the drop-down on the Cost function. Permission to modify the C.Cost uses this context unless the line item is a special order or miscellaneous, in which case it uses the Resource Costs security context.

The Db Console contains two entries required for this revision:
File: CostInvoice v6.3.005 to revise this stored procedure,
and TRXLOG.CCost (6.3.005) to add the CCost column to TRXLOG.

- Fixed: Changing the Scheduled date on a repair unit line item would prorate the line if the equipment were present on equipment sets with a recurring billing price.

- Changing the unit cost on a purchase line for a special order or miscellaneous item now updates the Item Cost on the customer order line Resource Costs.

- The Print function in FrontLine Scheduler now displays a printer selection window before printing. The schedules are printed in landscape orientation regardless of the printer default.

- Checking out a line item linked to a scheduler event now marks the event as completed.

The Db Console contains entries TRX[IP].CCost (6.3.004) to add new fields to the database,
and File: CommitInvoice v6.3 to revise the CommitInvoice stored procedure.

- Fixed: The month calendar for setting date fields could behave as if in read-only mode when it should allow changes. This bug was introduced in 6.3.002

- The last four contexts for custom Order Notes as set up in Lists can now be edited even after an order is closed. This allows ongoing order notes to be entered.

- Added two links to the Third Party panel in the Welcome window for Telus integrations. Note that these python programs require the python runtime to be installed on the machine that executes them:

- Repair Unit line items are no longer prorated when the price of a corresponding unit on an Equipment Set is changed.

- Company Setting for Scheduler Options must be set to Use Internal Scheduler to use the built-in scheduler.

- The Scheduler can now be printed using the Print function on the context menu or Ctrl-P

- Fixed: A unit individually returned that was last on a recurring bill would retain the recurring bill flag on the return order. One consequence is if the return order is voided, the committed to return event was not discarded.

- Fixed: There were cases when a vendor was assigned directly to a Purchase Order that had no location assigned, FrontLine would not assign the default location Ship-To, leaving the Ship-To blank.

- Added a security context for Customers: Bill-To Other. If a user as no permit, this field disappears from the customer maintenance window.

- Added to User Options: Default New line items to workstation Location instead of the order location.
FrontLine User Options

- Scheduler enhancements including listing and allowing changes to event participants within the Scheduler Event window. Note that the event primary participant cannot be changed within the Scheduler Event window. To change the primary participant, move the event in the main FrontLine Scheduler window.

- This is a preliminary test version of the Scheduler.
There is a new List for Scheduled Event Categories that should be populated.
If they are not already, Agents should be categorized for improved scheduler use.
There is a new security context for Scheduler to permit access to the scheduler. Security details have not yet been implemented.
The Db Console contains entry Scheduler (6.3) to add two new scheduler tables to the database.
If these tables are not created, FrontLine will work as usual, but without the scheduler. If an installation is not licensed to use the scheduler then do not create these tables.
Also note that the Company Setting for Scheduler Options - Scheduler Connecting Method should be Use Internal Scheduler to enable the built-in scheduler.

- Fixed: Assign a customer to a blank order, then redirect the billing by typing into the bill-to section and confirm the redirection. FrontLine would assign an OrderID despite the absence of line items, thus creating a blank order.

- Fixed: When RAs were shipped, FrontLine would mark the shipment record with the order customer number instead of the repair vendor number to whom the items were shipped. This ship-to address was correct anyway.

- Fixed: In the package model option selector, deselecting an optional subpackage with unfulfilled requirements within it would open the subpackage instead of simply excluding it.

- Fixed: Item substitutes are now used on customer orders when the line item is created by starting with the Item Lookup function.

- Added a

symbol to rental line items in the order entry window. Note that the return and quote symbols, if present, deliberately overlap the Rent symbol.

- The ShipDate, ShippedTo, and ShippedToName fields introduced in 6.2.016 are now available on all Forms for Orders.

- Added an optional Web Site field for addresses. When filled, FrontLine can open the web site using the user's default browser:

- Fixed: With a large purchasing history, PostgreSQL databases made FrontLine hang upon invoking purchasing auto-gen.

- Fixed: Upon replacing an address, the replacement address did not get the identfier document of the replaced address. They now share the identifier document.

- Fixed: When a new purchase order for an alternate location was created by auto-gen, the line locations were correct but the header location and ship-to would be the workstation location. This bug was introduced in an earlier 6.2 revision.

- Fixed: Retrieving a large order lookup result that gave the All option, then filtering the result, then changing the Address used, would lose the All option.

- Added these fields to Forms for Orders for Invoices, Receipts, Delivery Tickets, etc, but not order acknowledgements or quotes:

- Default email recipients for Forms for Orders will include the email address on the address record if there is no contact email address assigned.

- Fixed: When a set eligible item was sold to a customer with no equipment sets, an error "Failed to get object at index 0" would interrupt the flow and cause the addition of an extraneous equipment set.

- Fixed: Rental returns using the order Returns window could be returned to a non-rental location when the Return Lines to Original Location option was off and workstation location was a non-rental location.

- Addresses can now be retired without a replacement using the Retire Address action on the context menu of the address list in maintenance windows.

- Fixed: Quantities posted from a Physical Count sheet to an Adjustment were rounded to 2 decimal places. Aside from the potential inaccuracy, this could also raise SQL errors when an excessive quantity was adjusted out as a result.

- Rented units can now be shipped in Shipping when the new Include Rented Units option is used.

- Units shipped to depot for repair in Shipping no longer trigger invoicing an order for express repair customers.

- Fixed: Sorting the Physical Count sheet by clicking a column header had stopped using Stock number as the secondary sort key.

- Added Report List Filters to the Reports window. The two filters, which can be used independently or together, are:

- Fixed: Item Performance in purchasing auto-gen did not subtract purchase returns to vendor, and omitted some purchasing statistics.

- Fixed: FrontLine user count licensing is now functional. All active logins are counted against the license, except for system administrator who cannot create orders or new line items anymore. If the license count is depleted when a user logs in then they cannot enter FrontLine but have an option to see who is logged in under that license. The License Count Key in Company Setup is now hidden. After logging in with a new license key, the activated count can be confirmed by clicking the copyright text in the Welcome window while holding down a Ctrl key.

- Undone from 6.2.009: Shipping charge line items are created pending instead of on hold.

- Fixed: Selecting the Location filter in Order Lookup did not provide a list of locations to select from.

- Fixed: Retired addresses were still showing on lookups when the Search By field was not an address field.

- Added an Include Closed filter alongside the Include Retired filter in lookups for Agents, Customers, Locations, and Vendors.

- Added a simple row count hint to Equipment Search when pointing at the populated grid.

- Shipped units that are not yet invoiced are now considered inventory in Physical Count.

- Added a Company Setting Address Menu Texts along with code to provide custom address selection texts. This setting is about half way down the list, near the Scheduler entry. The custom address selection texts are used in order entry, equipment sets, shipping, etc.

- Fixed: BillTo/ShipTo/PurchaseFrom address drop-down lists on order entry did not show alternate addresses. This bug was introduced in 6.2.008 with the retired addresses feature.

- Fixed: MOL Export did not apply unit of measure (UOM) to the export quantities.

- Item Category Accounts at the line item location are now required during order entry.
Accounts can still be blank, but the Item Category must have an entry for the Location in Setup - Lists.

- Fixed: Units returned using the order Returns window did not unload the ship tracking number from their identifier document.

- Shipping charge line items are now created on hold instead of ready to invoice.

- Added contact [Title] to the drop-down list of contacts for an address on an order.

- Fixed: Looking up an alternate ship-to address for an order using blank search text would show addresses from all customers instead of only the order customer.

- Fixed: If the same address record was used by two locations (example, a rental location with corresponding rental sales) then only one of these two locations would appear on the source and destination selectors of a Transfer order.

- Fixed: Inserted line items on customer orders were not evaluated for special pricing.

- Fixed: Opening an order marked for repricing that contained line items with ItemID NULL would raise an SQL error and leave the user in an error condition in that order.

- Fixed: When demand notes were added by purchasing auto-gen to a PO with existing line items, the notes would be assigned to the wrong purchase line, potentially raising a key violation error.

- Added fields INVSUM.Description and INVSUM.LineNoteSubject to Periodic Invoices output.
INVSUM.Desc1 now contains only the first available item description line.
INVSUM.Description can contain either an item description line or a line item note subject:
For miscellanous line items preference is given to the note subject, while for non-miscellanous preference is given to the item description.

- If entered, the Item Cost for a customer special order line from Resource Costs is now used by:

- Added an Address Replacement and retire feature. Upon saving an address change, an Address Replacement prompt appears:

Address Correction simply updates the address as it did before.
Address Replacement retires the old address, creates a new address, and provides options to change the address on various records.
Retired addresses can be shown in maintenance windows using the Include Retired toggle in the context menu under Filter Addresses, or the checkbox in lookup windows. Retired addresses have a voided circle icon in the first column.
The Db Console contains entry Address ReplaceBy (6.2.008) to add a required field to the database.

- Widened address State fields to accommodate Australian states.
The Db Console contains entry Widen State (6.2.008) to widen the fields in the database.

- Fixed: When a customer's equipment sets were first opened from an order line with a unit in an equipment set, the Residence address list could again be incomplete.

- Fixed: Auto-commit upon unvoiding a line item put a zero location on the commit event.

- Added a

symbol to the Identifier column in the Customer Equipment list in Service Contracts for a quick visual distinction between rented equipment and equipment owned by the customer.

- Voided line items are now included in order repricing, however their quantities are not used to qualify for a price level.

- Fixed: While 6.2.004 allowed an exchange to be associated with a repair unit line, the exchange out line was not grouped with the repair unit line in the output of Forms for Orders.

- Fixed: The address list for Residence in Equipment Sets was incomplete again.

- To allow rental of ready-made assemblies, turning on the Recurring Rental Item Type in Items maintenance no longer turns off the Package Item Type, but FrontLine requires the Assemble Item Status to save a Recurring Rental Package. Assemblies (Work Orders) cannot be assembled in rental locations.

- Added a Rental Sale Location flag for locations. A Rental Sale Location is secured with Rental Locations but performs the transactions of non-rental locations.

- Fixed: Physical Count would miss some inventory quantities. This bug was introduced in 6.2.002

- Fixed: Upon saving an address, FrontLine could incorrectly claim that the Tax GeoCode is not listed for this address. This bug was introduced in 6.1.087

- Fixed: Recurring Billing did not advance the LastBill date on equipment lines introduced in 6.2.001

- Added date/time fields LaborStart and LaborEnd to Resource Costs. Between these two fields and the Labor (Hours) field, if two are entered and the third blank then FrontLine calculates the third value.
The Db Console contains entry Resource Costs Labor Start/End (6.2.004) to add these fields to the database.

- Implemented Location flags Tax On Location GeoCode and Ignore Item Default Location. Refer to the Location Status flag codes.

- Added to User Options: No new line item prep on open orders. This suppresses FrontLine's actions to prepare for entry of a new line item on open orders.

- Fixed: When multiple purchases, some open and some completed, had been made to fulfill one open special customer order line, the residual demand could produce duplicate purchase suggestions in Generate Purchase Order which would raise a primary key violation when added to a PO.

- Fixed: Order Totals did not include the package line item in Costed New Sales because packages do not carry a cost in themself. However, in Package First mode the package carries the sale value, so the results were skewed with packages on the order.

- Added a sticky Cost Used selector to the Order Totals window to choose between Standard, Last, and Average cost for margin calculations.

- Implemented Distinct Location Costs vs Blend Location Costs in Company Setting Discounts, Repricing, Cost Loc for Discount Presentation, Quantity Repricing, Cost Pricing:
Company Settings

And, Price Levels now have an optional Location distinction, where =ANY= can be specified for prices not specific to a location.
Connector note: =ANY= location corresponds to PRICELEVELS.LocationID = 0
Together these revisions provide more flexibility for pricing by location. Some rules about how FrontLine determines a price are:

- The Purchase from Primary Vendor Only option in Generate Purchase Order is now sticky.

- Added an export function for the purchasing suggestions in Generate Purchase Order.

The Db Console contains entry PRICELEVELS Location (6.2.002) for a required update.
Note that this script has to be executed one line at a time for both server types.

- Fixed: The Rollback Billing Dates action after returning a recurring bill did not release meter readings used on that bill.

- Added a LastBill field to equipment set members to record the last billed date individually per member. This enables two enhancements:

The Db Console contains entry ESDTL.LastBill (6.2.001) for an update required by recurring billing revisions.
Note that the MSSQL script has to be executed one line at a time. The PostgreSQL script can be executed in one go.

- Fixed: Special order line items without a scheduled date did not show up in Generate Purchase Order due to a bug related to future orders.

- Added a

icon to the Quantity column in Equipment Sets for a quick visual distinction between rented equipment and equipment owned by the customer.

- Direct entries of Initiated and Terminated dates on equipment set members now affect pro rata on the open order.

- Rentals need start (Initiated) and end (Terminated) dates to calculate fees. Changing a rental line item's Scheduled date changes the Initiated or Terminated (for returns) date on the equipment set member. The defaults are:

- Added a special customer order lookup Service Orders w/Services not Ready to find service orders with services not marked as ready/performed.

- Transaction Inquiry enters a Large Result Data Set mode if the date and order type criteria produce more than 10,000 rows of results.

- Rented units can now be repaired on service orders. Note that the location of the rental unit repair remains the rental location. Parts and services used for the repair can be from other locations, and will default to the order location or item default location as usual.

- Implemented a Case property for identifiers in Identifier Setup to convert identifier text typed in to upper case where needed.

The Db Console contains entry File: NewInvoice procedure 6.2 for a required update to complement repairs of rentals.

- The Web Order order type flag can now be toggled on customer orders using the drop-down menu beside the POS button on the top bar. The display text can be changed using the WebOrder Labels dictionary word.

- Added a Primary Identifiers Only option to Transaction Inquiry to show only one identifier per unit in the Details.

- Fixed: The ending quantity on hand calculated by Inventory Transactions did not include inventory committed to consume for assembly or to adjust out.

- Added more validation of US Zip codes and Canadian Postal codes and Tax Geocodes.

- Added three custom Item Status flags that can be set in Items maintenance. If any of the three flags with values 1000, 2000, or 4000 (in hexadecimal) are given a display text in Lists maintenance, FrontLine creates checkboxes for them in Items maintenance, enlarging the Item Status section as needed. Note that these flags do not influence FrontLine's behaviour with Items, but can be used for reporting, external data connectors, etc.

- Rental Returns now set the new line location to the rental origin if the order location is not a rental location.

- Fixed: Unknown Item message that could occur in order entry despite a valid scan code.

- Fixed: Selecting the first listed vendor as primary vendor or repair vendor in Items maintenance would raise a FK_ITEMS_VENDORS violation error upon saving.

- Fixed: Adding new intangible line items to a quote created equipment set members, and when that quote was turned into a new order the new set elibible services were not automatically added to equipment sets.

- Fixed: Presented Quote totals included Taxes. This fix is implemented in the NewInvoice database procedure.

- Canadian tax geocodes are now listed by single character match of postal code instead of 2-character match when the full postal code is not found in TaxGeoCode localities.

- Line status Discounted is now copied to return line items created in the Returns window.

- The letters in Canadian postal codes are now forced to upper case for consistency.

- Quotes are now excluded from special lookups Open Sales Orders and Sales Orders for Invoicing.

- Added a Scheduler Options window to add more settings to the Scheduler configuration in Company Settings, and implemented a new scheduler option to send an order bill-to vs ship-to address to the scheduler event text.

The Db Console contains an entry File: NewInvoice procedure 6.1.086 to implement the fix for quote presentation tax totals.

- Added a Print Lines with Zero Quantity option for invoice-related output in Forms for Orders.

- Implemented the global Discount percentage for customers. This discount is applied on top of the price a customer qualifies for by price level, etc, except if that price is a customer-specific price entry indicating an individually negotiated price.

- Pressing F3 while in the Agent field of Customers maintenance now invokes Agent lookup.

- Fixed: Changing the price of a return line item created by order returns would result in miscalculation of that return line item's taxes.

- Fixed: Exporting text fields containing the selected quote characters could cause issues for programs interpreting the export file. FrontLine now doubles the quote characters found within field text values.

- Added a direct link to Item Quantities from line items, using the context menu or shortcut key Ctrl-3

- Items maintenance is now also shown on the line item context menu, complementing the longstanding shortcut Alt-F2

- Counter discounts entered directly on return lines are not separated regardless of company settings.

- The Item Quantities window now floats alongside the Items maintenance and Item Lookup windows.

- Added a Company Setting under Returns, Repairs, Unidentified to choose the Item Action prompt function text Repair vs Service

- Links in the Maintenance and Inquiry groups of the Welcome window now rearrange to collect all disabled functions at the bottom.

- Fixed: FrontLine would not fulfill the remainder of a partially fulfilled line item with Unidentified.

- Fixed: In Shipping, Vendor RA units were bundled to their repair vendor instead of to the V-RA vendor.

- Fixed: FrontLine could not save Current Station setup when run directly on some 64-bit Windows 7 workstations. These settings are now saved in the "current user" registry on Windows 7 and Vista, as they already are on any terminal server.

- Added Address to Equipment Search inquiry. This field only appears when the window width is greater than 1,200 pixels.

- Added Bin to Item Lookup. The bin at the workstation location is shown, or the default item bin if there is no location-specific bin.

- Added seven more custom Order Status codes. These show up in the drop-down on orders when they have non-blank entries set up in Lists, and are handled by the code translator.

- Added a select prior (up arrow) / next (down arrow) feature to maintenance windows. Pressing the up/down arrow keys in the human key field triggers it. Note that there is no such thing as prior/next in an SQL table, so this function has to search the field, and searching large tables is not instantaneous. Implementations are:

- In the Item Action prompt, changed the button text Repair to Service. Notice that the hot key remains unchanged.

- Added SIC to customer and customer order lookups as both a display column and a Search By field.

- Ship tracking number identifiers are now only included in the output of Forms for Orders for shipped units.

- Added a Match first n option for bin selection in Physical Count to match bins using only leading characters.

- Holding down a Shift key while first opening a function window, or logging out of FrontLine, no longer inhibits user level persistence.

- Added a Purchase Freight ID to Company Settings separate from Shipping Charge ID:

The Db Console contains an entry File: CostInvoice v6.1.082 for landed costing to use Purchase Freight ID instead of Shipping Charge ID.

- Added a confirmation before sending email from Periodic Invoices or Recurring Billing Output.

- An Item's Default Location is no longer considered when the Order Location is a Rental location and inventory is not identified.

- Added a Receiving Landed option to the company setting for Costing Received Goods. Landed costing has some prerequisites:

The Db Console contains entries ITEMCOST.StdCost,LastUnlanded (6.1.081) and File: CostInvoice v6.1.081 for required database updates.
Apply the update to ITEMCOST before the CostInvoice revision.

- Added an Any Item option to the Item Billing Prices window to change prices of equipment set members based only on current price and billing frequency. Note that to enter this window it is still necessary to view a recurring billing item in Items maintenance then right-click on the ellipsis button next to list price.

- Fixed: Overriding a line item price back to list price after applying a counter discount would appear to remove the counter discount but not remove it from the database.

- Fixed: Rerunning the same Report SQL query for a non-visual report again would raise an error about missing parameters.

- Fixed: Exporting a Physical Count sheet excluding the unit fields would result in a dataset not open error.

- Added an ExtCost column to the Costing grid in the Check In/Out (Invoice) window, and clicking on the column header display the sum.

- Added a drop-down menu to the Service button for Service Orders with functions All To Depot and None To Depot to flag or unflag all unshipped committed to repair units on the order for depot repair.

- Vendor RAs (V-RAs) can now be shipped. They are included in the Ship RAs listing in Shipping. Shipping charges are added to V-RAs but without any markup.

- Added a F3 lookup feature for changing the Ship To address directly in Shipping.

- Added an optional company title display text. To set it, add a last line to the INI file like this:
CO="My Company Title"

- Fixed: Potential for an access violation and line number overruns when posting long Physical Count sheets to Adjustments.

- FrontLine no longer sets the Scheduled date of a line item when the line is created.

- Order Notes can now be opened read-only when the order itself is opened read-only. Previously, if the order was open read-only then order notes could not be opened.

- Added Inventory Transactions and Transaction Inquiry to the line item context menu on orders. Both the customer and item context are used for Transaction Inquiry.

- Moved the Inventory Transactions and Transaction Inquiry menu in Items maintenance to the Parts button, and added these inquiry functions similarly to Customers maintenance.

- Fixed: Committing a Physical Count sheet (posting it to an Adjustment) could result in a foreign key violation.

- Widened the user return email address field to 80 characters. Part of this revision is in the database.
The Db Console contains an entry Widen User Return Email (6.1.076) to implement the database part.

- Implemented a Company Setting under Returns, Repairs, Unidentified to Repair Units in Order Location vs Repair Units in Last Known Location.

- Added an icon to the Part column in purchasing auto-gen to indicate the presence of Resource Costs associated with the special order, and a context menu entry Special Vendor Resource to open the entry.

- Added a Scheduled column to the output of Transaction Inquiry. The value output is from the line item, or if blank on the line item then the order.

- Added a link to Inventory Transactions from Physical Count in the context menu.

- Added to the output of Forms for Orders fields ItemNoteSubject and ItemNote.

- Fixed: Access violation potential in Customer Lookup if Address Preferences were added, assigned to addresses, then removed from the preference list.

- Added an Urgent line item status, accessible in the context menu. The exclamation mark appears next to the Special order icon on both line items and in generating purchase orders.

- Fixed: This Physical Count fix in 6.1.071 should now be implemented correctly.

- Fixed: In Physical Count, when Bin criteria was included it searched both the location-specific bin and general bin. Now if a location-specific bin exists the general bin is not considered to qualify the item.

- It is now possible to open Inventory Transactions and Transaction Inquiry directly from Items maintenance using the drop-down next to the Quantities function.

- Added a company setting to enable Demand Snapshot notes under Notify Options.

- Added a means of cancelling a shipment: Enter or scan the tracking number (ShipRef) in the Destination of the Shipping window and, if there are any units shipped with that tracking number still committed FrontLine will display some information about the shipment and, if the user has Delete permission for Shipping, allow the user to cancel the shipment. Cancelling a shipment removes the shipped status and tracking number from the units, and voids the open shipping charge if there is one.

- Fixed: The service order counts on Score Card would overcount when multiple repair units were on each order.

- LocationID is now translated for Recurring Billing Output forms as it is for other forms.

- Shipped Committed for sale inventory is now shown in the Quantity per Location and Status list for a location in Item Quantities.

- Added Demand Snapshot notes to purchasing line items created by auto-gen that are not special orders.

- Fixed: A revision to the check out commit procedure in 6.1.064 broke the creation of new unit warranties for sales on MSSQL only. This fix is implemented in the database procedure CommitInvoice.

- Fixed: Returns to inventory of customer units last repaired at depot. Part of this fix is in the database procedure CopyLineItems.

- Fixed: Posting a Physical Count worksheet with unidentified quantities would result in additional inventory adjusting in equivalent to the unidentified quantity per such item.

The Db Console contains entries File: CommitInvoice v6.1.071 to implement the first fix above (MSSQL)
and File: CopyLineItems v6.1.071 to complement the second fix above.

- Fixed: Access violation after selecting a vendor from vendor lookup invoked from Items maintenance to select the item's primary vendor.

- Removed the on hand quantity re-evaluation when counts are entered in Physical Count for further refinement.

- Added a function in Shipping to ship all units on the current line item. Use the context menu or F12

- Fixed: Inventory Valuation included unidentified repairs in unidentified sales.

- Fixed: Assemblies on Work Orders would lose total cost synchronization with their components due to rounding timing when the quantity was changed by user.

- Fixed: When a sale line item had no inventory committed to it, and had a location different from the order location, the Scan Match window Location filter was given the order location instead of the line location, potentially confusing the user about availability of inventory at the line location.

- Little improvements in the Item Quantities window including ability to double-click an available quantity in the Quantity per Location and Status tab to show the Inventory and Committed for that location.

The Db Console contains an entry File: SpawnItemDtl 6.1 to implement a revision that creates a new identifier document for return and repair events when the unit already has a ship tracking number so prior ship tracking numbers in history are not in the present event.

- Fixed: Check In of Assemblies on Work Orders - this fix is now implemented for PostgreSQL, and enhanced for MSSQL over the 6.1.064 fix in the commit phase. See the db update note below.

- Added a security context for Periodic Invoices separate from Recurring Billing.

- The Report function in Inventory Valuation now uses a different form InventoryValuationSU.rep when Subtract Unidentified is turned on. This alternate form should use the INV.QtyUnidentified value to adjust quantities and values accordingly.

The Db Console contains entries File: NewInvoice procedure 6.1.068 and File: CommitInvoice v6.1.068 to implement the fixes for work order assemblies check in.

- In Company Settings, elaborated Order Entity Reactions into Order Activity Reactions where there are now options for Item Note Popups. At this time, Item Note Popups do not occur for package members

- In Physical Count, the Include Never On Hand Items option is now disabled unless the Include Zero Quantities option is selected.

- Added an OrderScheduled field to Forms for Orders for Pick Tickets, Invoices, etc. Previously it was only available for Sales Orders, Purchase Order, Quotes, etc.

- In Transaction Inquiry added [F3] lookup to the hints on Stock and Customer criteria, added field EntityOrder to the main result set, and fixed an issue where columns on the far right moved to the left did not remember that new position after logoff. This revision may also fix a column persistence issue in order lookup.

- Fixed: The Stock number shown in the Identifier Document window did not always update when a new identifier document was opened.

- Added an Add item function to Physical Count, to add a particular stock item to the list. Note that adding an item this way does not change the original criteria, so looking back at the list one might wonder how this item became part of the count.

- In Company Settings, elaborated Order After Entity into Order Activity Reactions options, adding a Item Note Popups group of checkboxesfor: Customer Orders, Purchase Orders, and Work Orders. Implemented corresponding pop ups of Item Notes during order processing.

- Implemented Multiple Recipient EMail of reports from the preview window using the eMail sections per recipient unattended function from the Mail drop-down menu. For this function to work the first dataset in the report must contain a MailTo field. The report is broken into multiple PDF files, with the recipient's email address inserted into the file name. It is best to place these PDF files in an empty folder created for the mailing batch. FrontLine does not delete these files after sending them.

- FrontLine now detects and skips the 3-byte UTF-8 BOM (Byte-Order Mark) EF BB BF when reading script files from disk into the Db Console.

- Fixed: Check In of Assemblies on Work Orders did not level out quantities of the components and the assembly itself to the lowest committed level. This fix is contained entirely in the database procedures NewInvoice and CommitInvoice. See the db update note below.

- FedEx Ship Manager main window did not bring itself to the foreground when activated for shipping integration. FrontLine now takes additional steps to make this happen.

- Added Entity, BillTo, and ShipTo trailer notes to the output from Batch Picking.

- Item Notes are now exposed in the Generate Purchase Order window: The Stock column contains a note icon when the item has notes. Added a Notes F7 function to the context menu to open the note, with the note subject shown in the context menu.

- FrontLine now includes a Backordered and Shipped status when relevant in WEBUPDATES records created for Order Status changes, and WEBUPDATES records are no longer created for Order Status changes if there are already records indicating a shipment with a ShipRef.

- Imported line items due for repricing that include the ZeroPrice flag 32,768 in TrxType will be repriced at zero instead of the customer price.

The Db Console contains entries File: NewInvoice procedure 6.1.064 and File: CommitInvoice v6.1.064 to implement the fix for work order assemblies check in.

- Fixed: Under some circumstances it was possible to enter a duplicate unique identifier in Receiving.

- It is now possible to edit external invoice numbers and dates of the Costing records in the check-in/out window if the user has Modify permission for the new security contexts AP Invoice Number and AP Invoice Date found in the Purchase Orders class.

- Fixed: 6.1.060 and 6.1.061 would produce and access violation upon using the Print function in Batch Picking.

- Orders can be opened for editing from the Inventory and Committed list in the Item Quantities window when the OrderID is shown in the context menu, which occurs when the unit is committed for sale or rent.

- Elaborated the Company Setting Quote Life into a Quote Options window with a new option Reset Placed date when Quote is toggled off.

- Elaborated the Company Setting Notify Before Activations into a Notify Options window with a new option Remind user to document Out of Service events to make the out of service reminder configurable.

- When an equipment set member is transferred from one set to another, FrontLine now copies it's residence to the event address [ITEMDTL.AddressID]

- Fixed: Negative priced or costed line items can now be overridden to a more negative value as well as towards zero.

- Fixed: Line Location was not changed to the Inventory Location when using the Scan Code entry method in Line Item Details to commit inventory.

- Fixed: Inventory Valuation now includes quantities committed to adjust out or consume for an assembly in the On Hand total.

- Fixed: Using Company Setting Known Units to Origin in Return and Unidentified Options would take precedence over the Exchange option Return incoming unit to location of outgoing unit with a possible result of the incoming unit event location not matching the line item location.

- Fixed: Inventory transferred by auto-commit ended up at its source location instead of destination.

- Improved handling of IIF conditional text expressions using TrxType and TrxStatus code fields from Forms for Orders.

- Added two location options to Inventory Valuation: <All Rentals> and <All Non-Rentals>

- Changed the suggested purchase quantity in Generate Purchase Order to cover all potential needs (including open customer orders) and replenish inventory to Max.

- Added Vendor RAs to Purchasing. To start a Vendor RA, press Ctrl-R or click the drop-down arrow next to the Transfer button and choose V-RA.

- Fixed: ShipTo addresses on orders with redirected billing were not skipped when more than 40 as the 6.1.041 revision did for regular orders.

- Fixed: Exchanging two different stock items would result in the same Scan Code displayed on both lines instead of the two distinct stock numbers. This problem began in 6.1.056

- Added an context menu to the Identifier Document window with functions to Open Resource and Ship Tracking when applicable.

- Added a Ship Tracking function to the unit context menu in Line Item Details.

- Added event notes to the Unit Tracking window. The note subject or leading text of the note is shown in the event text, and the Notes F7 function opens the note in full for reading.

- Added a Quantity column to the Inventory and Committed view in Item Quantities, and now include quantities committed for sale in the Quantity per Location and Status view even when the Show Sold Quantities option is off.

- Revised the ORDERS.OrderType field data type from smallint to int.
The Db Console contains an entry ORDERS.OrderType int (6.1.059) make this change in the database.
There is also a trigger revision TR_ItemDtl_QtyCheck v6.1 (MSSQL) that applies only to Microsoft SQL Server.

- Fixed: Two line items on a customer order of the same stock item, location, and quantity were analyzed as the same line for quantities to generate a purchase order.

- Added an On Order floating view to the Generate Purchase Order feature to show purchase orders where an item has been ordered but not yet received.

- Fixed: Creating a Periodic Invoices batch with a Customer Number Pattern would result in an SQL error about an ambiguous column name after the 6.1.045 database update to the INVOICES table.

- Fixed: Periodic Invoices would output lines to the detail section that were on invoices prior to the relevant invoice.

- The Sales Order output from Forms for Orders is like a Pick Ticket when operating with Red Deer's activation key.
This modification is active when there is a blue tint on the Sales Order form selector button.

- Fixed: Receiving in Scan mode after receiving in range mode would add characters to the identifier value scanned.

- Fixed: Adjustments got ShipTo addresses upon reopening, and their location would change to the ShipTo assigned. This was probably broken in the last month or two.

- Fixed: Recurring Billing did not exclude equipment set members that were still committed for sale/rent.

- The purchase quantity suggested in the Generate Purchase Order feature now tops up inventory to the Max if a max is defined.

- In the Price Levels window, when a number typed in for Entity matches both a CustomerID and CustomerNumber, FrontLine now consistently chooses the match on CustomerNumber.

- The Item Quantities window layout has been revised, and a Show Sold Quantities filter added.

- Fixed: The address list for Residence in Equipment Sets was incomplete. This was broken in 6.1.041

- Added a Proprietary Item Status (flag value 2048), visible in Items maintenance, and available as a sticky criteria in Inventory Valuation.

- Shipping now considers Bill Transportation To for whether to charge for the shipment. Shipping is charged when transportation is billed to the Sender/Shipper, but not when billed to Receiver, Third Party, or Collect. This revision goes with changes in the shipping integration details for WorldShip and Ship Manager.

- Fixed: FrontLine could not tolerate line items with NULL ItemID other than order discounts and payments on account.

- Added a Use Order Scheduled date where set sticky option to Batch Picking.

- Elaborated Company Setting Discount Presentation to Discount Lines & Repricing to add an option No Quantity Reprice for Repricing after Quantity change.

- FrontLine can now input the ShipID key itself in WorldShip and Ship Manager through window messages and attempt to make them open the shipment.

- Recruited the field ADDRESSES.NotifyVia to flag Residential addresses for by the Ship Manager and WorldShip integrations. There is now a Residential checkbox in address maintenance.

- Added a field CUSTOMERS.ShipAccount for use by the Ship Manager and WorldShip integrations. Customer maintenance has been tweaked to accomodate.
The Db Console contains an entry CUSTOMERS.ShipAccount (New in 6.1.054) to add a required field.

- Added a Parts view option to purchase order line items to show the vendor part number vs stock number.

- When a Pick Ticket is produced interactively for an order from Forms for Orders the order status is now flagged as Picking.

- When authorize.net returns code 4 to Hold for Review FrontLine now gives the user a choice to accept the payment.

- Fixed: Although FrontLine detected and notified the user of circular references during package setup, if a circular reference was created in the data by other means it caused a hang when FrontLine attempted to display the package selector.

- Fixed: Assembly components with fractional cent costs could cause a rounding mismatch for the assembly cost on work orders, leading to $0.01 order totals.

- Fixed: The Discount security contexts (which affect a user's ability to change line item prices) from Customer Orders were applied in Purchase Orders.

- Fixed: The effect of inventory Minimums on purchase quantity suggestions from the Generate Purchase Order feature.

- Fixed: In the Generate Purchase Order feature, when viewing suggestions for multiple vendors, a purchase quantity override entered using the Enter/Return key was lost.

- Fixed: An item's Default Location is only applicable to customer orders, not purchase orders.

- Fixed: Changing the Ship-To on a regular purchase order did not change the order location.

- Added a Purchase from Primary Vendor Only option to the Generate Purchase Order feature.

- Implemented posting of Shipping Charges to Customer Orders. The customer order must be in an open status. If the user has the order open in the background, that presentation is deferred for manipulation of the order by shipping. Note that shipment charges are retrieved from Ship Manager and WorldShip, but these are presented to the user for confirmation in case the recipient has their own shipping carrier account and thus should not be charged in FrontLine.

- Fixed: The automatic invoicing of express repairs customer orders in Shipping could overwrite the TotalPaid value of all orders in the database.

- Fixed: Shipping units that had been shipped before would overwrite their prior shipping reference (tracking number) or cause a key violation.

- Fixed: Line items with the Surplus flag could not be manually fulfilled as inventory.

- Fixed: In some circumstances, the line effective total did not reflect the customer's discounted price when the line item was entered.

- Added a BackOrders field to the output of Forms for Orders to indicate the customer's backorder preference on forms.

- Added an Order Type flag for Web Orders, value 0x2000 (hexadecimal) or 8192. This flag serves as an alternate trigger for web updates.

- Added to Company Settings: Shipping Charge ID and Shipping Charge %
To enable automatic addition of shipping charges returned by Ship Manager and WorldShip to customer orders the Shipping Charge ItemID must be set, and the Shipping Charge percentage greater than zero. Use the ItemID of an intangible (the ellipsis provides an Item Lookup), such as a Charge or Service, that is not set eligible.
Automatic addition of shipping charges to an order was not ready until 6.1.051

- Fixed: The No Package Prompt Item Status broke the sale of ready-made assemblies.

- Fixed: When the same unit appeared more than once on the same order, it's identifiers were repeated in the output of Forms for Orders.

- Added a Print intangible line items option to Forms for Orders for Pick Tickets, Delivery Tickets, Ship Tickets, and Edit Lists.

The Db Console contains an entry File: ImportItemDtl procedure 6.1 which uses script files ImportItemDtl61.sql (MSSQL) or pgImportItemDtl61.sql (PostgreSQL) retrieved directly from the web site.
FrontLine does not use this procedure directly, instead it is used by the back office connector.

- Fixed: Starting a rental line item from Item Lookup could result in rental inventory not appearing in Scan Match until after the line item was created.

- Implemented some security detail for setup Labels and Lists so that a user can have read-only access.

- Added a Show Age option to Order Lookup windows so the user can choose to see the age of open orders (or time from placement to completion for closed orders) as before.

- Added to User Options: F8 Defers Orders. This makes FrontLine defer open orders when the user presses the F8 key instead of checking through the order. On an open order, this option effectively moves the F8 shortcut from Check-Out/In to Defer.

- Fixed: Changing the recurring price of a service contract in the Service Contracts window did not prorate the line item price on the open order.

- The Customer Lookup invoked by typing into a Ship-To address field on an order now only shows addresses for the current ship-to customer of the order.

- Fixed: After redirecting the bill-to of a customer order, the ship-to contact (if defined) would display Unknown.

- Fixed: After redirecting the bill-to of a customer order, then restoring the bill-to back to the ship-to customer, the prior redirected bill-to's EntityID could remain on the order.

- Fixed: Parts and package members used for repairs were not held back from Shipping when the repair unit itself was not ready to ship.

- Fixed: The Item Action prompt count of # days ago was off by a day in many cases.

- Fixed: Changing the xTo Address selector in Order Lookup while viewing a special lookup such as Open Service Orders did not refresh the results displayed.

- Fixed: Assembly Packages marked No Package Prompt could not be placed on Work Orders. FrontLine now ignores the No Package Prompt flag in this scenario.

- In Items maintenance, the Primary Vendor and Repair Vendor fields now have drop-down selection lists and auto-complete from text typed in.

- Required identifiers missing from an order's I.Doc no longer prevent printing of Forms for Orders for a closed order.

- Fixed: Recurring Bill line items were missing the recurring bill flag. This bug was introduced some time this year. One consequence is that these line items are not counted in the Contract Profitability Report.
Check for affected line items with this SQL:
SELECT * FROM TRX WHERE OrderID BETWEEN 80000000 AND 89999999 AND TrxType&4=0 AND OrderLineRef IS NOT NULL
Fix affected line items with this SQL:
UPDATE TRX SET TrxType=TrxType|4 WHERE OrderID BETWEEN 80000000 AND 89999999 AND TrxType&4=0 AND OrderLineRef IS NOT NULL

- Fixed: Two step line item reference links were not considered in order check-out. This fix is one of the two revisions in the NewInvoice database procedure.

- Added a Search By Part Reference option to Item Lookup. All vendor and customer part numbers are searched. Note that the vendor/customer part numbers are not displayed in the lookup results.

- The Location selector in the Generate Purchase Order function now allows free-form entry.

- Added a Print non-repair lines first persistent option to Forms for Orders when the output is from a service order, and made sorting of Invoices and Receipts consistent with Service Orders.

- Added an Applied to nnn- n context menu function to the payment tenders of an order. The nnn- n indicates the order and invoice sequence (if applied) and the function opens the relevant invoice (check-out) for viewing.

- Added BillTo information to the INVOICES table, affecting Forms for Orders and periodic invoices. The Bill-To address of an open but partially invoiced customer order can now be changed so the next invoice goes to a different party.
The Db Console contains entries File: NewInvoice procedure 6.1.045 which uses script files NewInvoice61045.sql (MSSQL) or pgNewInvoice61045.sql (PostgreSQL) which are retrieved directly from the web site, and INVOICES.BillTo+EntityID (New in 6.1.045) which is an embedded script.
Execute the INVOICES.BillTo+EntityID script before updating the NewInvoice procedure.

- Fixed: The Generate Purchase Order function omitted demands from open line items where the committed quantity partially fulfilled the order.

- Fixed: FrontLine did not prompt for Item Action of an unidentified non-identifiable inventory item with a default location.

- Fixed: Pick Tickets, Delivery Tickets, Ship Tickets, and Edit Lists were including intangibles from a revision in 5.6

- An open Work Order can now output a Pick Ticket. Work Orders are not included in Batch Picking.

- Users with appropriate permission can now override exceeding a customer's credit limit even when the customer is already over their credit limit. See the initial implementation notes.

- Fixed: The last known unit address for order ShipTo introduced in 6.1.038 did not work for returns.

- Added a persistent Exchange option to return the incoming unit to the location of outgoing unit. When this option is off, the incoming unit is returned to the order location.

- Fixed: More issues in the Demands list for the Generate Purchase Order window.

- Fixed: Attaching parts and services to a warrantied repair unit after return from depot did not cover those parts and services under the warranty.

- Bill-To and Ship-To addresses are no longer listed in popup menus on customer orders if there are more than 40 of them on the list. Instead an entry Lookup address... appears.

- Bill-To and Ship-To address lists in the Equipment Sets window are now built when Equipment Sets are first opened for the customer. This saves time when assigning a customer with hundreds or thousands of addresses to an order.

- Added Copy & Paste functions to Contacts maintenance. Paste is performed with the same button/shortcut as Copy, but on a new contact record.

- Implemented a meaning for the Repair Vendor of a Service or Charge: When a service or charge with a repair vendor is added to a service order (a customer order with units to be repaired) that vendor's addresses are matched to customer addresses, and if a customer matches then that customer's default bill-to is assigned to the service order with user confirmation. Note that the addresses are matched by AddressID so, for example, the customer needs to have one of the vendor's addresses added to its list using the Other Address... function in maintenance.

- Fixed: The Orders function from Unit Tracking opened over the Scan Match window failed to open the relevant order in the background window.

- Fixed: Starting in 6.1.036, voided line items could show up on invoices.
The Db Console contains an entry File: NewInvoice procedure 6.1.041 to fix the NewInvoice database procedure bug introduced in 6.1.036.
This entry uses script files NewInvoice61041.sql (MSSQL) or pgNewInvoice61041.sql (PostgreSQL) which are retrieved directly from the web site.

- Fixed: Quantity analysis of work orders and adjustments used to make auto-gen suggestions in Generate Purchase Order.

- Fixed: Security contexts for Quarantine Release and Certificates did not show up in Access Profiles. They should now show up in the Items group.

- Events (as in the Unit Tracker) for assemblies are now marked as Assembled (instead of Received) and components used are marked as Consumed, for Assembly.

- Added a Scanner mode to the Receive window. In scanner mode identifier ranges are disabled, the identifier input is fully processed in the first step, and focus returns to the identifier input after each scan. Scan mode is available when receiving items that have identifiers, and its activation is persistent for the user after logoff.

- Added the Vendor / Customer name to the awning label in Parts Cross-Reference. This name comes from the Vendor's Default Purchase From address.

- Added Find Stock # function to the line item context menu to help locate a stock number on a long order.

- Added a Get latest FrontLine.exe command to the Db Console context menu. This function does not upgrade FrontLine in place. It simply retrieves FrontLine.exe from the web site for convenience. User is prompted for where to save the file. Database updates should be performed with the latest FrontLine, so after updating FrontLine.exe close FrontLine, launch the new executable and return to the Db Console to run any required scripts.

- Fixed: Physical Count using "Include Zero Quantities" but not "Include Never On Hand Items" did not include items that had been sold unidentified without ever having quantity on hand.

- Fixed: Depot returns made from outside the service order could fail to take the original equipment's place on equipment sets and service contracts.

- Fixed: FrontLine was not preventing check-out of Service Order / I-RA units still at depot when those line items on the order (or the service order itself) were not marked as ready.

- Fixed: When a unit whose most recent transaction was a repair was returned, the return line item had some flags that made it look like another repair.

- Fixed: Voided work order parts line items showed up on the Demands for the Generate Purchase Order window.

- Fixed: Check-In of Purchase Orders should not consider the ready checkboxes, all receivings qualify for check-in.

- Fixed: On customer orders, a unit received back from depot shows the received symbol on the line item but the symbol disappeared after the line completed, causing visual ambiguity between the outgoing and incoming depot RA line items.

- Fixed: Possible SQL error in Shipping after units are shipped but there is nothing to invoice. Example, after shipping RA units.

- Fixed: Persistent sorting introduced in 6.1.038 now puts the cursor back at the top of the resorted grid.

- FrontLine will now attempt to load the File script entries in the Db Console directly from http://www.ormandy.com/r/scripts/ so the files do not have to be manually transferred to client sites.

- Changed the auto-complete full text search (introduced in 6.1.038) trigger from 3 to 4 characters minimum entry.

- Added a context menu on the Shipping list to visually expose some available functions: Orders, Items, Customers, Vendors.

- Shipping directly from an order with units to send to depot now preselects the Ship RAs option.

- Refreshing costs and substitutes... for purchasing should take less time on PostgreSQL now.

- Added to User Options: Focus on Repair Codes that makes the Repair Codes window open immediately when a repair unit is checked in, and also makes this window receive focus when Line Item Details open for a repair unit line.

- Added an Address ID to unit event records. FrontLine uses this value among others to determine the last known address of a unit. Although FrontLine does not set this value yet, some external data connectors do.
The Db Console contains an entry ITEMDTL.AddressID (New in 6.1.039) to add this database field.

- Fixed: Special Orders for Work Order components did not show up in the purchase list suggested by auto-gen in Generate Purchase Order.

- It is now possible to add an item to the purchase suggestion list in Generate Purchase Order using the context menu or F3 which invokes Item Lookup.

- Enhanced auto-complete of fields with a drop-down list of values: If three characters are typed in without a match by leading text then FrontLine performs a full text search of the list values and selects the first match.

- FrontLine will now set the EntityID of EDI line records if the field exists in TRXEDI and no value has been assigned to it.

- Units brought in for repair or return on a blank order will now set the Ship To address of the order to the unit's last known residence or ship-to provided those addresses belong to the customer.

- Added a company setting Web Orders ID to change the default workstation ID of 99 used to recognize OrderIDs generated from web orders. The valid range is between 90 and 999, keeping in mind that 100 to 999 are also valid FrontLine workstation IDs.

- Added a special customer order lookup Shipped, not Invoiced to find orders where inventory has shipped and needs to be invoiced.

- Added a backordered symbol (truck with calendar) to the line number column in Shipping to indicate that part of the line quantity has been marked backordered, or some parts used to repair the unit are marked backordered.

- When a repair unit is scanned as shipped in Shipping, any parts linked to it that are ready to ship are also marked as shipped.

- User defined sorting (by clicking column headers) of the location cost grid in Item Costing and the location bin list in Item Bins is now persistent.

- Added a CustomerPO field to Periodic Invoices. A periodic invoice includes multiple bills and invoices, so FrontLine uses the first customer PO number in the group. This field is output to periodic invoice forms as INVSUM.CustomerPO
The Db Console contains an entry PVIDS.CustomerPO (New in 6.1.038) to add a required database field for this revision.

- Fixed: Price generation code has been reworked for improved consistency between line repricing and new line item entry pricing.

- Fixed: The location of auto-committed units for a new line item came up with an odd number. This bug was introduced in 6.1.031

- Added an Order Status In Transit, and exposed it and the On Hold flag in the drop-down on the order header. The labels can be changed by modifying the Display text of the desired entry in the Order Status list found in Setup -- Lists.

- The Express Repairs shipping feature introduced in 6.1.034 now invoices those service orders. Note that a database procedure update is required:
The Db Console contains an entry File: NewInvoice procedure 6.1 to revise the NewInvoice database procedure. This entry requires script files NewInvoice61.sql (MSSQL) or pgNewInvoice61.sql (PostgreSQL).

- Fixed: Transfers and Adjustments in Rental locations are not rental transactions.

- Fixed: Odd bug in Physical Count that would make a list of identified units appear for the last entry when the cursor is not on the last entry.

- The location cost grid in Item Costing, and the bin list in Item Bins can now be sorted by clicking their column headers.

- The Spreadsheet option in the Export window is now always visible but when it is checked with HTML the output format is changed to comma delimited. Similarly when HTML output format is chosen the Spreadsheet option is turned off.

- Added a Customer Status flag Express Repairs to indicate that a customer's repair units can be shipped without indicating readiness on the service order. The effects of this flag are seen in Shipping where it affects both the units listed to ship, and units shipped that were marked To Repair are changed to Repaired.

- Fixed: Placement of equipment set members was not saved in some circumstances.

- Included non-unit identifiers (ex, Service Contract) in Recurring Billing Output.

- Fixed: When a rental unit was returned using the Returns window, the unit status included the Sold flag where it should be only Returned.

- Fixed: Recurring Billing Output on PostgreSQL would raise an SQL error about conversion of ReadDate. This bug was introduced in 6.1.023 and only occurs when using a PostgreSQL database.

- Added a persistent option "Sort ship list by Order / Line" to Shipping that can be toggled until units are shipped from the list.

- More tweaks and fixes related to EDI integration, including an ability to auto-commit inventory upon opening an EDI order just imported.

- Added a Line Item EDI window to display and allow editing of EDI information from the new TRXEDI table. Fields in the TRXEDI table are defined by the EDI interface, not FrontLine. FrontLine only requires this table to have a key on OrderID and Line. There is a new security class for EDI with 20 contexts to control user access to the EDI data. If TRXEDI contains an int field named PersonID, FrontLine will not display this field but will set it to the User ID of the person who saves changes to a record.

- Both Ctrl keys must now be down to delete a Tax Detail record from tax maintenance.

- Service orders with repair units still at the depot can now be partially checked out when the entire service order is not marked as ready/serviced.

- Fixed: Entering a total of zero units quantity counted in Physical Count did not update the overall item quantity in the location from a blank.

- Fixed: Unique identifiers of units adjusted out were not excluded when verifying identifier uniqueness.

- Fixed: A part or service selected from Item Lookup for a service order did not trigger the repair unit assignment menu.

- Fixed: Purchase Order Lookup Open Received Purchase Orders was including closed purchase orders.

- Titles of the form selection buttons in Forms for Orders are now labels that can be changed. Note that changing such a label does not affect the form file names. Example, if "Delivery Ticket" is relabelled "In Process" the form files are still DeliveryTicket*.rep

- The Entity function in order windows is now labelled Customer or Vendor (using label dictionary) depending on the order type.

- In Locations maintenance, copying a location no longer copies the ExtRef, and a system administrator can edit the location's ExtRef value.

- It is now possible to override a customer's credit limit when manually entering an On Account tender. Permission to do this is determined by the user's Add permit for the context Orders for Customer On Hold.

- Fixed: When the company setting Constrain Payments was set to Isolated it was not possible to pay for multiple receivables on a single order.

- Rental line items are now created at $0. To price recurring rentals, the recurring price must be set on the equipment set member. Non-recurring rentals are priced directly on the line item.

- The order header location can now be changed on any open uninvoiced order. FrontLine notifies the user that existing line items remain in their current location and can be changed individually as applicable.

- Introduced a Recurring Rental Item Type flag to indicate that the item is set eligible and incurs recurring bills as a rental item from rental locations, but is neither from non-rental locations. To mark an Item as a Recurring Rental, its ITEMS.ItemType needs a combination of three flags:
>> Rental (256)
>> Set Eligible (64)
>> Recurring Bills (4)
for a combination value of 324 in decimal or 144 in hex.

- The Customer Equipment list in the Scan Match window now shows units rented to the customer sorted before units owned by the customer.

- Fixed: Some quirks finding equipment from the Service Contracts window using the Identifier field type-in search method.

- Added BillToContactPhone3 and ShipToContactPhone3 to outputs from Forms for Orders.

- Added a display of the Equipment Set Customer PO: ... in the Contracts list in the Service Contracts window when there is no primary identifier.

- Added a Rental Location flag for locations. A rental location provides rentals in the place of sales. Units from a rental location can be rented, returned, and exchanged. Rental units are eligible for equipment sets. Units in stock at a rental location can be repaired on an Inventory RA, but any parts for the repair must come from non-rental locations.

- Changed the item category acount field AllowAdvertise to UnearnedRevenue.
The Db Console contains an entry ITEMCATS.AllowAdvertise to UnearnedRevenue (6.1.026) to rename this column.
Note that this update is required to log into FrontLine 6.1.026 and breaks prior versions of FrontLine.
To apply the update, log in as 'sa' and proceed directly to the Db Console.

- Fixed: When shipped units were returned using the Returns window, the return unit was incorrectly marked shipped.

- Fixed: In Receiving, FrontLine can sequence up to 19 trailing digits on the primary identifiers. Now if the trailing digits are more than 19 digits only the right-most 19 digits are used, additional digits on the left are preserved as non-digits instead of being lost or rejected.

- Fixed: Adding a new unit to a new equipment set for a customer just created could result in a key violation of PK_ESDTL.

- Added a contacts icon to the first column of the address list in maintenance windows to indicate the presence of contacts at that address.

- The Country of the workstation's location's pay-to address is now used as a default for new addresses.

- Fixed: Incorrectly costed assemblies where a component was costed from multiple layers.

- Fixed: On MSSQL, a Meter ReadDate can include a time but FrontLine did not show this time. One consequence was that entries with a time could not be deleted.

- Fixed: Billed meter readings could not be deleted (correct), but they could be modified (wrong). Billed meter readings should not be deleted or modified.

- Added field ReadDate to recurring billing output, the date of a meter reading.

- Added fields INVOICE.OrderTotalItems and INVOICE.OrderTotalTaxes to the output from Forms for Orders for Invoices, Receipts, Pick Tickets, Delivery Tickets, etc. Note that these order totals are subject to change until the order is closed.

- Fixed: Shipped committed units are now handled correctly by user-commit and auto-commit of inventory and unidentified units.

- Fixed: Inventory Valuation and Inventory Transactions did not handle I-RAs and shipping correctly. These revisions should have been made with the implementation of I-RAs in 6.1.019

- Revised the Manufacturer Representative (MR) line item icon and added it to order lookup.

- Fixed: With a few steps it was possible to work around entering required order identifiers.

- Added a drop down to the Print button in report previews with a Make PDF function to save the output as a PDF in a file designated by the user.

- Added a drop down to the Quote button in customer orders with a Manufacturer Representative toggle function that makes any special order line items (whether orders or quotes) MR items instead. Currently this is only a visual distinction, there is no functional difference.

- Implemented Inventory RAs, abbreviated I-RA. These are special service orders for the SELF Customer. Shipping is revised to accommodate them.

- Fixed: Changing the line price of returned equipment would result in a tax miscalculation.

- Fixed: The Details section in Periodic Invoices was using reference line Effective $ instead of the actual line Effective.

- Fixed: In Shipping, manually entered shipping references did not update the shipments record.

- Added a notice message when the user changes an order location with line items in other locations.

- Expanded application of the security contact Orders for Customer On Hold to:

- Fixed: When the user changed an Order Location, FrontLine would change the location of existing line items without updating other properties such as the accounts. Now changing the order location does not change the location of existing line items, it only changes the default location of new line items.

- Added a Ship Tracking information line to relevant events in the Unit Tracker.

- Fixed: A new address assigned as an entity's default address for a function was not assigned that address attribute when it was the first address for the entity. This bug was probably introduced in 6.1.011

- Added a D indicator to depot repair line items and orders with depot repairs in order lookup.

- Shipping can now handle RA units to an undetermined depot. These units are collected in a potential shipment where the user must determine the destination when preparing to ship.

- The alternate Ship To address selector in Shipping now shows the names of the address, and up to eight most recently used entries are saved persistently across sessions for a user in the drop-down list.

- FrontLine now tags a repair unit to return to depot automatically based on the last sale date and the depot repair start/end age defined in the item stock record. The depot repair start/end numbers are age in days. If the start and end numbers are equal then the item is never automatically sent to depot. If the end age is higher than the start, the item is automatically sent to depot when its age falls between the start and end. If the start age is higher than the end, the item is automatically sent to depot when its age falls outside the end and start.
The Db Console contains an entry File: UnitAge v1 (6.1.015) to create a new required database procedure.
This entry requires script files UnitAge.sql (MSSQL) or pgUnitAge.sql (PostgreSQL)

- Fixed: The lookup for Open Transfer Orders did not find transfers that had just been created due to a piece of data lost when setting the destination.

- Added a Placed vs Scheduled date selector for Recurring Bills in a Tax Report. For existing batches this selection only affects the date reported for recurring bills. For new batches this selection also changes the tagging criteria.

- Fixed: As of 6.1.011, FrontLine stopped asking to make a new entity address the default bill-to / ship-to / etc (depending on relevance) when not already assigned.

- Repair Unit line items do not permit user price changes, even if the unit has no identifiers.

- Added a security context Other's Orders for both Customer Orders and Purchase Orders. Values relevant in this context are:

Recommended db revision for MSSQL to prevent foreign key constraint errors when deleting entities such as customers:
ALTER TABLE ENTITYADDRESSES DROP CONSTRAINT FK_ENTITYADDRESSES

- Fixed: Returning a long order (ex, more than 40 lines with multiple units to return) could result in an access violation from the Returns window.

- Fixed: Some labels, like Phone 1, 2, 3 in Contacts maintenance, lost label translation in the last revision or two.

- A copied address now gets all the address preferences from the source address.

- The results of an Order Lookup by an order identifier value are now sorted to show open orders first, with the secondary sort the Placed date descending. Before it was sorted only by the order placed date descending.

- Added a "Ship To" modifier entry box to Shipping where one can override the shipping address by entering a vendor number or customer number to get their default ship-to address. A "Revert" function is provided to undo the change. No lookup is provided.

- Added an indicator icon to the Status column in Scan Match views "Scan Matches" and "Unit Details" that appears when the unit is covered under at least one active contract.

- Fixed: The total fields output by Periodic Invoices to the forms (example, INVTO.InvoiceTotal) were multipled by the number of Invoicing contacts indicated on the BillTo address.

- Fixed: When package members were marked to Hide under some circumstances the package itself would be marked to Hide too.

- Fixed: Persistence of identifier types selected in Equipment Search was broken.

- Fixed: In Purchase Order Lookup the Vendor Ref Search By entry was labelled Entity Order.

- Fixed: When list entries appeared in a triggering order, FrontLine matched an unintended entry by partial match when a complete match was present. Example, PK2 could match PK25. This is only correct when there is no PK2 entry.

- When price levels are copied after saving a copied item, Min Base is no longer set in the new item's price levels.

- On Return orders (where the entire order is a return) the ShipTo address and POS vs Order Entry mode cannot be changed due to taxes.

- Fixed: Forms for Orders printed from the Invoice window did not fill in the contact email addresses upon emailing the output.

- Fixed: In the Periodic Invoices function, Print This Invoice did not provide contact email details to the preview for email potential.

- Fixed: In Periodic Invoices, opening subsequent batches would lose the billing email presence indicator.

- In Periodic Invoices, changed the criteria for Action vs Stock number exposure in the output from "Line is from a recurring bill" to "Item Type includes recurring billing."

- The first three datasets are now used for field subsitution in the email text templates introduced in 6.1

- Some minor tweaks in Shipping integration features. Note that the SHIPMENTS table has been updated. If this table is already in the database, drop it then recreate it with the Db Console entry.

- Fixed: Pasted identifier values from the feature introduced in 6.0.0112 stopped saving at some later revision.

- Added an optional Customer Number Pattern to Periodic Invoices to filter out bills and invoices based on customer number.

- In Shipping package members are now listed first with a package icon by the line number.

- Fixed: When Recurring Billing Output is invoked directly from an order, only the "Print One" and "eMail One" functions are available.

- Fixed: A voided service line item with an identifiers document would often wait for required identifiers.

- Added functionality to Shipping for integration with UPS WorldShip and FedEx Ship Manager. Note, however, that such integration involves significant setup in WorldShip / Ship Manager as well as creating special database objects and functions to handle the data exchange.
The Db Console contains an entry SHIPMENTS (New in 6.1.006) to create a new SHIPMENTS table.

- Fixed: Payment collection during order checkout would assign an 1899 date to card payments where no expiration date had been entered. This bug was introduced in 6.0.0111

- Fixed: The end date criteria for Periodic Invoices did not include the whole ending day.

- Added an index key to a temporary table used to generate purchasing suggestions. The result is faster auto-gen suggestions for catalog vendors.

- Fixed: Latitude and Longitude identifiers formatted for double display (example Latitude: 39° 11' 15" N 39deg 11.25min) would erroneously change by the seconds when a user passes through this identifier value while editing.

- Fixed: A recent revision to the order voiding process no longer voids the lines. Transaction Inquiry did not exclude such items, now it does (the fix).

- Put the customer name in the title of calendar event submissions, and moved the customer number into the event description.

- Added a resource link capability to the Identifier Document window: Plain text identifier values that begin with \\ or C:\ (C can be any letter) or http:// or https:// activate an icon in the left column indicating the resource link. The resource (file or web page) can be opened with either a double-click or using Ctrl-. (control period). FrontLine opens the resource as Windows would, file type associations determine which program opens a file.

- Fixed: The calendar button in the Next Bill Up To field for Recurring Billing had disappeared in 6.0.0111

- The identifier type selection offered in Equipment Search is now constrained to identifiers that appear on item templates.

- The first four Contact Preferences are now relevant to FrontLine processing, indicating that a contact is used for these purposes:

- Periodic Invoices and Recurring Bills Output now provide for direct emailing. This facility provides three new functions alongside the existing "print all" and "print one" options:

- Alongside forms, FrontLine now supports email body text templates. For example, sending email from the output of the SalesOrder.rep form will use an optional corresponding SalesOrder.eml template. If the very first line in the template begins with 'Subject:' that line is used as the email subject. Field subsitution is performed from the first dataset in the output. In the template file, indicate fields by their names using tags like <FLF>CustomerNumber</FLF> where FLF stands for FrontLine Field.
Note that interactive email composition does not interpret html, but html tags can be used in the message body if it begins with <html> and ends with </html>

- Fixed: The Add (New) and Delete (Cancel) permits for the Recurring Billing security context were not applied to Recurring Billing and Periodic Invoices, only None (no access) was implemented.

- Added a security context for Customers: Address Preferences. Note that this context must be set for appropriate access profiles or users will not be able to set or change customer address preferences.

- Periodic Invoices now removes sale/refund pairs from its line item output. The refund (return) must refer to the original sale, have the same total price and taxes, and be in the same periodic invoice batch.

- Added a note indicator to the Equipment Search results grid, and a function to open these address notes.

- Resource Costs are now copied to return line items, and the quantity of miscellaneous returns cannot be changed.
The Db Console contains a link File: CopyLineItems 6.0.0115 to open the appropriate script to update the CopyLineItems database procedure.

- Fixed: When future orders were enabled, FrontLine would ask the user for confirmation to commit inventory to future orders when the line item was scheduled with a non-future date.

- Fixed: Receiving transfer inventory without first committing them to the transfer would create a circular reference in the unit event history.

- Fixed: Inventory Valuation incorrectly summarized unit and total values for Unit(Actual) costed items under some circumstances.

- Connected Periodic Invoices [SyncStatus>=0] can no longer be cancelled, and are marked with a green checkmark in the list.

- Added a Lookup function to Periodic Invoices to find a Periodic Invoice ID (PVID) in any batch.

- Fixed: Inventory Transactions counted inventory committed to transfer in the total of the destination location instead of the source location.

- The default cost of miscellaneous purchases is now zero regardless of last cost.

- Added an I.Doc function to the Scan Match window that opens the unit identifier document in read-only mode.

- Added a drop-down menu to the Edit button in the Identifier Document window with Copy and Paste functions. Note that Paste does not set unique identifiers, and does not overwrite existing values.

- Enabled the Provisioning Item Type for any recurring billing item. Tangible items marked for provisioning are now treated like recurring billing services and charges in that prices are set on the new equipment set member and the sale line item price is prorated accordingly.

- Periodic Invoices no longer summarizes recurring bill line items for the middle grid data.

- Added Country to Equipment Search. Note that countries are identified in the database using a two-character country code. Thus, partial matches on country names are not supported.

The Db Console contains a required database update entry PAYMENTS.TransID (New in 6.0.0111) to add a new required field.

- Fixed: FrontLine could not prorate returns without a valid order reference on the equipment set member.

- Fixed two hang situations: Generate Purchase Order upon PO generation if some suggestions were deleted. Deleting an address in the middle of list (as in customer maintenance). These were introduced in 6.0.0108 by a troublesome fix (clicking line item) that has now been undone.

- Fixed: Critical bug introduced in 6.0.0106 that caused FrontLine to fail after entering a new agent directly on the order header.

- Fixed: An error would occur upon deleting an address from the entity address list. This bug was introduced in 6.0.0087

- Fixed: An SQL foreign key conflict would occur upon invoking the context menu (or keyboard short-cuts for some of the functions) on a new equipment set member moved to an equipment set that had just been created.

- New: FrontLine prorates returns of recurring billing items that are currently on equipment sets.

- Fixed: Yes/No option fields in the Package editor were broken in the last month or two.

- Fixed: Clicking on an existing line item when the cursor is on a new line item, particularly when there are enough line items to scroll, would position on the line above the line clicked.

- Added an Equipment Search feature accessible from the Inquiry group in the Welcome window:

- Fixed: Newly added equipment set members would show the stock number as a secondary identifier in the Equipment Sets window until the equipment sets were reopened or the secondary identifier changed.

- The secondary identifier in the Equipment Sets window is now left aligned instead of centered.

- Changing the Bill Frequency of an Equipment Set now re-prorates set members that are open on the background order.

- Fixed: While future special orders would be quantified as future in the Quantity Details of Generate Purchase Order, the purchase line would be suggested anyway.

- Exchange In line items are now excluded from the details of Periodic Invoices.

- Added a By Location option to the Tax Report. Choosing this option sorts the output first by Location, and requires a form file TaxesByLocation.rep that is appropriately grouped.

- In Generate Purchase Order there is now an option to generate purchases only for special orders placed by a particular agent.

- When a single letter is entered as a Customer Number for a new customer record, FrontLine will assign the customer number using that letter with a trailing number that is the next higher value of existing customer numbers that begin with that letter. Example:

- Fixed: The 4dp revision in 6.0.0104 did not post correctly in some circumstances.

- Fixed: When the same item appeared more than once on a customer order, it was not correctly represented in Periodic Invoices.

- The filter in lookup windows is no longer reset upon a new search, and the column headers turn a pink when the results are filtered.

- Added to Company Setting Returns, Unidentified an option I.Docs can be modified on Returns in the Returns and Unidentified Options window. Activating this option allows users to edit identifier documents of return units in the Line Item Details window.

- Fixed: With the company setting Costing Received Goods set to Receiving Check-In, Check In of received line items with a UOM factor other than 1 would produce incorrect quantities and unit costs in the layers and transaction costing, and also throw off average costs. This bug was introduced with the 6.0.0087 revision of CostInvoice. Fields that could get incorrect data are:

- Fixed: Items marked Special Order on the stock record could not be committed from the Scan Match window. Instead, the line item simply became a special order.

- The secondary sort field when a column header is clicked in Physical Count is now Stock number.

- Added a Demands floating view to the Generate Purchase Order feature to show more information about the demands that resulted in a purchase suggestion.

- Lead times (Max/Min/Avg) of Vendor Performance in Generate Purchase Order are now evaluated for the past 3 months instead of 1 year.

- Allow for four decimal places (4dp) for unit Cost and Price information beyond line item overrides to Std/Avg/Last costs, Costing layers, List Price, and Price Levels. Line totals and Order totals are still rounded to two decimal places. This is a continuation of the 4dp revision introduced in 6.0.0100
The Db Console contains an entry 4dp costing (PostgreSQL 6.0.0104) to revise some column data types in more tables in PostgreSQL only.

- Added a Find Invoice ID function to the summary grid in Periodic Invoices.

- Added a Print This Invoice function to Periodic Invoices that outputs only the current periodic invoice.

- Added TotalItems and TotalTaxes to the Payments and Bill Completion list in Recurring Billing and extended the Export function to provide an option of exporting Payments and Bill Completion vs Bill Summary by Stock Number. (Don't miss the old Show Names toggle on the context menu.)

- Added an Action field to the INVOICE and INVSUM datasets in Periodic Invoices. The value of this field is:

- Added Item Type flag Flat Billing Rate that can also be toggled on Equipment Set members.

- Allow for four decimal places (4dp) on the Cost/Price of line items. Note that the line total is still rounded to two decimal places. A similar revision applies to equipment set members, with potential effects on recurring billing.
The Db Console contains an entry 4dp line cost (PostgreSQL 6.0.0100) to revise the column data types in several fields in PostgreSQL only.

- Added a non-persistent Explode Quantities option to Forms for Orders that expands lump sum unit quantities greater than 1 without fractions into rows with quantity 1 each. This is to facilitate creating unit labels on a form.

- The appearance of the Periodic Invoices link in the Welcome window now depends on the existence of the optional PVIDS table in the database, instead of specific activation codes.

- Periodic Invoices now reads the equipment residence address before the airport address.

- Periodic Invoices now produces a Periodic Invoice ID (PVID) for each collection sent to a particular Customer+BillTo address.
The Db Console contains an entry PVIDS (Optional 6.0.0099) to create a table required for mapping PVID values.
This table is not required to use FrontLine, but without it the Periodic Invoices link in the Welcome window does not appear.
Thus for sites that do not use periodic invoicing, do not create this table.

- Fixed: In Forms for Orders, the payments dataset was not reset for Sales Orders output.

- Fixed: Identifiers with single quotes added in the Identifier Document window after choosing Unidentified from the Scan Match window would result in an SQL syntax error upon saving.

- Fixed: Cost of assemblies cannot be changed directly anymore. Instead when a member cost or quantity is changed, the assembly cost is updated accordingly.

- Added a special Item Lookup Packages w/Discontinued Members, and in the Package editor discontinued members are indicated as such in their description text.

- Added a Location filter to Customer and Purchase Order Lookup. Note that for this filter to be useful, when applicable the All Locations option checkbox near the bottom of the window must be turned on.

- Renamed ITEMCATS.AllowMisc to AssemblyWO for use by assemblies. This is the last column in Setup Lists for Item Category Accounts.
The Db Console contains an entry ITEMCATS.AllowMisc to AssemblyWO (6.0.0096) to rename this field.
This change breaks older versions of FrontLine, and 6.0.0096 requires the change to log on.
Thus the first log on after this update must be by 'sa' to open the Db Console directly.

- Added an Exclude Committed option to Physical Count that excludes inventory committed for sale from the Qty On File. The Qty On File is re-evaluated when Total Counted is changed by user input. Qty On File is the reference value used to create adjustments.

- The Periodic Invoices feature only appears for Ormandy and ASRI activations.

- Added Periodic Invoices feature, accessible from the Recurring Billing group in the Welcome window.
The Db Console contains an entry ORDERS|INVOICES.PSet to add the required PSet field to two tables.

- Separated and changed the security contexts of Item Tax Category and Billing Tax Category in preparation for an upcoming log feature. Consequently, access profiles have to be updated. An Unknown Context [210015] will appear in existing access profiles; it can be removed using the Delete function in the Access Profiles window.

- If known, the Residence address of an equipment unit brought in for repair becomes the ShipTo address of a new service order.

- Added a Filter Addresses feature to the address list context menu in maintenance windows, enabling the user to show all or only addresses that match one or more address preferences. This filter is persistent after logoff. The column headers of the address list turn pink when the list is filtered.

- Added simple last changed date/time/person to Item Category Accounts in Lists Setup. This requires a database update to the ITEMCATS table. Note that FrontLine will work without adding these fields but users will not be able to save changes to Item Category Accounts.
The Db Console contains an entry ITEMCATS.Update to add the two fields to one table.

- Fixed: When an exchange was returned, the units were not swapped back in equipment sets.

- Fixed: When a unit was returned that was ungrouped in an equipment set, after check-out FrontLine would remove all ungrouped members of that equipment set instead of only the one unit.

- Fixed: The Order Returns feature introduced in 6.0.0051 did not handle discount line items.

- Added a context menu to the unit detail grid in Inventory Valuation, including an ability to directly open the purchase order where the unit was received.

- Fixed: Inventory Valuation for Actual(Unit) costed items was omitting units committed for sale, and did not trace back to original purchases.

- Fixed: In the Returns window, entering a quantity in the Line Units then pressing Esc and entering another quantity would get the Line Items quantity out of sync.

- Fixed: The standard address property checkboxes in maintenance window, such as BillTo and ShipTo, were not modified by changing the corresponding Labels.

- Custom Address Prefs now appear before standard address properties in texts.

- Added an Address option to the Service Contracts window that provides a field below the equipment list with equipment residence address.

- Fixed: The Details feature in Inventory Valuation had stopped showing any details.

- Fixed: The Identifier Document window presented for an adjust IN highlighted identifiers required for sale instead of identifiers required for receiving.

- Added a context menu to the results grid of the Db Console to make it easier to see some of the functions available.

- The Unit Price column on order line items how goes by the UOM, both for display and data entry.

- If an outgoing Exchange unit's identifier document contains identifiers that the incoming Exchange unit's document contains, those identifiers are discarded from the outgoing unit when the Exchange window is closed so they can be replaced by the incoming identifiers.

- Exchanges now update the ItemID, OrderID, and Line of applicable Equipment Set members.
The Db Console contains an entry File: CommitInvoice v6.0.0088 to implement this revision. This entry requires script files CommitInvoice600088.sql (MSSQL) or pgCommitInvoice600088.sql (PostgreSQL)
The Db Console also contains an entry File: CostInvoice v6.0.0087 to implement another critical revision that coordinates the purchasing UOM with back office. This entry requires script files CostInvoice600087.sql (MSSQL) or pgCostInvoice600087.sql (PostgreSQL)

- Fixed: When the recurring billing price of an equipment set member with a corresponding line item on an open order, FrontLine would change the line item price (prorated) even if that line item was no longer open.

- Implementation of Airport identifier type, with a new Airports list that can be edited in Setup - Lists. Only the airport code is stored in an identifier, but both the airport code and the airport name are matched when typed into an identifier document.

- In the Identifier Document editor window, an Airport row is enlarged and the airport City, State, Longitude, Latitude, and Elevation are shown. Note that these are not shown in the Line Item Details window.

- In the Identifier Document editor window, while editing, the Enter/Return key now simluates the Down arrow.

- Fixed: On Microsoft SQL Server databases, setting a large line item quantity could result in an error like "Cannot insert the value NULL into column 'Quantity', table TRXTAXIP;" This fix is entirely in the database itself, and can be used with older versions of FrontLine.
The Db Console contains an entry File: GetTaxes v6 (MSSQL) to implement this fix.
First, the type of some fields in the database must be updated, then the GetTaxes stored procedure updated. The script file has brief comments.

- Fixed: There were some circumstances when, during check-out, FrontLine would stop on a voided line to fulfill the quantity. Related revisions 6.0.0076 (broken) and 6.0.0078 (fix).

- Fixed: Adjust out transactions were not put through costing.
The Db Console contains an entry File: CostInvoice v6.0.0086 for a required updated to the CostInvoice database procedure.
Both the FrontLine executable and this db procedure must be updated for the 6.0.0086 fix to work.
Do NOT deploy the 6.0.0086 executable without the 6.0.0086 CostInvoice procedure update.

- Fixed: After moving equipment set members from one existing set to another, a primary key violation could result when saving the changes.

- Fixed: The alternate coverage icon for provisioning contracts stopped showing up in the Service Contracts window from 6.0.0080

- Fixed: The list of which check-out to print in Reports for Orders would fail to appear for a Ship Ticket when it was selected right after a Picket Ticket.

- Added a Spreadsheet option to the Export function that adds a leading single quote to text field values so they are not interpreted as numbers by Excel.

- Implementation of Length identifier type. Units supported for display and input are: mm, cm, m, km, in, ft, yd, mi. Lengths are stored in meters. The default display and input is in meters. Multiple units can be displayed for a single identifier value. Example, a mask like %ft %m will display the length in both feet and meters. Because ft appears first, typing in a length of 5 is considered to be 5 feet. To input other units, include the unit as in 5m, or 5 m, or 5cm, or 5mi, etc. Spaces between the number and unit are tolerated.

- Fixed: The "Include Zero Quantities" option in Inventory Valuation was broken.

- Fixed: Inventory committed to a repair part line item (a sale line linked to a repair unit line) whether from known stock or unidentified, was marked as repaired instead of sold.

- Implementation of Latitude and Longitude identifier types. Either is stored as a single signed decimal coordinate. The identifier mask controls both the input and display format. This format can convert the coordinate into degrees, minutes, and seconds, and indicate the hemisphere. The format tokens, which can appear in any order, are:
%C +/- integer coordinate degrees
%c +/- decimal coordinate degrees
%D + integer degrees
%d + decimal degrees
%M + integer minutes
%m + decimal minutes
%S + integer seconds
%s + decimal seconds
%H = hemisphere N/S/E/W.
%D° %M' %S" %H is the default format used when the identifier mask is blank. Note the literal degree, minute, and second characters in the format string for reading clarity, without them only the values for each token are displayed. A latitude output sample for this format is 34° 56' 47" S

- Fixed: Some completed count events were not shown in Physical Count when the All option was used.

- Added a Find function for text columns in Physical Count, Inventory Transactions, and Inventory Valuation.

- In Physical Count, changed the option label "Include Untransacted Items" to "Include Never On Hand Items".

- Added a worksheet icon indicator to the status column in Inventory Transactions when the transaction was from a physical count.

- Defective and In Shop inventory can now be seen in the Scan Match window for adjust out transactions.

- In the Item Quantities window, unidentified sale quantities are now shown in square brackets, as a negative number on available, and positive on sold.

- Added a Subtract Unidentified option to Inventory Valuation. The unidentified quantity is not subtracted in the export/report dataset, but instead is available as a separate field named QtyUnidentified regardless of whether the Subtract Unidentified option is on.

- Added a new option to the Physical Count criteria: Include Items with no Transactions in this Location.

- The start date of a Physical Count is now copied to the Scheduled date on the resulting Adjustment Order.

- The adjustment event date of transactions created by a Physical Count is now set to the start date of the physical count.

- The Physical Count function is now aware of Unidentified transactions. The unidentified quantity found when the physical was started is shown as a subtraction in square brackets in the Qty On File column, and the adjusted input quantity is shown in the Total Counted column. The unidentified quantity is available as a separate field named QtyUnidentified for exports and reports. Adjustments in for unidentified sales are put on a separate line item ending with a 9.
The Db Console contains an entry PHYSCOUNT.UnidentifiedQty (6.0.0081) to add a new field required.

- When a service contract line item is returned, the corresponding equipment set entry is now disabled and its Terminated date is set.

- Added a Provisioning Item Type to the Items maintenance window that is applicable to Service Contracts,

- Added Address Prefs as a display and filter field to lookups of Customer and Vendor lookups.

- Added custom Address Preferences. This is a list of up to 15 attributes that can be labelled as desired in FrontLine Lists maintenance. Checkboxes are added at the base of the full address block in maintenance windows with addresses (lower right) for non-blank custom attributes.
The Db Console contains an entry Expand Address Attributes (6.0.0080) to expand the ENTITYADDRESSES.Attributes field.
The Db Console contains an entry File: CommitInvoice procedure 6.0.0080 to carry the UI field introduced in 6.0.0076 to line item history. This entry requires script files CommitInvoice600080.sql (MSSQL) or pgCommitInvoice600080.sql (PostgreSQL)

- Fixed: FrontLine would stop on voided line items to fulfill the quantity. This bug was introduced in 6.0.0076

- Fixed: The Lookup function in Line Item Details was enabled on Adjust In transactions.

- Added a Report function to the context menu in Physical Count. A visual report file named PhysicalCount.rep in the templates folder is used for the presentation.

- Added TESSCO Catalog Update to the Third Party panel in the Welcome window. This link launches a batch file in the FrontLine program folder named TESCatUpFLFL.CMD where FLFL is the name of the database in use. See the MOL Catalog Update release notes.

- Added an All function to the Service Contracts window to show all of the customer's service contracts like the selected contract. This function is only available when a single contract is shown.

- Added an ability to open the identifier documents of service contracts, as applicable, from both the Service Contracts window and the Equipment Sets window. The members grid in the Equipment Sets window now also shows the primary identifier of a service contract, if one exists.

- Fixed: The new Report function introduced in 6.0.0076 for Inventory Valuation did not look in the templates folder, and missed a step in the assignment of dataset aliases.

- Added a Report function to the context menu in Inventory Valuation. A visual report file named InventoryValuation.rep in the templates folder is used for the presentation.

- Added a list of Sorting fields in Inventory Valuation. Drag and drop the names to change the sorting precendence. The order set is not yet persistent after logoff.

- Added Identifier Documents to line items and equipment set service lines. This allows a service to have an identifier document attached to the transaction. Now, service and charge line items with a suitable doc template [UISet] will show an identifier document in Line Item Details and enable the I.Doc function in Equipment Sets.
The Db Console contains an entry Service I.Docs (6.0.0076) to update four tables and one trigger.

- FrontLine now offers to complete an order that has been checked through before but not completed. For example, a partial check out followed by reduction of partially fulfilled line item quantities to cancel backorders, and/or voiding open line items.

- Added a Map Address function to the address context menu in relevant maintenance windows.

- There is a new Report category Diagnostic (default for file names starting Z_) for SQL queries to display the results in a FrontLine grid that can be used for viewing additional data in FrontLine windows if requisite fields are present: Orders, Customers, Vendors, Items, Item Quantities, Item Costing, Unit Tracking. The data can also be exported.

- In the Reports window, pressing a character key when not in maintenance mode moves to the next report with a description start starts with that character.

- The Scripts contained in the Db Console has been pruned to remove updates prior to 5.6

- Item Costing can now be opened directly from the Db Console using Ctrl-6 with these fields present in the dataset:
ItemID, ItemType, UISet, ItemStatus, Stock.

- This revision of the database procedure makes no changes to the logic. It averts a potential deadlock that occurs in Microsoft SQL Server only. Note that this version is not listed in the FrontLine Db Console. However, it can be loaded in the Db Console by manually selecting the file CostInvoice600073.sql or applied using SQL Server Management Studio.

- Fixed: The SQL script writer for building destination costing layers upon check in of a transfer order could overwhelm MSSQL Server when a large number of transfer line items were being checked in at once.

- Fixed: The Returns function didn't do anything when the current line item was a return.

- Items maintenance now has a Zoom function to Maximize the section with Preset Identifiers / Price Levels / Promotions.

- This revision of the database procedure fixes an omission that caused the Check In of Transfers to produce an error in FrontLine CostInvoice-Line specified with other parameters missing. The transfer source would be costed (out) successfully but not the destination (in). Note that this version will be listed in the FrontLine Db Console in 6.0.0073. It can be also be loaded in earlier versions of the Db Console by manually selecting the file CostInvoice600072.sql (MSSQL) or pgCostInvoice600072.sql (PostgreSQL).

- Fixed: Identifiers entered in the Receive window were not validated against fixed value lists. For example, a Color identifier.

- Fixed: FrontLine no longer checks for required order identifiers on recurring bills.

- Fixed: Set Eligible items will no longer auto-commit because auto-commit cannot add members to equipment sets.

- In Shipping FrontLine will now pop up a message when the Scan Code entered has no match.

- The values in the Identifier Document window are refreshed every time it is opened, even when the same unit is viewed twice in a row.

- Added a Show Discontinued option to the Item Lookup window. By default, discontinued items are no longer shown.

- Fixed: The Recurring Bills item type flag (from ITEMS.ItemType) is no longer put on the line item type (TrxType) for orders that are not recurring bills. This addresses missing costing on sales of such items.

- Fixed: The order Returns function was disabled if there were any return line items on the customer order. This constraint is no longer necessary with the elaborated Returns feature introduced in 6.0.0051

- Added MOL Catalog Update to the Third Party panel in the Welcome window. This link launches a batch file in the FrontLine program folder named MOLCatUpFLFL.CMD where FLFL is the name of the database in use. FrontLine notifies the user if it has already launched a catalog update. This link is disabled when the corresponding file is not found.

- Fixed: Auto-commit in PostgreSQL didn't find any inventory. This was broken in 6.0.0069 below.

- Fixed: Checking in a PO with packages where FrontLine is set to Cost Receivings Check-In would result in an error from the CostInvoice procedure about the unit missing for the package line. This was introduced in 6.0.0063

- On the costing display introduced in the prior release, changed the ExInvoice column title to Method and ExInvDate column title to Date and InvQty column title to Quantity.

- FrontLine will now only ask if all the line items on the order are ready when none of the line items have been marked ready individually.

The Db Console contains an entry File: CostInvoice v6.0.0070 to update this database stored procedure.
This update is required for back office AP to send back purchasing invoice numbers without costing values.
The script is contained in external files CostInvoice600070.sql (MSSQL) or pgCostInvoice600070.sql (PostgreSQL)

- Fixed: Changing a line quantity on a transfer order when there was already inventory allocated to the line would result in auto-commit allocating from the destination location.

- Fixed: Transfers are now costed. From the source location they are costed like sales. At the destination location they are costed like receivings at the source sale cost. The CostInvoice db procedure revision described below is required as part of this fix.

- Costing details recorded in TRXINVCOST can now be seen in the Invoice/Receipt/Check In/Check Out/etc window by using the Costing function on the toolbar. Note that this costing is only available after the process has completed. Completed invoices/receipts/check-ins/check-outs for an order can be seen using Alt-F8 from the main order window.

- The cost shown in the Cost column in Transaction Inquiry now depends on the item costing method:

The Db Console contains an entry File: CostInvoice v6.0.0069 to update this database stored procedure.
This required update is contained in external files CostInvoice600069.sql (MSSQL) or pgCostInvoice600069.sql (PostgreSQL)

- Fixed: The green box around the line item quantity did not update when a quantity the Selected Items list of Line Item Details (new in 6.0.0067) was changed.

- Fixed: An occasional "No value for parameter" error from the order Returns function.

- Fixed: The green box indicator around line item quantities was not drawn when an adjust out line was first created with inventory allocated to it.

- The Find feature in the Equipment Sets window now finds stock numbers if a matching primary identifier is not found.

- Added an Copy Address feature to maintenance windows. It can be seen on the context menu that appears for the address list.

- Added a No Print flag toggle on the line item context menu that can be used on forms to hide line items marked as such. A crossed out printer icon on the line item reveals this flag. The default value for this flag comes from the Item Type flag Hide Line.

- Fixed: FrontLine would assume an order's line increment should be 10 when the first line number was less than 100; for example, when line 50 was inserted. This has been adjusted to when the first line number is 10 or less. This was only a problem with the company setting for line increment at 100.

- The Quantity of a unit committed for sale in the Line Item Details window can now be changed per allocation for items that do not have unique identifiers. Simply type into the Quantity cell in the Selected Items list. This allows one to set the quantity allocated to a value other than the line quantity or quantity available in stock, for cases where one wants to share available stock among multiple orders.

- Added the Location ExtRef to order address selection menus when the address is a location address. This may be helpful for Purchases, Transfers, and Adjustments.

- Added a single letter type indicator after the OrderID in the Scan Match listing for open Purchase Orders: Adjustment, Purchase, Transfer, Work Order.

- Uniquely identifiable items are no longer assigned to customer backorders by default when received. However, customer backorders are still shown at receiving, allowing the user to assign them as needed.

- BillTo address notes of an order now pop up for user attention when the address is selected, or the order reopened.

- Added an indicator to Reports that prevents FrontLine from performing field code interpretation for .sql and .rep reports: If the very first two characters in the query are {} then FrontLine skips code interpretation for that query and replaces the {} with spaces.

- Fixed: In Inventory Transactions, when an item was sold at Location A then returned at Location B the return transaction was shown on an inquiry for Location A.

- Fixed some inconsistent behaviour of the Stock criteria entry in the Inventory Valuation inquiry.

- Added quantities to the Inventory Valuation inquiry: Defective, In Use, In Shop.

- Resource Costs can now be entered on quotes, and will be copied to an order produced from such quote.

- Shipping will now find a potential shipment by entering an identifier of a unit ready to ship in the Destination.

- When a service order is marked Serviced, all the repair units marked To Repair will now become Repaired right away.

- In maintenance windows with the address list, when a record is opened from lookup FrontLine will now select the matching address in the list.

- Added a Send copy of email to self option to the User Options window which is accessed from the System Users window. This makes FrontLine send all outgoing email by this user to the user's return address as well as declared recipients. Note that the user's return address as a recipient is not shown in the CC field or email header.

- Added more features to Shipping including direct entry of an OrderID as the Destination.

- Added a Bin range to the Physical Count function with awareness of location-specific bins.

- Invoiced line items can now be voided provided no quantity has been checked out and no quantity has been shipped.

- Added a Company Setting Cost Receivings Check-In with an ability to have FrontLine cost the checked-in goods using the price on the PO. The default is By AP which does not cost purchases in FrontLine.
This configuration has been elaborated in later releases, see the options available in 6.3.005

- This revision of the database procedure fixes an omission in its processing: Prior versions did not add costing details to return transactions of FIFO and LIFO items.

- Fixed: Voided orders where listed in the customer Order Lookup window for special entries Open Sales Orders and Open Service Orders.

- Fixed: Marking a customer order as Complete or Serviced did not check for missing identifiers required on the order I.Doc as it does during check-out.

- Fixed: Completion of Recurring Bill Credits did not transfer tax details from TRXTAXIP to TRXTAX.

- Holding down a Ctrl key while changing an Item Type flag in Items maintenance allows you to override the Item Type Constraint.

- Added a Shipping feature. Ship Tracking numbers are attached to shipped items as identifiers. Identifier [UIType] 32,767 is used, and is added if it doesn't exist in identifier setup. However, users must be given read permission for this identifier's security context or it will appear as asterisks.
There is no integration with carrier shipping software yet.
There are two new order lookup entries to facilitate shipping: Lines Shipped Part Quantity and Lines Shipped Part of Commit.

- Fixed: When Receiving committed a received unit to a customer order (special orders and backorders), the committed event record was not directly identified with the customer.

- Fixed: An invalid (value not listed) UOM on line items would result in an access violation when viewing the order.

- Fixed: SQL error upon changing the Vendor in Resource Costs for a Miscellaneous Source. This bug was introduced somewhere between 6.0.0051 and 6.0.0057

- Fixed: The bill boundary dates were not copied to a bill credit. These are the Scheduled and Fulfilled fields of the ORDERS table.

- Printing a recurring bill credit from the Recurring Billing Output window will use a BillCredit form. The standard form is "BillCredit.rep" but where Equipment Set Category indicates "BillBones.rep" the credit form is "BillBonesCredit.rep"

- Added an information popup that recurring bills must be credited in full when user turns off the All option in the Returns window.

- Added Item Bins per location, accessible from the Items maintenance window using the ellipsis beside the Bin field. All locations are shown. Bins need only be identified where necessary. For locations where a specific Bin is not identified for an item, the Bin field on the item record serves as a default in output such as from Forms for Orders. Note that the security context of the Item Bins window is the same as the Bin field of an item.
The Db Console contains an entry ITEMBINS table (6.0.0059) to add this required table to the database.

- Fixed: When an unidentified unit was in for repair, and a unique identifier value was entered for it which was already on file for an unrelated item, the identifier value would silently be discarded as a failure of the uniqueness requirement. The uniqueness test in this context has been corrected.

- Workaround implemented: Microsoft SQL Server 2000 would incorrectly raise an error message 104 upon producing output from Forms for Orders with the Print Order I.Doc option turned on.

- A Recurring Bill can now be credited using the Return function.
>> Note that part of the voiding code has been reworked - database procedure UnCommitLineDetails is no longer used.

- Fixed: When a line item was fulfilled from the Line Item Details window, and the Available Inventory view of the Scan Match window was used to select inventory location of an item with no identifiers, the committed unit event would end up with a strange status.

- Fixed: Return orders created by the recently added Returns window did not forward the warranty flag on line items.

- Fixed: Payments grid in the Orders window could refuse input under a particular set of circumstances.

- Fixed: The green box around the line item quantity that indicates the ordered quantity has been committed or fulfilled did not work on changed line quantities until the Line Item Details window was opened once for the order.

- Fixed: When two service orders are viewed in a row where the repair unit line(s) are the same line number, and the repair assignment menu was shown for the first, FrontLine would show the same serial number in the repair assignment menu for the second.

- Fixed: When the Transfer From location was changed, the descriptive text above the address did not update.

- In Orders windows, the Return/Enter key simulates the down arrow on existing line items.

- In the Returns window, the line return quantity can now be set in the line grid (left) for items without identifiers. Previously this was only allowed for intangibles.

- In the Returns window, the Return Order Location can be changed, and there is an option to return line items to their original location.

- Added a Quarantine option per line item to the Returns feature. It defaults to the Quarantine flag on the item record, but can be turned on or off for return lines of tangibles.

- When a line item is voided, it is now also put on hold (not ready), and when unvoided the ready checkbox is unchecked.

- Added VendorNumber and VendorName to the Physical Count item list. These fields are displayed in the grid and available for export. Click the column header to sort.

- When a customer has no default SoldTo address, the BillTo first assigned to the order is used as the SoldTo.

- Fixed: Assemblies added to a Transfer Order by entering a complete stock number in the Scan text were not being stripped of the package flag.

- Fixed: When the Microsoft SQL Server default collation differs from the collation used in the FrontLine database, a "collation conflict" error would occur upon receiving an identifiable item.

- Order returns are elaborated with a new Returns window where the user can select what to return. This window also provides information about existing returns.

- Added an Account Number field to Vendors. This field is exposed in Forms for Orders as AccountNumber.
The Db Console contains an entry VENDORS.AccountNumber (6.0.0051) to add this required field to the VENDORS table in the database.

- The Line Item Change Log now includes the line item Accounts. The Line Item Change Log view has been updated to show all changes without horizontal scrolling, show the latest change on top, and add an Export function on the context menu.
The Db Console contains an entry TRXLOG Accounts (6.0.0051) to add the required account fields to the TRXLOG table in the database.

- Fixed: Under some conditions, after the first item was made an Adjust In on an Adjustment order, subsequent items entered without unit identification were assumed to be Adjust In instead of prompting for Adjust In vs Out.

- Fixed: If Customer Lookup is automatically invoked from Transaction Inquiry upon leaving the Customer criteria field, then the lookup cancelled, FrontLine did not put focus back on the Customer criteria, thus leaving an unverified customer number.

- The Note button in Equipment Sets now shows an alternate icon when the note exists, and its hover hint includes the note subject.

- Added Notes to Equipment Sets. These notes are copied to the order notes of recurring bills.

- Fixed: The TrxStatus field added to Forms for Orders in 6.0.0047 was interpreting the codes into text, which is not ideal for expressions on forms.

- Fixed: After choosing Any from the Receivables window for a payment FrontLine did not keep the total amount to check for overpayment.

- Fixed: The line items output on a Pick Ticket from Forms for Orders could come from the last order printed from the other order type function.

- The number of matches that can be shown in the special orders list of the line items context menu has been increased from 4 to 8.

- Fixed: The special order assignment feature added in 6.0.0046 did not consider the location of the line items.

- Fixed: Reopening a Payment order from the customer orders window would complain that it is not processed as a Customer Order.

- Added a green checkmark to the first column of order lookup windows to indicate completed orders. This is the same flag that is seen in text in the order status column.

- When the last received unit on an order is unreceived, the Received flag is removed from the order itself so the order can be voided.

- Added a special order assignment feature to the Special Order context menu for purchase orders. This allows manual linking of an unassigned special purchase line to a customer special order line that matches the stock number and quantity.

- Added a special lookup Unlinked Special Purchase Orders to the Purchase Order Lookup window.

- The TaxGeoCode Description display is persistent in maintenance address blocks.

- When an order is voided, only the unique identifiers in its identifier document are deleted.

- Auto-commit is attempted upon changing a line item quantity on adjustments and transfers.

- Fixed: Assembly line items on Work Orders could be checked in without receiving the assembled unit(s).

- Added a separate option for Agent on Work Orders, as seen in the Order Agent Requirements list for Company Setting Order Agent Required.

- FrontLine now checks for a missing order Agent, per company setting above, upon order Defer and Print.

- TaxGeoCode Descriptions now apear in the drop-down list of TaxGeoCodes in the address block of Agent/Customer/Location/Vendor maintenance. Note that the description is not permanently entered in the field.

- Added CommittedQuantity to the output of Forms for Orders for Pick Ticket, Delivery Ticket, Ship Ticket, and Edit List. This field contains the total quantity committed to the line item, but not checked through.

- Integrated a read-only view of Price Levels into the Items maintenance window. There is now a tabbed view for Preset Identifiers. Price Levels, and Promotions.

- Added a Default Location field to Items maintenance that sets the location of a new line item, overriding the order location. Note that this does NOT override a user-selected location from Unidentified, or an inventory unit location when a unit is selected. This feature is most useful to set the default location of a service.
The Db Console contains an entry ITEMS.DefaultLocation (6.0.0044) to add this field to the ITEMS table in database.

- Fixed: Assembled packages where not included in the Inventory Valuation inquiry.

- Fixed: Assigning a customer using lookup in Price Levels showed the Customer ID.

- Fixed: In the Scan Match window, Vendor Catalog items were not checked for the user's permission to Transact Unidentified. While vendor catalog items can be unidentified from any location, regardless of stocking history, a user without this permission should still not be able to sell them as unidentified.

- Added a Description for TaxGeoCodes in the Tax Detail window. This is an optional description of the TaxGeoCode that will be displayed in the drop-down lists in the next release of FrontLine.
The Db Console contains an entry TaxGeoDesc in 6.0.0043 to add a required table to the database.

- Fixed: In the Scan Match window, Unidentified is now enabled for Miscellaneous items even if the user does not have Transact Unidentified permission.

- Fixed: Making a customer order POS after changing the location did not use the correct TaxGeoCode.

- Added an Out of Service command to the unit context menu in the Line Item Details window that is applicable to repair units and returns. The unit gets marked as such, and if brought back for a new transaction, raises a status confirmation question. If the user accepts it anyway, the unit is still marked out of service on the new order unless the user turns off this flag using the same context menu.

- Fixed: In the Price Levels window FrontLine recognizes and displays Customer Numbers and Vendor Numbers.

- Fixed: The default quantity for a new line item is one unit of measure rather than 1.

- For Adjustments, locations on the Unidentified list in the Scan Match window are enabled even if they never had inventory.

- Fixed: Recurring Billing using a PostgreSQL database failed to set the quantity of non-contract line items on the bill to the number of months for periods of a year or longer, like Annual billing.

- Added a Tax Category override for recurring billing to ITEMS records. This enables an item to produce recurring billing line items with a tax category different from what it produces on a sales order.
The Db Console contains an entry ITEMS.TaxCatBill (New in 6.0.0040) to add this field to the database.

- Fixed: It was possible to receive a duplicate unique identifier of an item in the Receive window by deleting the offending row when FrontLine first identified it, then entering a duplicate again without closing the Receive window. The subsequent offending entries weren't caught unless the Receive window was closed.

- Fixed: ShipVia was missing from Pick Ticket forms for orders that had not been checked out yet.

- In Items maintenance, Costing method and Commissionable are now required.
Vendor is also required unless the item has either the Service or Assemble flags.

- Added two options to Physical Count. These criteria were previously always on:

- An Assembly Package as a component within another package is treated as a unit rather than a subpackage of components.

- In lookup windows, when a multi-field lookup search by (such as Description* which searches Desc1, Desc2, and Desc3) is present, those individual fields are excluded from the Search By list.

- Fixed: Possible SQL error about a missing LRL object when auto-commit is triggered.

- Fixed: Assemblies with varying member quantities were incorrectly Costed upon check-in of a Work Order.

- Costing of assemblies is performed when assemblies are checked in.
The Db Console contains an entry File: CostInvoice v6 to update a database stored procedure.
This required update is contained in external files CostInvoice6.sql (MSSQL) or pgCostInvoice6.sql (PostgreSQL)

- Fixed: If an item was a member of regular packages, the assembly packages it was a member of also showed up in the Package Content Selector.

- Fixed: When the Print Prior Identifier Values was chosen in Forms for Orders on a PostgreSQL database an SQL error would arise when producing forms output.

- Fixed: The Quantities function is now available for assembly packages in Items maintenance.

- Fixed: Clicking the checkbox on an assembly component of a work order would receive instead of committing inventory to it.

- Fixed: Assembly package line items in Package As Discount mode are no longer described as a Package Discount in the Work Order window.

- Fixed: On adjustments, FrontLine would sometimes ask if the adjustment was In or Out when it should be obvious from the selection made in the Scan Match window.

- Fixed: An SQL error could arise upon responding Yes to the Add Price Levels to Catalog Item prompt. This bug was introduced in 6.0.0032

- Fixed: Unique identifiers in Order I.Docs were not checked for uniqueness upon entry.

- Added Vendor Number and Vendor Name to Item Lookup. This is the default vendor for an item.

- Added Vendor Number to Inventory Valuation. This is the default vendor for an item.

- Allow the identifier value pick list in the Identifier Document window to be wider when the window is wider.

- Added some discrimination for Assembly Packages to the Package Content Selector and process where the selection is put on line items of the order:

- Fixed: FrontLine would sometimes raise an error TAXSUM:No value for parameter in Forms for Orders when a form had a tax summary section.

- Fixed: Some erratic behaviour when the Customer criteria is set in the Transaction Inquiry window before the first retrieval.

- Added Physical Count to the Maintenance... section of the Welcome window. There is a security context in the Items group for Physical Count.
The Db Console contains an entry Tables for Physicals to add two new tables to the database.

- When the Unit of Measure view of line item quantities is turned off the quantity entered is no longer multiplied by the UOM factor. This prevents rounding problems when the UOM factor produces fractions with many digits after the decimal place.
Example: UOM is a Pack of 12 and you want a quantity of 5 units (not 5 packs) on the line item.

- Fixed: The merging of line items in UOM Fractions analysis was not the same as in Forms for Orders output for Purchase Orders.

- Fixed the fix: Customer Equipment listed in the Scan Match window did not include equipment committed for repair (repair units).

- Fixed: Inventory that was later sold could be omitted from Inventory Valuation when a Date in History was specified.

- In the Inventory Transactions window, changed the "Roll up by Date" option label to "Summarize by Day".

- Fixed: Turning off units of measure display on the line item view affected the display in the UOM fractions list.

- Added unit of measure factor to the UOM Fractions list texts. Ex: Qty 21 = 3.5 PK of 6

- Fixed: Items without a vendor/customer unit of measure could not be entered on an order. This bug was introduced in 6.0.0024

- Fixed: Upon trying to return a line item, FrontLine mistook a special order purchase line for a return when checking whether the line item had already been returned.

- It is now possible to see a read-only view of an order without opening it from the Order Lookup window using the context menu or F4 key.

- Added a UOM Fractions viewer to the line item context menu for purchase orders. This opens a side list showing any fractional totals per Stock#/Location/UOM. As each row is selected in this list the line items with this Stock#/Location/UOM have their Quantity highlighted in yellow. The list is updated when line item quantities are changed.

- Fixed: Upon saving a new customer record, FrontLine would overwrite the Customer Number entered by the user with one generated from the CustomerID.

- Fixed: Customer Equipment listed in the Scan Match window did not include equipment committed for repair (repair units).

- Implemented a 24 Month (2 year) billing frequency. The database field [BillFreq] value is 8192.

- Added an ANY Location option to the Transaction Inquiry (aka Productivity) window.

- Added Unit of Measure awareness to order entry. Line item quantities are shown and entered in the units of measure, unless the Unit of Measure display option is turned off from the line item context menu. Package members are brought in by absolute quantity defined in the package. Note that the Factor value shown in Setup Lists is used for conversion.

- Added Unit of Measure fields to the part numbers table. Here vendor and customer units of measure can be defined per item. The Parts Cross-Reference window has been revised accordingly.
The Db Console contains an entry PARTS.UOM (New in 6.0.0023) to add this field to the database.
It also contains an required update Repair Depot fields in ITEMS (6.0.0023) to add fields that can be maintained now but will be used with the upcoming RA implementation.

- Fixed: Inventory Valuation on a snapshot date in history would miss solo events, and was thus likely to misreport inventory quantity when Date in History was used.

- Fixed: If a package line item quantity was increased, then the order deferred and reopened, then the quantity changed again, the TaxedValue used for tax calculations was incorrect.

- Added a Add To Equipment Set function to the equipment context menu in the Service Contracts window. This function places the unit in the same equipment set as the selected service contract. It is disabled if no service contract is selected, or the unit is already in the same equipment set as the contract, or the unit is currently committed on an order. If the unit was already in an equipment set, this function will move it, keeping the existing price. If the unit was not in an equipment set, it is added with a zero price. The price of such members can be changed in the equipment set.

- The equipment list in the Service Contracts window can now be sorted by identifier or stock number by clicking the column header.

- In receiving, pressing the Enter/Return key with focus on the center grid of the Receive window sends focus back to the Identifier/Quantity input if the expected quantity has not been received yet. This facilitates receiving multiple units with non-sequential identifiers because one has only to press Enter/Return again to identify the next unit.

- Fixed: Members of catalog packages are no longer checked for stock price levels. This was an omission in the related feature from 6.0.0017

- Added SoldToContact for customer orders. View and change this contact using the drop-down in the title of the fourth field of the order header grid. This addition requires a field to be added to the database table.
The Db Console contains an entry ORDERS.SoldToContact (New in 6.0.0019) to add this field to the database.

- Fixed: An SQL error could occur in the Inventory Transactions window when performing a roll up inquiry on MSSQL.

- Fixed: After a special order package was checked in on a purchase order, the package line itself would reappear in auto-gen if the package line item on the customer order was still open.

- It is now possible to change the quantity of a repair unit line item if the item has no identifiers.

- It is now possible to mark units in for repair as defective from the Selected Items list in Line Item Details window. If the unit quantity is greater than one, a quantity prompt appears to allow indication that some (but not all) are defective.

- There are now default costs for items in Inventory Valuation that do not have costs on record that match their costing method. The default cost is selected as found in this order: Average, Last, Standard.

- Fixed: An SQL error could occur (or the input was ignored) upon changing some Item Type flags on existing items using PostgreSQL.

- Fixed: An SQL error occurred upon information retrieval in Productivity Inquiry if an agent was specified before retrieval. This bug was introduced in 6.0.0015

- FrontLine now shows the address note subject when you point at the note icon in the address list in customer, vendor, location, and agent maintenance windows.

- If a package is a catalog item, all members added to an order from the package content selector are marked as catalog line items. Note that if the package is NOT a catalog item, members still carry their own catalog flag to their line items - FrontLine does not remove those.

- Fixed: Units on recurring bills appeared in the Inventory Transactions list.

- Added a roll up feature to the Inventory Transactions window to reduce the number of rows shown. Direct unit identification and tracking are unavailable with roll up. However, opening the order reveals more details about the transaction, including unit identification and tracking in the Line Item Details window.

- Identifier Documents opened from the Service Contracts window can now be edited if the unit is not committed on an order.

- Added a note icon to indicate the existence of an address note in the first column of the address list in maintenance windows.

- Added yellow highlighting to subtractive events in the Inventory Transactions window.

- Added some alternate field name matching for code translation on reports. Note that these are not case sensitive.

- Added Inventory Transactions to the Inquiry group in the Welcome window.

- Fixed: Assigning a vendor to a purchase order using entity lookup failed to assign the current location address to the ship-to of the PO.

- Fixed: Received units that were automatically committed to customer orders by FrontLine at the time of receiving were missing the Sale/Sold flag.

- Fixed: Inventory committed for sale was marked committed for return. This bug was probably introduced in 6.0.0001

- Changed the availability of the Edit List in Forms for Orders. It is now available any time on adjustments and transfers, and on regular purchase orders if something has been received.

- The Company Setting for Order Agent requirement is now elaborated to make this requirement distinct for different order types:

- Fixed: Members of packages entered manually on a PO did not have correct Cost.

- Fixed: Units on Transfer orders that were checked in remained in a Committed status. This fix is in the database procedure CommitInvoice.

- Fixed: If there were blank prices on line items, Forms for Orders raised a database error about NULL in column Price.

- When a Price Level type is changed from Flat Price to a percentage, the base price for that entry is erased.

The Db Console contains an entry File: CommitInvoice procedure 6.0 to implement the top fix above.
This entry requires script files CommitInvoice6.sql (MSSQL) or pgCommitInvoice6.sql (PostgreSQL)

- Fixed: The default vendor was not assigned to a blank PO when the purchase item was selected using Item Lookup. FrontLine would ask the user to identify the vendor for the new PO.

- Fixed: The Purchase Orders list in the Scan Match window included adjustments.

- Fixed: Inventory Valuation would show Services, Charges, Packages, or Miscellaneous items if they had inventory tracking records.

- Fixed: The Customer Transactions link in the Welcome window had reverted to Orders.

- Added an Edit List to Forms for Orders. This form applies to open adjustments and open purchase orders. Like a pick ticket, the data contains line items and committed units. The default form file is EditList.rep and contains the same data elements as a Pick Ticket.

- Improved consistency of flow in the purchase order window between entering a full stock number as a scan code and using item lookup to find the stock number.

- It is now possible to change the price/cost of a package member in the purchase order window. Beware that in Package as Discount presentation mode (where the package appears after all the members) changing a member price this way will not recalculate taxes.

- Fixed: Line items added to a PO from auto-gen with no AP purchase history from the vendor used only Standard Cost. Now they use Last Cost at the location, then Avg Cost at the location, then Standard Cost as last resort.

- Fixed: Incorrect Item Action prompt displayed for adjustments after being used for other transaction types.

- Added a minimum base price for use in percentage calculations on price levels. In the Price Levels window there is now an optional Min Base column that applies to percentage prices. If the base price used for the percentage calculation falls below this minimum then the minimum is used to calculate the percentage instead.
Note that this base price for percentage calculations can be one of: List Price, Std Cost, Last Cost, Avg Cost.

The Db Console contains a script Allow NULL in PRICELEVELS.Price that is necessary to allow no minimum base price for percentage calculations.

- Open special order line items with a non-null TRXIP.SyncSetC value are excluded from purchasing auto-gen.

- Transfer orders and adjustments are tax exempt even if the SELF Customer has no Exempt Code.

- Added an Adjustment Ledger to Forms for Orders. This form applies to adjustments that have been checked through. The default form file is Adjustment.rep and contains the same data elements as the Receiving register.

- Fixed: SQL error using MSSQL when adding a line item to an order. This bug was introduced in 6.0.0001

- Fixed: When no Last Cost was on file from the vendor for line items created from the Generate Purchase Order feature, FrontLine was using the list price instead of standard cost as a fallback.

- Fixed: When using Generate Purchase Order feature for =ALL= vendors, and some items to purchase are available from multiple vendors, it was possible to get a key violation when creating a PO for one of those vendors.

- Fixed: Receiving identifiable items for a line item in multiple separate ranges would create DtlID values outside the assigned sequence, leading to primary key violations later on PK_ITEMDTL.

- Fixed: Clicking off a blank new row onto an existing line item would select the row above the one actually clicked.

- Fixed: In the Identifier Document window, start edit mode on an identifier document with some missing values and the identifiers that were blank appeared in reverse order of identifier setup.

- Added Purchase Orders identifier document template to be distinct from the Customer Orders template.

The Db Console contains a script Expand SUINFO.KeyValue that is necessary to support column persistence for the new fields added in Productivity Inquiry.

- Can override (with confirmation) existing individual context permits in Access Profiles by setting the function class permit.

- Added a Recently Completed special lookup to Order Lookup and Purchase Order Lookup.

- Fixed: Payments were not retrieved correctly for Sales/Service Order forms. This applies to the new feature in 5.6.0027 below.

- In the Equipment Sets window, there is now a Contacts button (or use Ctrl-K) to directly open the contact list for the BillTo address of an Equipment Set.

- In the Generate Purchase Order window, any items with a default vendor qualify the stock number as a part number for that vendor: For that vendor the stock number is considered the part number unless a part number is explicitly defined.
This extends a feature in 5.5.0005 that only applied to vendor catalog items.

- Fixed: Access violation upon printing a form in a terminal services (RDP) session. This bug was introduced in 5.5.0026

- Fixed: Log on to FrontLine, use Order Lookup, log out of FrontLine without closing it, log on again, use Order Lookup again and search by an Order I.Doc field, get an SQL error about a missing UIOL object.

- Return Orders no longer show Pick Ticket, Ship Ticket, or Delivery Ticket in Forms for Orders.

- The Sales and Service orders datasets in Forms for Orders now include PAYMENTS. Beware that these payments have not necessarily been collected.

- Enhanced the Item Billing Prices window, where one can quickly change the price of multiple occurrences of a recurring billing item in equipment sets:

- Fixed: Printer names over 80 characters long could cause an access violation when printing forms. This is the same fix made in 5.5.0241

- Sort output from Forms for Orders for Receiving register by line Location so the form can be grouped by Location.

- If a parameter name for a custom Report ends with ALL (note all caps) then FrontLine will fill in a default value of ALL so the user doesn't have to enter a value.

- Fixed: Selecting an alternate form in Forms for Orders where the file name was modified for display could result in a file not found error.

- Upon copying an item with percentage price levels in Items maintenance, FrontLine now asks if those percentage price levels should be copied too.

- FrontLine now checks Customer PO requirement when the user indicates the order is Ready or Service is complete.

- The PAYMENTS dataset from Forms for Orders is now sorted so that On Account appears last.

- When selecting uniquely identified units in the Scan Match window invoked from the Line Item Details window to fulfill a quantitiy greater than one, one can now use the Shift and Ctrl keys to highlight multiple units in the Unit Details list to be committed to the line item.

- Added committed units to Forms for Orders output for Pick Ticket forms. Note some consequences:

- Fixed: In the Productivity inquiry window the Margin column was miscalculated.

- Fixed: After entering an email address in the address section of a maintenance window an SQL error would result when FrontLine checked if that address was already on file.

- The PurchaseFrom, BillTo, and ShipTo contact email addresses on an order are forwarded to the email created in the Forms for Orders window.

- Added a PriceType to Price Levels to indicate what a price percentage is based on. The options are:

The Db Console contains two new scripts:
PRICELEVELS.PriceType (New column) to add a new field needed.
File: CopyLineItems procedure 5.6 to open the appropriate script to update the CopyLineItems database procedure so that it forwards the CustomerPO to a return order.

- Fixed: SQL error upon saving in Items maintenance window. This bug was introduced in the last release.

- Added a Third Party group to the Welcome window with a Send POs to MOL function that opens Export MOL window. Here one can manage exports of MOL orders by batch, preview the purchase orders, redo any purchase orders, view the export files, open the web site, etc. There are two new company settings for MOL: The MOL Vendor which must be assigned to perform MOL exports, and MOL URL which has a default value that can be changed if necessary.
The Db Console contains a script ORDEREXB (New Table) to create a new table needed.

- The Inventory Received function on the welcome window no longer appears for system administrator.

- FrontLine can now show the customer order where a special order was placed from a purchase order. See the Special Order entry on the line item context menu.

- There is now an ANY Vendor option in the Generate Purchase Order window. This option generates a preview of purchasing needs without choosing a vendor. The vendors found with needed items are listed, as well as a special entry Multi-Vendor Line Items to show those available from multiple vendors. Tentative purchase line items can be removed as usual. The Add To PO function then creates a purchase order for the selected vendor, one at a time.

- Fixed: Access Violation during Exchange processing after selecting alternate unit from Scan Match window.

- Fixed: Package member lines on purchase orders were marked ready as they were as entered manually.

- The default vendor field in Items maintenance now shows the Vendor Number instead of VendorID.

- Many drop-down fields in the maintenance windows have been enhanced to allow free-form entry with value matching as you type. This can improve data entry speed or simply make it easier.

- To facilitate selection of billing frequency and ESet category in recurring billing, there is now a potential bill count preview in the Recurring Billing window. When a date is entered in the Next Bill Up To field in Step 1 a list of billing frequencies and ESet categories appears with potential bill counts. Selecting a row from this list (using double-click or Enter key) puts that bill frequency and category in the Step 1 fields. This list can ignored (set focus elsewhere or Esc key) or redisplayed using F2 (or the small button) at any time during Step 1 when there is a date in the Next Bill Up To field.

- Fixed: An error opening the receiving form would interrupt check-in of receiving.

- Fixed: Editing Lists where the default list had been removed, user assigned key value of a new entry was ignored.

- Fixed: Disappearing description cell text on a purchase order after the Receiving window pops up for unit identification in response to clicking the ready box.

- The LineNoteSubject for Miscellaneous line items is now brought into the ItemDescription field in the datasets in Forms for Orders as it already does on the line item display in the Orders window.

- The VarPrice package member option does not produce a prompt for purchase orders.

- Upon receiving an identifiable member of a package, FrontLine attempts to auto-receive the other members of the package at the same ratio.
Currently only member line items that require no identification are processed.

- Fixed: The price change prompt for package members introduced in the last release could contain undesirable formatting characters.

- Fixed: Identifier values that the user had no permission to read were displayed. They now display the typical stars.

- Added a context menu to the line items in the Generate Purchase Order window.

- Removed the checkboxes on the right side of the check-out/in (invoice) window because they are unused since the introduction of the Forms for Orders window.

- Added the green box around the line item quantity to customer orders to indicate that the quantity committed (and maybe checked out) equals the quantity ordered. This indicator is only shown when the green check mark that indicates a completed and closed line item is absent.

- Added a Receiving form to the Forms for Orders window. This form is used for check-in of receivings on purchase orders. The dataset is like receipts and delivery tickets.

- Added a VarPrice option to package members. This property is set in the Package window. When a member with this property is selected by the user FrontLine prompts for a new price.
The new price entered is coerced to the same sign as the list price.
If negative prices are desired then the item's list price should be negative.

- Added two features in the User Options window that is accessed from the System Users window:

- Fixed: Catalog line items entered on a quote did not get the Special Order flag by default.

- Fixed: Copying an access profile in the Access Profiles was broken. Note that you must change something in the new profile to save it.

- Fixed: In Forms for Orders, when an alternate form was selected from the drop-down list, the check for a PO required by the customer was not performed.

- Fixed: MSSQL db only - entering a large quantity on a line item, resulting in a large line taxed value, could raise an error about NULL not allowed in TaxedValue column. The fix is in a revision of the GetTaxes stored procedure.
The Db Console contains a script GetTaxes v5.6 to revise the stored procedure.

- PostgreSQL db only - increased the data size of some numeric fields to prevent overflows on large line item quantities.
The Db Console contains a script Expand Totals Fields in PostgreSQL to apply these revisions to the database.

- When a catalog item without price levels is manually added to a purchase order, FrontLine asks if it should add price levels to consider this a stocked item.

- Added a Recurring Bills option to the customer Order Lookup window. Recurring Bills are not listed unless this option is on.

- When a Recurring Bill is open in the customer orders window, the Print function now opens the Recurring Billing Output window for that bill.

- Added a PricePercent field to PRICELEVELS to allow pricing relative to list price.
The value stored in PRICELEVELS.PricePercent is a direct multiplication factor: 50% is stored as 0.5
In the Price Levels maintenance window, entering a percentage makes use of this new feature.

- Increased the number of batches shown in the drop-down list for Recurring Billing Output to 72.

- Added two mini-functions to the Print Template Folder field in Locations maintenance: F2 Open (opens the folder to view files). F3 Browse (presents folder tree to select a folder). These functions are only useful for the local location.

- Added an Item Costing window, accessible from Items maintenance using the ellipsis by the Cost field. Here you can:

- Added a CostInvoice database procedure that is used by FrontLine at the conclusion of checkout, and can be used by the connector to bring in cost information from payables.

- Fixed: Transfers would put the unit in its original location instead of the destination.

- Fixed: Changing the Transfer From address on a transfer order resulted in an error that the Field cannot be modified.

- Fixed: When the Item Quantities window opens for an item, it initially shows rows for all and combined locations, which can appear to be duplication. This was a presentation bug.

- Added an Available Anywhere feature to the location selector in the Item Quantities window.

- Two Company Settings for the Scheduler interface were changed in version 1.6 of the scheduler:

- Fixed: In the Order Totals window, repair parts and services were excluded from the cost and margin calculations. Only repair units should be excluded.

- Added an Add All function to the custom Reports window. This function creates entries for all the '.rpt' and '.sql' files found in the template folder, excluding those used by Forms for Orders, to facilitate setup. FrontLine guesses the report group by a prefix in the file name:
AR_=Accounts Receivable
S_=Sales
SE_=Service
P_=Purchasing
F_=Fulfillment
T_=Taxes
R_=Recurring Bills
I_=Inventory
C_=Customers
V_=Vendors
If matched, the prefix is removed to make a default description. The default description also adds spaces where lowercase changes to uppercase.
There is a Report Groups list in Setup Lists.

- In maintenance of customers, vendors, agents, and locations, entries to these fields of an address of a new entity will perform a lookup for an exact match in related fields (without case sensitivity) to minimize accidental entry of duplicates. If the lookup is cancelled the entry can continue:

- Receiving a quantity of an item with no identification: In the Receive window, the Accept function performs the Start function to save a manual step.

- Added order type discrimination to Terms. In the Terms list setup there is a new column for category AR(Receivable)=0 or AP(Payable)=1. This affects drop-down lists and entry validation in customer orders, purchase orders, customer maintenance, vendor maintenance, etc.

- Added a notice when a received line item is put back on hold, explaining that this does not undo receiving.

- Added an option in the Item Quantities window to show Transfers and Receiving separately or merged with the Available quantity.

- Added functions to the Item Quantities window to change the status of inventory:

- Added a selection to the Auto generate function for purchase orders. In addition to the existing auto-gen feature, there is now a Miscellaneous Item Purchases function that opens the Miscellaneous Purchases window where miscellaneous items on customer orders can be reviewed, assigned a vendor and part number, assigned a cost, and added to the purchase order. A note is created for each miscellaneous line item placed on the purchase order with the miscellaneous part number as the note subject. Note that miscellaneous purchases are received like special orders.

- Added a green rectangle around the line item quantity on purchase orders indicating that the quantity received equals the quantity ordered. This indicator is only shown when the green check mark that indicates a completed and closed line item is absent.

- Fixed: When the quantity On Hand of an item was below the Minimum quantity specified for the location, FrontLine failed to consider the quantity On Order in the Generate Purchase Order window when calculating reorder quantity.

- Fixed: Closing the Resource Costs window with unsaved changes did not raise a save prompt.

- FrontLine now lists that Last Cost of an item in the Generate Purchase Order window, and uses this value on the Purchase Order line items. This requires data in the new TRXINVCOST table.

- The Units list in the Item Quantities window can now open the Purchase Order of a Received unit directly.

- Miscellaneous items with no description will show line item note subject as the Scan Code on orders.

- The Receive function is now shown on the lower toolbar of the Purchase Order window.

- Added NoteSubject and TotalQuote to the lookup windows for customer orders and purchase orders.
This addition may throw off your column arrangements in these windows.

- Fixed: Access Violation upon opening the Forms for Orders window. This bug was introduced in 5.6.0009

- Implemented Purchase Order form output in the Forms for Orders window. This introduces "PurchaseFrom" address fields like the existing "BillTo" and so on. Purchase Order forms should normally use "PurchaseFrom" and "ShipTo" addresses.
The output data stream has the same fields as the Sales Order form, but merging of line items is performed with these exceptions:

- Fixed: Access Violation in purchase and customer order lookup. This bug was introduced in 5.6.0009

- Fixed: No OrderID error upon adding auto-generated purchases to a blank PO where you have already assigned the vendor. This bug was introduced in 5.6.0009

- Fixed: The available quantity shown in the Generate Purchase Order window did not include items that had only been received.

- In the VENDORS table, changed ExtRef to VendorNumber. This affects multiple features in FrontLine, and the connector. The Db Console contains a script VENDORS.ExtRef to VendorNumber to change the table in the database. The script syntax varies per server type.

- Added append capability to copying note templates. To append the template note text to the current note text instead of replacing the entire note, hold down the Ctrl key when selecting a template from the list.

- Added capability to print trailer notes on Forms for Orders. Template notes and customer/address notes can be selected per order using the Trailers context menu entry. The notes selected are persistent per order. There is a new dataset available for the forms named TNOTE.
Trailer notes are entirely optional on forms. To add trailer notes to a form, add a TNOTE dataset in the designer, then add a SubReport with Main dataset TNOTE. In this subreport the detail band will list the notes. Headers and/or footers are only necessary if you want some visuals at the beginning/end of the trailer notes.
The trailer notes do not need to be a Child SubReport of any other band.
If later another subreport is added be sure to reposition the trailer notes as the last subreport so they appear at the very end of the output.

- Added a Provisioning option to Service Contracts window.
A provisioning service contract does not provide any repairs coverage, instead it provides other billable services to the units covered.

- Added relative (to present) date entry for date fields. Below are some details on entering dates in FrontLine. Only the relative features (+ and -) are new:
>> The date delimiter is usually a / but can be a - or other character, depending on Windows and FrontLine Company setup.
>> The year can be omitted when entering a date in the current year. Ex, 8/12 for August 12, 2009.
>> Times are optional. When omitted, a date alone refers to midnight.
>> Times can be entered in 12 or 24 hour format.
>> A - alone takes the current date only.
>> -1 takes yesterday's date, -7 a week ago, etc.
>> -.25 takes six hours ago, so a time is included. -2.5 take two and a half days ago, including time.
>> +1 takes tomorrow's date, +7 next week, etc.
>> +.25 takes six hours from now, +1. takes one date from now (including time), +1.5 takes a day and a half from now.
>> Trailing the offset number with an h or H (or hr, hour, etc) makes it hours instead of days, and time is always included.

- Fixed: Repeating a special lookup without reselecting the Search By resulted in a SQL syntax error in PostgreSQL.

- Added three Order Status flags:
Urgent
WIP
Waiting
FrontLine users can toggle these indicators using the drop-down above the Scheduled field in the order header.

- Added basic urgency highlighting to the Order Lookup window. Highlighting is only applicable to orders that are open. The first two are only applicable to orders that have a Scheduled (due) date set. If the order is due within three hours the text is purple, if it is overdue the text is red. Otherwise, if an order is marked Ready the text is green. If an order is marked WIP (in process) the text is blue.

QuickFind in ESETS: Ctrl-F (Find on the context menu) will open a QuickFind box where you can type in a primary identifier value to find it in the customer's equipment sets. FrontLine performs auto-completion here, but if you don't care you can type as if it isn't there. However, it can be handy because you may get the entry long before you have typed in all the characters needed. Note that you do not enter mask formatting here, just the data. For example, no parentheses or hypens in phone numbers, just the numbers. Whenever the value displayed in QuickFind exists in the customer's equipment sets the Ok button is enabled.

In FrontLine 5.4.0032 another addition is a basic "supporting document" link for customers. Presently this links to an Excel spreadsheet for each customer. Here is how it works:

1. The file name FrontLine seeks is CUSTOMERS#.xls where the # represents the CustomerID. Example: For customer 1057 the file name is CUSTOMERS1057.xls and for customer 908000000 the file name is CUSTOMERS908000000.xls

2. FrontLine looks for these files in the print templates folder for your location.

3. When you view a customer in maintenance if FrontLine finds the matching "supporting document" per above then an additional button appears at the end of the button bar with the caption "S/D"

4. Similarly in Orders when you assign the order to a customer, or retrieve an order, this button will appear at the end of the lower button bar if FrontLine finds a file for the customer.

5. When you invoke the function (by clicking the button or using the short-cut key combination) FrontLine attempts to open the file via the Windows file registration. If you have Excel on the computer it should open in Excel. If you have no program that has registered 'xls' files then FrontLine will open the template folder in an Explorer window for you to see the files and try something else.

Future enhancements to this feature could include storing the files in the database (so that all locations can access a single set of files) and having a company setup for the file type instead of the hard-coded 'xls' it uses presently.

The Tax Report window is accessed from the welcome window. The link is in the Inquiry group.

A new form Taxes.rep is required in the templates folder. A sample is provided to get you started. This form is used by the Tax Report window. You do not create a report entry in the custom Reports feature, and there is no need for any SQL in the form because data is supplied by FrontLine.

To create a new report click on the calendar and drag to select a date range. Alternately, a date range can be typed directly into the batch grid in the format date to date, like FrontLine enters it when you select on the calendar. Typing in the dates will also show them on the calendar.

A new batch is indicated by New Batch in the first column of the batch list instead of an actual batch number. When you have entered the date range desired, click the Report function or press F8 to run the report. This will tag tax detail records that meet the date criteria and run a report on them.

You can also Report on an existing batch. In this case no tagging is performed. You are simply reporting on already tagged tax detail records.

In addition to reporting, you can export the tax details using the Export function.

It is possible for a new batch to overlap one or more existing batches. In this case FrontLine will notify you with the message:

FrontLine setup program and db server DLLs: How the installer handles the database server DLLs FrontLine needs.

The FrontLine setup program checks for the required SQL Server DLLs in the system folder (which is usually WIN???\System32) and if they are already there it does not add them to the FrontLine folder. Why? Because their presence indicates an existing installation of SQL Server or its client tools, so better use the existing DLLs.

When you run the setup on a machine running the db server it finds the existing DLLs and does not put them in the FrontLine folder. On most workstations the setup finds no existing DLLs so it puts them in the local FrontLine folder.

If you change the workstations to use the FrontLine folder on the server that has no SQL Server DLLs when you launch FrontLine on these workstations it will fail due to missing DLLs. The solution is to get the DLLs into the server's FrontLine folder. Two ways to accomplish this are:

1. On the server, simply copy them from the system folder to the FrontLine folder, or...

2. Instead of running the setup on the server run it on a workstation (having it install the files on a server folder) and FrontLine setup will add its version of the DLLs since the workstation doesn't have them.

We could elaborate the setup program so that it checks for the DLLs before presenting the setup options, and have an option for including db server DLLs in the installation. If it finds them in the system folder the option will be off, if not it will be on, but since it is an option you can change you could override its assumption and make it put them there anyway.

While that might simplify installs I don't think it is the best because it is preferable to use the DLLs that came with the SQL Server installation. For example, our customer could have SQL 2005 but FrontLine setup includes SQL 2000 versions of the DLLs. Even in the same SQL Server version the client DLLs may be revised in service packs, etc.

FrontLine DSN

The DSN parameter in the INI file is usually in the form ServerName:DatabaseName for example

 ServerA:FLDB

An IP address can be used for the server name. For example

 65.205.161.245:FLDB

FrontLine can use a "Named Instance" of Microsoft SQL Server. In this case replace ServerName with

 ServerName\InstanceName

If the database server is listening on a non-default port (MSSQL default is 1433, PostgreSQL default is 5432) then the port must be specified in the DSN for PostgreSQL. An example DSN specifying port 91919 is

 ServerA/91919:FLDB

For MSSQL the client configuration utility can be used to specify the alternate port.

FrontLine supports UTF-8 encoded databases in PostgreSQL.

The counter base for a workstation is the StationID * one million.
For Station 101, the counters are 101000000(base) + offset.
Example, Station 101 DtlID counter key is 101000002.

All counter values start at the base value for the station and produce one million values before potential collision with the next station. FrontLine warns of impending collisions.

Microsoft SQL Server client notes

The client library FrontLine uses for MSSQL is NTWDBLIB.DLL
which should be in the same folder as FrontLine.exe
Some versions may also require msvcr71.dll

Do not put DBnetlib.dll and other Microsoft client libraries in the FrontLine folder, they can cause mysterious connection problems.

PC Charge and PostgreSQL conflicts

PC Charge Pro puts many dll files in the Windows system folder, a sloppy practice. Among them are three files that conflict with PostgreSQL client libraries: libpq.dll libeay32.dll ssleay32.dll Uninstalling PC Charge removes libpq.dll but the uninstaller may leave the other two. Any of these files will cause FrontLine failures attempting to connect to a PostgreSQL server unless the genuine PostgreSQL client dll files are put in the same folder as FrontLine.exe

Another failure to load libpq.dll

On a clean installation of Windows XP, FrontLine may fail to load libpq.dll to connect to a PostgreSQL database server, despite the presence of files libpq.dll and company. The solution may be to load the appropriate Microsoft Visual C++ Redistributable available for free download from Microsoft.

If you can log on to FrontLine on PostgreSQL without a password then find and edit the file pg_hba.conf to change trust connections to password. Particularly, the entry that refers to connections from the LAN.
In Linux this file is typically in a location like:
/etc/postgresql/8.x/main/pg_hba.conf

Details can be found in this documentation page:
auth-pg-hba-conf.html

ACTDTL contains activation unit identifier links.
ACTIVATIONS contains activation requests.

CALEVENTS contains scheduler events.
CALAGENTS contains scheduler event participants.

CERTIFICATIONS contains certification requirements for working on a model with particular problems.

ESDTL contains equipment set member information.
ESDTL_A is a change log of ESDTL.
ESETS contains equipment set information.

ITEMS contains information about stock items, catalog items, services, charges, packages, etc.

LISTVALS contains custom list values.
LISTVALX as above, with different field requirements.

LOCATIONS contains business location information. Locations are considered entities in relation to addresses.

PROBLEMS contains problem, solution, and peripheral codes associated with units brought in for repair.

PTL contains a simple map of default accounts per location by tender type.
Users can override the default if permitted. The result is saved in PAYMENTS.Account

RECON contains cash drawer reconciliation batches.
RECONDEN contains optionsl reconciliation cash denomination details.

TAXDTL contains tax details per geocode.
TAXGEO contains tax localities in a geocode.

TRX contains completed line item information.
TRXIP contains information about open line items.
TRXDTL links line items to unit details.
TRXRESOURCE contains optional line item resource costs.
TRXLOG is a line item change log.

TRXTAX contains tax details about line items checked out.
TRXTAXIP contains tax details about open line items.

UILISTS contains valid values set up for given identifier.
UISETS contains identifier templates, which are a group of individual identifiers that can be put on a unit.

Note that some "Credit" types may not be used anymore, instead use the sign of Amount.

Name	Hex Value	Decimal Value	Comment
Pending	0	0	Neither invoiced nor completed
Completed	1	1	Closed to further changes
Invoiced	2	2	Has been checked out (customer order) or checked in (purchase order)
Received	4	4	Has been received, partly or fully
Picking	10	16	Print indicator
Billed	20	32	Print indicator
Percent Discounted	40	64
Discounted	80	128
Cancelled	100	256	Quote or Vendor Invoice(AP) has been cancelled
Returned	200	512	Order has been returned via the Returns function (Returns window)
Submitted	400	1,024	Sent to a Third Party, like Motorola. MOL uses ORDEREXB.ExType=101 AvaTax only for Recurring Bills.
Ready/Repaired	800	2,048	Entire Order marked ready (sales) or all repairs completed (service order)
Quote	1000	4,096	Entirely a quote
In Use	2000	8,192	A user has the order open for editing
On Hold	4000	16,384	Cannot commit inventory to, or invoice an order that is On Hold
Voided	8000	32,768
Reprice Pending	10000	65,536	Unpriced line items to be repriced automatically when opened
Retax Lines	20000	131,072	Line item taxes to be recalculated when opened
Auto Commit	40000	262,144	Qualifying unfulfilled line items to be auto-committed when opened
In Transit	100000	1,048,576	User flag
Urgent	200000	2,097,152	User flag
WIP	400000	4,194,304	User flag for work in process
Waiting	800000	8,388,608	User flag to indicate waiting for third party

Name	Hex Value	Decimal Value	Comment
Sales Order	0	0	Sales and Service
Purchase Order	1	1	Purchasing, Receiving, Transfers, and Adjustments
Payment	2	2	Contains a payment on account
?	4	4	Reserved (unused)
Exempt	8	8	Tax exempt order
Non-AR	10	16	Non-AR orders have only charge line items, are exempt from taxes, and excluded from tax reports
Adjustment	80	128	Adjustment, appears with the Purchase Order flag
Short Term Rental	100	256	These orders are left open after check out unless all rentals have been returned
Return	200	512	Return of an entire order
Warranty PO	400	1,024	Warranty Vendor Return Authorization Claim (previously Warranty V-RA) Replacements do not affect item last cost, average cost, or costing layers
Physical	800	2,048	Adjustment created by posting Physical Count
Manufacturer Representative	1000	4,096
Web Order	2000	8,192	Alternate trigger for web updates
Vendor Invoice	4000	16,384	Vendor Invoices do not link to inventory
History	8000	32,768	History Orders can be ignored by some searches
Service Order	40000	262,144	Includes equipment in for Repairs
Third Party	100000	1,048,576	Indicates a PO is a subrental, not a stock purchase, and does not journal Inventory-COS

Name	Hex Value	Decimal Value	Comment
Inventory	0	0	Tracked items. Not a service, charge, or payment
Service	1	1	Services are intangible with no unit tracking
Charge	2	2	Charges are intangible with no unit tracking
Payment	3	3	Payment on account
Recurring Bills	4	4	Line of a recurring bill
Package	8	8	Packages are intangible with no unit tracking Exception: Ready-made assemblies lose this flag
Drop Ship	10	16	Handling code
Special Order	20	32	Handling code
Assemble	40	64	Handling code for work orders
Surplus	80	128	Handling code, no effect in FL
Rental	100	256
Return	200	512	Incoming. Absence is outgoing, ex: a sale
Exchange	400	1,024
Repair	800	2,048	Without next flag, a Part or Service used for a repair
Repair Unit	1800	6,144	Includes the Repair code above
Catalog Item	2000	8,192	Vendor catalog item
Hide Line	4000	16,384	Enables forms to suppress select line items
ZeroPrice	8000	32,768	Used internally by FL
Scheduled	10000	65,536	Usually for a scheduled service
Miscellaneous	20000	131,072	Miscellaneous items depend on Resource Costs in sales and Auto Miscellaneous Item Purchases function on POs
Provisioning	40000	262,144	Provisioning qualifier for Service Contracts
Flat Billing Rate	80000	524,288	Recurring Billing Option
Customer Discount	100000	1,048,576	Due to special customer pricing
Promotional Discount	200000	2,097,152	Due to time-sensitive promotions
Warranty Discount	300000	3,145,728
Package Discount	400000	4,194,304	Occurs in Package As Discount mode
QuantityDiscount	500000	5,242,880	Due to increased quantity
Counter Discount	600000	6,291,456	Applied at time of order entry
Order Discount	700000	7,340,032	Applied to the entire order
% Discount	800000	8,388,608	Qualifies that a discount was entered as a percentage

Name	Hex Value	Decimal Value	Comment
Pending	0	0	Lack of codes 1 and 2 below
Completed	1	1	Closed
Invoiced	2	2	Has been checked out
Received	4	4	Can be partial receipt
Back Ordered	8	8	A line item may be backordered until completely fulfilled
Activated	10	16	Obsolete, may be redefined
Deactivated	20	32	Obsolete, may be redefined
Activation Required	30	48	Obsolete, may be redefined
As Package Member	40	64	Line item is a member of a package here
Discounted	80	128	Line item has an explicit discount line
Returned	200	512	Line item has been returned
Item On Hold	400	1,024	Line was created while ITEM was On Hold
Warranty	800	2,048	Part/Service covered by a warranty
Quote	1000	4,096	Is a Quote
In Use	2000	8,192	Not presently used on line items
Line On Hold	4000	16,384	Line will not be checked in or out unless order is marked ready
Voided	8000	32,768
Future Now	10000	65,536	Line will not be considered a future order
CCC	20000	131,072	Line has Custom Commission Cost override entered
CAA	40000	262,144	Line has Custom Accounts Assigned
Depot Repair	80000	524,288
Imported	100000	1,048,576	Imported line item, ex from Mobile Connect
Urgent	200000	2,097,152	Urgent special orders are highlighted in purchasing
Assigned Price	400000	4,194,304	No automatic discounts because price is from Assigned Price identifier value

Name	Hex Value	Decimal Value	Comment
Available	0	0	* below are also potentially available for sale or rent
Committed	1	1	Committed to an order
Defective	2	2	Can be set manually in Item Quantities
Sold	4	4	Owned by a customer
Received	8	8	Unit was received
In Use	10	16	Can be set manually in Item Quantities
In Shop	20	32	Can be set manually in Item Quantities
Assembled	40	64	Unit was consumed in an assembly
Out of Service	80	128	Can be set manually on a repair unit in Line Item Details
Rented	100	256
Returned	200	512	Returned unit *
Shipped	400	1,024	Unit was shipped by FrontLine Shipping
Transferred	800	2,048	Transferred unit *
To Repair	1000	4,096	Unit in for repairs
Send To Depot	2000	8,192	Units to send (committed) or sent to repair depot
Repaired	4000	16,384	Unit has been repaired *
Adjusted Out	8000	32,768	Adjusted out of inventory
Quarantined	10000	65,536	Should not sell until released
Customer Equipment	40000	262,144	Imported customer equipment
Third Party	100000	1,048,576	Unit belongs to a third party
As Unidentified	200000	2,097,152	Unit was unidentified at commit time
Activated	10000000	268,435,456	Unit has been activated
Rental Unit	80000000	-2,147,483,648	Not used yet

Name	Hex Value	Decimal Value	Comment
Pending	0	0	Not completed, can be voided by user
Completed	1	1
Invoice Printed	2	2
Receipt Printed	4	4
Delivery Ticket Printed	8	8
Ship Ticket Printed	10	16
Payments Only	80	128	Contains only payment on account lines
Warranty	800	2,048	Warranty vendor invoice
Tax Credited	2000	8,192	Taxes on this invoice were later written off
Voided	8000	-32,768	Voided invoices cannot be unvoided

Name	Hex	Decimal
Customer Invoice	0	0
Payment	1	1
Debit Memo	2	2
Credit Memo	3	3
Finance Charge	4	4
Finance Credit	5	5
AR Write-Off	6	6
Write-Off Credit	7	7
Tax Write-Off	E	14
Tax Write-Off Credit	F	15
Retainage	80	128
Retainage Credit	83	131

Name	Hex	Decimal
Vendor Invoice	100	256
AP Credit	101	257
Card Tender	104	260
Invoice Reimbursement	110	272
Invoice 1099	120	288
Invoice 1099 Reimbursement	130	304
Cash Tender	200	512
AP Write-Off	206	518

Name	Hex Value	Decimal Value	Comment
None	0	0	No special attributes
Bill To	1	1
Ship To	2	2
Sold To	4	4
Pay To	8	8
Account	10	16	Not used presently
Purchase From	40	64
Retired	8000	32,768	Address is no longer used by this entity

The first four Contact Preferences are relevant to FrontLine processing,indicating that a contact is used for these purposes.
Note that multiple contacts can have the same preferences,so in some cases FrontLine selects one of them.

Name	Hex Value	Decimal Value	Comment
Invoicing	1	1	Contact is the default for this address as a bill-to on orders, recurring bills, and periodic invoices.
Shipping	2	2	Contact is the default for this address as a ship-to.
Purchasing	4	4	Contact is the default for this address as a purchase-from.
Transfers	8	8	Contact is the default for this address as a transfer-from.

Name	Hex Value	Decimal Value	Comment
Card Issuer	20	32	Vendor is a Card Issuer
Prospect	400	1,024	Automatically removed after check out of this customer's order
Express Repairs	800	2,048	Customers: Repaired equipment can be shipped before marked complete
Corporation	1000	4,096	Affects output format of SSN (nnn-nn-nnnn) vs EIN (nn-nnnnnnn)
No Late Fees	2000	8,192	Exclude this Customer from Late Fee Billing
On Hold	4000	16,384	Transactions for this customer require permission
Closed	8000	32,768

Name	Hex Value	Decimal Value	Comment
No Package Prompt	8	8	Members of this package will not invoke the Package Model Option selector
Drop-Ship	10	16
Special Order	20	32
Assemble	40	64	Indicates an assembly package
Surplus	80	128	Not implemented
Discontinued	100	256	Discontinued items should have substitutes, and require permission to transact
Clearance	200	512
On Hold	400	1,024	Items on hold require explicit permission to transact
Proprietary	800	2,048	Proprietary items can be distinct in Inventory Valuation
Bill Of Materials (BOM)	10000	65,536	BOM package contents are added to an order with no further relationship
Simple PO Cost	20000	131,072	Do not use vendor-specific last cost as default on PO
Distinct PO Lines	40000	262,144	Line items of the same stock# are not combined on PO output to Forms for Orders
Warranty PO	80000	524,288	Item is sent to vendor for warranty claims (previously Warranty V-RA)
Allow Third Party	100000	1,048,576	Item can be special ordered for subrental
Depot During Warranty	400000	4,194,304	Depot repair start and end only apply to units still under warranty
Custom 1	1000	4,096	If labelled, appears in Items maintenance
Custom 2	2000	8,192	If labelled, appears in Items maintenance
Custom 3	4000	16,384	If labelled, appears in Items maintenance

Name	Hex Value	Decimal Value	Comment
Rental Location	100	256	Customer transactions here are rentals instead of sales.
Rental Sale Location	200	512	Secured as a Rental Location but performs non-rental transactions.
No Shipping	400	1,024	Cannot ship out of this location.
Tax On Location	1000	4,096	Sales here are taxed by location address instead of Ship-To.
Ignore Item Default Location	2000	8,192	Sales added to orders in this location ignore item default location.
On Hold	4000	16,384
Closed	8000	32,768

Name	Hex Value	Decimal Value	Comment
Completed	1	1	User has indicated that the job is complete.
Budget Locked	10	16	Changes to job line items no longer change the job budget.
Job Quote	1000	4,096	This is a job quote, not an actual job.
Cancelled	8000	32,768	Job has been cancelled.

Name	Hex Value	Decimal Value	Comment
Optional	1	1	This member group is not required.
Mutually Exclusive	2	2	Only one member in this group can be selected.
Default	4	4	This member is preselected by default.
Var Qty	10	16	The quantity of this member can be changed during package sale configuration.
Var Price	20	32	The price of this member can be changed during package sale configuration.

Name	Value
Flat Price	0
List Price %	1
Std Cost %	2
Last Cost %	3
Avg Cost %	4

Name	Value
Standard	0
Last	1
Average	2
Unit (Actual)	3
FIFO	4
LIFO	5

Setup Name	Hex Value	Decimal Value	Comment
Unique	1	1	Must uniquely identify this unit within a model.
Fixed	2	2	Does not change in the life of a unit.
!Sale	4	4	Required at Sale.
!Recv	8	8	Required at Receiving.
!Exch	10	16	Swapped in an Exchange.
RClr	20	32	Cleared upon Return of unit.
!Rent	40	64	Required at Rental.
!Warr	400	1,024	Required on Warrantied line items.
Hide	80	128	May be Hidden on Forms.
ActP	100	256	Activation property.
RxClr	200	512	Cleared upon Repair of unit.
Case	800	2,048	Values typed in forced to upper case.
Data Type:	Mask F0000	Mask 983,040	Data types in the upper 16 bit word. These are not single bits:
Any	0	0	Free text.
Numeric	10000	65,536	Any number.
DateOnly	20000	131,072	Plain Date.
DateTime	30000	196,608	Date and Time.
AlphaOnly	40000	262,144	Alphabet characters only.
Length	50000	327,680	Length in feet, meters, etc.
Latitude	60000	393,216	Latitude coordinates.
Longitude	70000	458,752	Longitude coordinates.
Airport	80000	524,288	Airport code, uses the AIRPORTS table.

Group	Hex Value	Decimal Value
Sales	0	0
Purchasing	1	1
Fulfillment	2	2
Taxes	4	4
Recurring Bills	8	8
Inventory	10	16
Customers	20	32
Vendors	40	64
Service	100	256
Accounts Receivable	200	512
Accounts Payable	400	1024
Commissions	800	2048
Jobs	1000	4096
General Ledger	4000	16384
Diagnostic	8000	32768
Related to a Customer Order	10000	65536
Related to a Purchase Order	10001	65537
Related to a Periodic Invoice Batch	10010	65552
Related to an Inventory Valuation	10020	65558

Type	Hex Value	Decimal Value
Undefined	0	0
Assets	100	256
Cash Accounts	101	257
Receivables	102	258
Inventory	104	260
Other Current Assets	108	264
Fixed Assets	120	288
Intangible Assets	130	304
Other Non-Current Assets	138	312
Liabilities	200	512
Payables	202	514
Taxes Payable	204	516
Other Current Liabilities	208	520
Long-Term Liabilities	220	544
Equity	300	768
Revenues	400	1024
Revenues - Goods Sold	401	1025
Revenues - Services Rendered	402	1026
Revenues - Other	408	1032
Cost of Sales	800	2048
Cost of Goods Sold	801	2049
Cost of Services Rendered	802	2050
Expenses	900	2304
Corporate Taxes	904	2308
Other Expenses	908	2312
GL Code Only flag	8000	32768

Type	Hex Value	Decimal Value
Customer Invoice	100	256
Customer Deposit	200	512
Customer Cash Receipt	300	768
Customer Recurring Billing	400	1024
Customer Late Fees	500	1280
AR Write-Off	800	2048
AR Tax Write-Off	900	2304
PO Receiving	1000	4096
PO Vendor Invoice	1100	4352
PO Transfers	1200	4608
PO Adjustment	1300	4864
PO Physical Inventory	1400	5120
PO Vendor RA	1500	5376
PO Work Order (Assemblies)	1600	5632
AP Transactions	1800	6144
AP Non-PO	1900	6400
AP Payment Process	1A00	6656
AP Write-Off	1B00	6912
AP Cancellation	1C00	7168
AP Void Checks	1D00	7424
Payroll	2000	8192
Depreciation	2100	8448
Bank Reconciliation	2200	8704
Miscellaneous	2300	8960
Accrual	2400	9216
Beginning Balance	3000	12288

Intent	Hex Value	Decimal Value
History (not set by FrontLine)	0	0
Customer Invoice Income	1	1
Customer Invoice Tax	2	2
Customer Invoice COS	3	3
Customer Invoice Inventory	4	4
Recurring Bill Income	9	9
Recurring Bill Tax	A	10
Recurring Bill Unearned	C	12
Recurring Bill Receivables	E	14
Recurring Bill Payments	F	15
Customer Invoice Receivables	10	16
Customer Invoice Payment Tenders	11	17
Customer Deposit Debit	14	20
Customer Deposit Credit	15	21
Receivable Write-Off	18	24
Overpayments Or Underpayments	19	25
Deposit Tenders	1A	26
Vendor Invoice Inventory Clearing	20	32
Vendor Invoice Discrepancy	21	33
Vendor Invoice Expense	22	34
Vendor Invoice Tax	23	35
Vendor Invoice Payable	24	36
Payable Tenders	28	40
Payable Write-Off	2A	42
Receiving Inventory	2C	44
Receiving Clearing	2D	45
(Misc) Accruals	30	48
(Misc) Accrual Reversals	31	49
Payroll Accruals	32	50
Payroll Accrual Reversals	33	31
Payroll	38	56
Inventory Adjustment INV	40	64
Inventory Adjustment COS	41	65
Physical Adjustment INV	42	66
Physical Adjustment COS	43	67
Miscellaneous	48	72
Inventory Transfer From	50	80
Inventory Transfer To	51	81
Assembly Assemblies	60	96
Assembly Components	61	97
Assembly Intangibles	62	98
Bank Adjustment	70	112
Bank Disparity	71	113
Bank Fees	72	114
Bank Interest Earned	74	116
Bank Ending Balance (informational)	7F	127

Order notes have NoteGrp = OrderID, NoteItm = 0
Line notes have NoteGrp = OrderID, NoteItm = Line
Payment notes have NoteGrp = OrderID, NoteItm = -PLine

Not all group values listed above are currently in use, and there are some special notes with large negative NoteGrp values.

The SMTP mail relay options in FrontLine are set by adding one of these trailing characters to the location mail relay host name: