Contents
Overview
Meditator Servers
Meditator Client Information
Combo Store Meditator Client Information
Mediator Client Service Login Setup (Windows 8.1 and up)
Mediator Client Configuration File (aaMediatorClient.ini)
Online Ordering Printer Setup
Connecting Printers
Testing Printers
Troubleshooting Guide
Status Codes
Common Problems and Solutions
Logs
Overview
Online ordering for Aura is done through a cosoft-built integration that has an API that allows third-party developers to send order data from their portals in the form of an XML document. Yumbi's portal is used for all Famous Brands stores, whereas some stores, such as Romans, have their own portal developed by BNRY.
This integration is done using a mediator server and client system. As the name suggests, a mediator server is a ‘middleman’ between the online ordering portal platform and the Aura POS system. When an order is placed through a portal (such as a website, call centre or mobile app) it is submitted to a mediator server, where it is saved in the database. Stores using Aura will have a mediator client, which is a service that runs on the store’s Aura server PC. The mediator client communicates with mediator server and checks if any orders that have been placed for them.
If an order is placed for the store the client will acknowledge that the order is received and tries to process the order. It will then print the Order to the store’s Invoice and Production printers. It then it sends the status (whether successful or not) back to that mediator server, which can then send a success or failure acknowledgement to the portal.
Diagram of the Online Ordering Process
Meditator Servers
Currently there are four instances of the mediator server running. Each mediator server has a different address and will require different login/configuration information before a mediator client can connect to it.
Debonairs
Yumbi (All Other Brands, Combo Stores)
Big Pizza
Testing
Mediator Client installation and Setup
In order for a store to use Yumbi/Online Ordering with Aura, the mediator client will need to be installed. As with any Aura integration or expansion, the Online Ordering setup file will need to be released via Aura Updater. Before it can be released, these steps happen first:
When a store requests to be set up with Yumbi, they will contact Yumbi to sign up and create an account and profile with them, and provide them with all the necessary information.
Yumbi will then send a request to the Aura Development Department to have a profile created with information such as Store ID, name, area, trading times, and menu profiles.
The store is created on the mediator profile and then the relevant setup file is released which will contain the particular store’s configuration and will be different if the store is a Debonairs, Combo, or Other brand.
The Aura Updater will install the client at the store automatically.
Below are the different setups that may get released depending on whether the store is a Standalone or Combo:
Standalone
Online Ordering Base
OnlineOrderingClient-X.X.X.X-Setup.exe
Combo*
Online Ordering Base
Combo Yumbi Installer
OnlineOrderingClient-X.X.X.X-Setup.exe
OnlineOrderingClient-X.X.X.X-Combo-Setup.exe*Combo stores will always have two installers released; one for Debonairs, one for the other brands.
Meditator Client Information
The setup installs to a folder called AuraMEDclient in the C:\Program Files\Alphapos\Aura directory (or C:\Program Files(x86)\Alphapos\Aura on 64-bit OSes). The following can be found in the folder:
Executable: aaMediatorClientSvc.exe
Service Name: AuraMEDClient
GUI: OnlineOrdering.exe
Settings File: aaMediatorClient.ini
Log File: aaMediatorClient.log
The setup will also create a Service called AuraMEDclient in the Services.msc service list (Start > Run > “services.msc”).
Combo Store Mediator Client Information
The Combo Yumbi Installer installs alongside the Base installer in combo stores. The setup installs to a folder called AuraMEDclientYumbi in the C:\Program Files\Alphapos\Aura directory (or C:\Program Files(x86)\Alphapos\Aura on 64-bit OSes). The following can also be found in the folder:
Executable: aaMediatorClientSvc.exe
Service Name: AuraMEDClientYumbi
GUI: OnlineOrdering.exe
Settings File: aaMediatorClient.ini
Log File: aaMediatorClient.log
The setup will also create a Service called AuraMEDclientYumbi in the Services.msc service list (Start > Run > “services.msc”).
AuraMEDclient directory contents
AuraMEDClient/Yumbi services entries in a Combo store
Below are some command line (CMD) commands that can be run to help out with service diagnostics on the store’s server:
Start Service: net start AuraMEDClient
Stop Service: net stop AuraMEDClient
Install Service: AuraMEDClient /install
Uninstall Service: AuraMEDClient /uninstall
Check Service Running: sc query AuraMEDClient
Run in Console Mode (From AuraMEDclient directory): aaMediatorClientSvc.exe /console
Mediator Client Service Login Setup (Windows 8.1 and up)
For stores running Windows 8.1/10/Server 2012, access permissions can often prohibit proper communication between the mediator client and printers, or stop the service from operation completely. For this reason it’s recommended to set the service to log in as the Aurauser user. To do this take the following steps:
Open the Services windows (Start > Run > “services.msc”)
Double-click the AuraMEDClient service
Click the Log On tab
Select This Account and enter Aurauser as username with aurauser as password.
Click OK and then restart the service.
NB: This will need to be repeated for each instance of the service if the store is a combo store.
Mediator Client Configuration File (aaMediatorClient.ini)
The settings file is a .INI file which can be used to configure the service.The settings file contains the following information:
ServerURL
The URL of which Mediator Server the service is connecting to.
(As per the list of Mediator Servers above)
StoreID
The AEC StoreID for the store
AuthUser
The username used to connect to the Mediator Server
AuthPassword
The password used to connect to the Mediator Server
FunctionHost
Used by GUI to connect to the service
FunctionPort
Used by GUI to connect to the service
ConnectToExternal
Flag to determine whether to connect to a Mediator Server
This information will come Pre-Configured for the store from Aura Updater. If the information is incorrect you may correct it, but make sure to inform the Development Department.
Configuration file contents
NOTE:
if you are unsure if the INI file is correct, follow these steps to reload it from AES:A new aaMediatorClient.ini file will be inserted automatically with the store settings on AES.
- Uninstall the mediator using the Uninstall exe in the AuraMEDClient folder
- Rename/Remove the aaMediatorClient.ini
- Run Aura Updater and let it reinstall the mediator service and settings.
Online Ordering Printer SetupAfter the Online Ordering/Yumbi client is installed, a new till called **ONLINEORDERING** is added to the Aura system, which will process orders coming through from Yumbi.
Printers will need to be set up on this till for Online Orders to be able to print out orders. The store will first need to choose which invoice printer and production printer they want the order to print out from. These printers need to be shared and accessible from the SERVER computer.
Connecting Printers
All Aura computers should have an AURAUSER user account. This account is important as it’s what the Online Ordering service must log in as to connect to the system’s printers. Use the following steps to connect printers for Online Ordering:
Log Off the current user on the server
Log in as Aurauser. The aurauser account is hidden by default, so you may need to use CTRL+ALT+DEL to be prompted with a manual user login screen. Use the password aurauser. NB: Do not give out the Aurauser username and password to customers.
When logged in, use the Run command to network access the machine that’s hosting the printer (e.g if the till machine is MAIN1, type \\main1). The computer’s shared printers and folders will be visible.
Right-Click the printer and click Connect…
Open Printers and Faxes (or Devices and Printers) and confirm that the connected printer shows (i.e Invoice on Main1 and Kitchen)
Once the necessary printers are connected, open Invoicing access Settings. Click Select Till and select the online ordering till (**ONLINEORDERING**).
Open the Printer Setup tab and set the Invoice and Production printers as a normal till using the printers you connected.
Example printer configuration
Testing Printers
You will need to confirm that the service can properly connect to the printers you’ve configured. While still logged in as Aurauser, take the following steps to test your printers:
Navigate to the Aura directory (C:\Program Files\Alphapos\Aura)
Right-click the AuraMEDClient folder and select Aura Command Here…
In the console, type net stop AuraMEDClient to stop the mediator service. If the service fails to stop you can kill the process in Task Manager.
Type aaMediatorClientSvc.exe /console. This will launch the service in Console Mode.
The console will display the background processes that run when the service is active, including connecting to the printers. See the below for the result when printers connect True:
Troubleshooting GuideOnline orders that fail are logged on the mediator server and can be viewed here:
Debonairs: http://admin.debonairs.auraonline.co.za/med_user/login?url=
Yumbi: http://admin.yumbioo.auraonline.co.za/med_user/login?url=
Romans: http://admin.romansoo.auraonline.co.za/med_user/login?url=
An order in progress will display a status code of 0-4 depending on what stage of the ordering process it’s at. When an order fails, it provide a status code 93-98 which indicates where the problem lies.Status Codes
0
Order Outstanding
1
Order Acknowledged by Store
2
Order Processed by Store
3
Manual Processing Started
4
Manually Processed at Store
91 93
Item does not exist at store or is set inactive
94
Order has become stale: 5 minutes has elapsed since order was placed
95
Connection problem to the database at the store
96
The order XML is invalid and cannot be processed
97
There are no Line Items for the order
98
The order failed to print at the store
Common Problems and Solutions
The store is offline on the Mediator
Use AESWeb to check the current status of the store on its Mediator server: http://support.cosoft.co.za/solution/articles/1000208666
When you have the status you can check the following:
Opening/closing times: Check that the current time is between the "Opening Time" and "Closing Times".
Store has set themselves offline: Check that the current time is less than the "Closing Time Today".
Is the store connected to the Mediator: Is the "Is Online" true. When was the "Last Ping" - if it is not current then there could be the following problems:
The service is not running at the store.
The service is being blocked from contacting the server.
The store has internet problems.
Error 98 - The order failed to print at the store
Check that printers have been setup in Aura Printer Setup screen for the Online Ordering virtual till.
Check that the printers that have been setup for the Online Ordering virtual till have the "Direct To Port" option that matches the driver.
Printers that have been setup have been created/connected to for the "aurauser" user.
Check that the till the printer is connected to also has an administrative “aurauser” account.
Check the log to see what the actual error is regarding the printing.
After setting up the printers, the AuraMEDClient (or AuraMEDClientYumbi) service needs to be restarted.
Store is on an incorrect/older version
Most likely there is a problem with the AuraUpdater that it is unable to update the software at the store
Check the Task Manager to see if AuraUpdater.exe is currently running. If so, end the process and start again.
Run the Updater from BackOffice or via the command line: "AuraUpdater.exe SHOW" to check if there are any error messages coming up.
Check the Aura POS Update log file for problems.
There could be permission problems on the Aura or AuraMedClient folders.
Error 93 - Item does not exist at store or is set inactive
This means that one of the items in the order is not available at the store
Goto http://mediator.cosoft.co.za/rest/store/ordercheck (or the correct Mediator URL)
Search for the order
The "StatusText" column will contain the item(s) that are not available at the store
Connect to the store
Check that they have the specified item
Check that the item is active
Check that they are on the correct menu version
Error 99
This is general error when saving/processing an order at a store
Go to http://mediator.cosoft.co.za/rest/store/ordercheck (or the correct Mediator URL)
Search for the order
The "StatusText" column will contain the error regarding the order.
Connect to the store.
Check the log file to see exactly where the occurred.
Log this as Helpdesk issue with the log attached.
Online Orders print the wrong currency
Log into Windows as aurauser, change the Regional Settings in the control panel to Rands, and restart the service.
If the above doesn't work, open a registry editor window (Start->Run->regedit).
Under HKEY_USERS, expand each SID key (The most likely ones to be causing the problem are. S-1-5-18, S-1-5-19 AND S-1-5-20), expand Control Panel, and click on International.
Change the value for sCurrency to "R" for each SID, and restart the AuraMedClient service.
Check the regional settings on the aurauser account of the till the printer is connected to.
Other Diagnostic options
Internet connectivity issues
If the internet is down, the service will not be able to communicate with the server. The store will need to contact their ISP for internet troubleshooting.
Temporarily offline due to failures
As a safety mechanism, the service takes the store offline in the event of multiple failed orders. In order to resolve this, the cause of the order failure must first be addressed. Once it is fixed and a test order is sent through, the store goes online again.
Outside of trading times
Stores are taken offline outside of the trading times specified on the mediator server. If the store changes their trading times, they need to notify us to adjust their trading times on the Mediator server.
Logs
Online Ordering has extensive logging, every time an order is processed or any other action is performed by the mediator service it gets logged.
The log file is named:
aaMediatorClientSvc.log
The log file can be found in the installation directory
64bit: C:\Program Files (x86)\Alphapos\Aura\AuraMEDClient
32bit: C:\Program Files\Alphapos\Aura\AuraMEDClient
The following is a general example of what the log looks like after logging some activities:
20150625 09052925 info [TaaMEDClientPrinterAdmin.TestPrinters] Printer [COM4]: True
20150625 09052925 info [TaaMEDClientPrinterAdmin.TestPrinters] Printer [COM4]: True
20150625 09052925 info [TaaMEDClientPrinterAdmin.TestPrinters] Printer [COM4]: True
20150625 09053320 info [TaaMediatorClientAdminThread.DoPing] Pinging the server
20150625 09053360 info [TaaMediatorClientAdminThread.DoPing] Ping response : Ping|Store: 60507|LastPing: 20150625 09:05:01
20150625 09053905 info [TaaMediatorOutstandingThread.GetOutstanding] Found 1 orders outstanding
20150625 09053905 info [TaaMediatorOutstandingThread.GetOutstanding] Looking for : {806A7A81-081B-E511-B093-BC764E04E8E6}
20150625 09053905 info [TaaMEDClientLists.FindOrder] Looking in New Orders : {806A7A81-081B-E511-0003-BC764E04E8E6}
20150625 09053905 info [TaaMEDClientLists.FindOrder] Looking in Acknowledged Orders : {806A7A81-081B-E511-0003-BC764E04E8E6}
20150625 09053905 info [TaaMEDClientLists.FindOrder] Looking in Processed Orders : {806A7A81-081B-E511-0003-BC764E04E8E6}
20150625 09053905 info [TaaMEDClientLists.FindOrder] Looking in Erorr Orders : {806A7A81-081B-E511-0003-BC764E04E8E6}
20150625 09053905 info [TaaMEDClientLists.FindOrder] Looking in Retry Orders : {806A7A81-081B-E511-0003-BC764E04E8E6}
20150625 09053905 info [TaaMediatorOutstandingThread.GetOutstanding] Adding order : {806A7A81-081B-E511-0003-BC764E04E8E6}
20150625 09053910 info [TaaMediatorAcknowledgeThread.ProcessAcknowledge] There are orders to be acknowledged
20150625 09053912 info [TaaMediatorOutstandingThread.GetOutstanding] Still Alive
20150625 09053912 info [TaaMEDClientLists.SendOrder] Sending status [1] to: http://mediator.cosoft.co.za/rest/order/update/{806A7A81-081B-E511-0003-BC764E04E8E6}
20150625 09054018 info [TaaMediatorOutstandingThread.GetOutstanding] Found 1 orders outstanding
20150625 09054018 info [TaaMediatorOutstandingThread.GetOutstanding] Looking for : {806A7A81-081B-E511-0003-BC764E04E8E6}
20150625 09054018 info [TaaMEDClientLists.FindOrder] Looking in New Orders : {806A7A81-081B-E511-0003-BC764E04E8E6}
20150625 09054018 info [TaaMediatorOutstandingThread.GetOutstanding] Order already exists
20150625 09054039 info [TaaMEDClientLists.SendOrder] Result: True | Response from server : Updated it
20150625 09054039 info [TaaMediatorAcknowledgeThread.ProcessAcknowledge] Updated status, moving to Acknowledged
20150625 09054043 info [TaaMediatorProcessThread.ProcessOrders] Processing Order : {806A7A81-081B-E511-0003-BC764E04E8E6}
20150625 09054046 info [TaaMediatorProcessThread.ProcessOrders] Checking OrderXML
20150625 09054046 info [TaaMediatorProcessThread.ProcessOrders] Checking if expired
20150625 09054046 info [TaaMediatorProcessThread.ProcessOrders] Converting XML to Object
20150625 09054046 info [TaaMediatorProcessThread.ProcessOrders] Calling SaveInvoice
aaMediatorClientSvc.log documented log activities
Here is a breakdown of a log line:
20150625 Is the date for when the log was saved.
Format: YYYYMMDD (YYYY = Year) (MM = Month) (DD = Day)
09052925 Is the exact time when the log was saved.
Format: HRMMSSMS (HR = Hour) (MM = Minutes) (SS = Seconds) (MS = Miliseconds)
[TaaMEDClientPrinterAdmin.TestPrinters] Printer [COM4]: True - States the finer detail related to the current activity that is logged.
In this specific case we can break the message down to the following:
TaaMEDClientPrinterAdmin.TestPrinters - Is testing the printer
Printer [COM4]: True - Printer is connected to COM port 4 and is responding
The following log shows details that gets logged when an order is placed
20150625 09113201 info [TaaMEDOnlinePaymentLogic.ParseFromOrderXML] Starting
20150625 09113201 info [SaveInvoice] Checking which printers to use
20150625 09113201 info [SaveInvoice] Printing invoice
20150625 09113201 info [SaveInvoice] Impersonating for print
20150625 09113201 info [aaImpersonateUser] Logging on
20150625 09113201 info [aaImpersonateUser] Load user profile
20150625 09113203 info [aaImpersonateUser] Impersonate the user
20150625 09113203 info [PrintInvoice] Starting
20150625 09113206 info [PrintInvoice] Getting Production Printers
20150625 09113206 info [PrintInvoice] Adding LineItems
20150625 09113206 info [PrintInvoice] Loading Payment Details Descriptions
20150625 09113206 info [PrintInvoice] Loading Payment Details List
20150625 09113207 info [PrintInvoice] Testing Invoice printers
20150625 09113207 info [PrintInvoice] Printing to Invoice Printers
20150625 09113207 info [TPrintInvoice.Print] Print Direct to port
20150625 09113207 info [TPrintInvoice.PrintNarrowInvoice] Starting
20150625 09113218 info [PrintInvoice] Printing to production printers
20150625 09113218 info [TPrintInvoice.Print] Print Direct to port
20150625 09113218 info [TPrintInvoice.PrintNarrowInvoice] Starting
20150625 09113222 info [SaveInvoice] Reverting after impersonate
20150625 09113222 info [TaaMEDClientLists.SendOrder] Sending status [2] to: http://mediator.cosoft.co.za/rest/order/update/{607E3C52-091B-E511-0003-BC764E04E8E6}
20150625 09113355 info [TaaMEDClientLists.SendOrder] Result: True | Response from server : Updated it
20150625 09113355 info [TaaMediatorProcessThread.ProcessOrders] Updated status on server, moving to processed
20150625 09113938 info [TaaMediatorClientAdminThread.DoPing] Pinging the server
20150625 09114015 info [TaaMediatorClientAdminThread.DoPing] Ping response : Ping|Store: 60507|LastPing: 20150625 09:11:07
20150625 09122714 info [TaaMediatorAcknowledgeThread.GetAcknowledged] Still Alive
20150625 09123058 info [TaaMediatorClientAdminThread.CheckDBConnection] Checking DB Connection now
20150625 09124042 info [TaaMediatorClientAdminThread.DoPing] Pinging the server
20150625 09124120 info [TaaMediatorClientAdminThread.DoPing] Ping response : Ping|Store: 60507|LastPing: 20150625 09:12:08
20150625 09124122 info [TaaMediatorOutstandingThread.GetOutstanding] Found 1 orders outstanding
20150625 09124122 info [TaaMediatorOutstandingThread.GetOutstanding] Looking for : {907C337D-091B-E511-B093-BC764E04E8E6}
20150625 09124122 info [TaaMEDClientLists.FindOrder] Looking in New Orders : {907C337D-091B-E511-B093-BC764E04E8E6}
20150625 09124122 info [TaaMEDClientLists.FindOrder] Looking in Acknowledged Orders : {907C337D-091B-E511-B093-BC764E04E8E6}
20150625 09124122 info [TaaMEDClientLists.FindOrder] Looking in Processed Orders : {907C337D-091B-E511-B093-BC764E04E8E6}
20150625 09124122 info [TaaMEDClientLists.FindOrder] Looking in Erorr Orders : {907C337D-091B-E511-B093-BC764E04E8E6}
20150625 09124122 info [TaaMEDClientLists.FindOrder] Looking in Retry Orders : {907C337D-091B-E511-B093-BC764E04E8E6}
20150625 09124122 info [TaaMediatorOutstandingThread.GetOutstanding] Adding order : {907C337D-091B-E511-B093-BC764E04E8E6}
20150625 09124126 info [TaaMediatorAcknowledgeThread.ProcessAcknowledge] There are orders to be acknowledged
20150625 09124126 info [TaaMEDClientLists.SendOrder] Sending status [1] to: http://mediator.cosoft.co.za/rest/order/update/{907C337D-091B-E511-0003-BC764E04E8E6}
20150625 09124129 info [TaaMediatorOutstandingThread.GetOutstanding] Still Alive
20150625 09124241 info [TaaMediatorOutstandingThread.GetOutstanding] Found 1 orders outstanding
20150625 09124241 info [TaaMediatorOutstandingThread.GetOutstanding] Looking for : {907C337D-091B-E511-0003-BC764E04E8E6}
20150625 09124241 info [TaaMEDClientLists.FindOrder] Looking in New Orders : {907C337D-091B-E511-0003-BC764E04E8E6}
20150625 09124241 info [TaaMediatorOutstandingThread.GetOutstanding] Order already exists
20150625 09124255 info [TaaMEDClientLists.SendOrder] Result: True | Response from server : Updated it
20150625 09124255 info [TaaMediatorAcknowledgeThread.ProcessAcknowledge] Updated status, moving to Acknowledged
20150625 09124260 info [TaaMediatorProcessThread.ProcessOrders] Processing Order : {907C337D-091B-E511-0003-BC764E04E8E6}
20150625 09124260 info [TaaMediatorProcessThread.ProcessOrders] Checking OrderXML
20150625 09124260 info [TaaMediatorProcessThread.ProcessOrders] Checking if expired
20150625 09124260 info [TaaMediatorProcessThread.ProcessOrders] Converting XML to Object
20150625 09124260 info [TaaMediatorProcessThread.ProcessOrders] Calling SaveInvoice
20150625 09124260 info [SaveInvoice] Starting
20150625 09124260 info [SaveInvoice] Checking DB connection
20150625 09124260 info [aaMatchCustomer] Matching on telephone : 0733333333
20150625 09124300 info [SaveInvoice] Updating Customer with Delivery information
20150625 09124302 info [aaGetStreetLink] Found existing Street : 3389
20150625 09124302 info [aaUpdateCustomer] Updating Customer details for : 0733333333
20150625 09124304 info [SaveInvoice] Getting Attend record for Online Orders
20150625 09124304 info [aaCheckMobileUser] Checking for Mobile user
20150625 09124306 info [aaAttendForEmployee] Getting Attend for : ZZZ
20150625 09124307 info [SaveInvoice] Converting the lineitems from HOCode to Code
20150625 09124307 info [SaveInvoice] Converting from DST2L => DST2L
20150625 09124308 info [SaveInvoice] Converting from L128 => L128
20150625 09124308 info [SaveInvoice] Converting from EL24 => EL24
20150625 09124308 info [SaveInvoice] Converting from EL24 => EL24
20150625 09124308 info [SaveInvoice] Checking that lineitems exist in the database
20150625 09124315 info [ValidateOrderTotals] Invoice Total : 193.60
20150625 09124315 info [ValidateOrderTotals] Line Totals :-163.60
20150625 09124315 info [ValidateOrderTotals] Discount Totals :-0.00
20150625 09124315 info [ValidateOrderTotals] Gratuity : 30.00
20150625 09124315 info [ValidateOrderTotals] Diff : 0.00
20150625 09124315 info [GetNextInvoiceNum] Getting next Invoice and OrderNum
20150625 09124316 info [GetNextInvoiceNum] InvoiceNum: 147 | OrderNum : 3
20150625 09124316 info [TaaMEDOnlinePaymentLogic.ParseFromOrderXML] Statrting New Payment Parsing
20150625 09124316 info [SaveInvoice] Removing old invoice data
20150625 09124316 info [aaRemoveOldData] Removing items for InvoiceNum : 147
20150625 09124321 info [SaveInvoice] Inserting into the database
20150625 09124328 info [SaveInvoice] Inserting line items
20150625 09124331 info [SaveInvoice] Distributing Discounts to Lineitems
20150625 09124331 info [aaInsertLineitems] Inserting LineItems for Invoice : 147
20150625 09124331 info [aaInsertLineitems] SQL : EXEC InsertLineItem 147, 1, '20150625 09:05:33', 1.0000000000, 'DST2L', '2L STONEY', '2 Litre', 23.9000000000, 23.9000000000, 0.0000000000, 0.0000000000, 'N', 0.0000000000, 0, 0, -1, 0, 0, '', 0, 0.0000000000, 20.964912280701753400, 14.0000000000, 0.0000000000, 0.0000000000
20150625 09124334 info [aaInsertLineitems] SQL : EXEC InsertLineItem 147, 2, '20150625 09:05:33', 1.0000000000, 'L128', 'CHICKEN TRIPLE DECKER', 'Lrg Piz', 109.9000000000, 109.9000000000, 0.0000000000, 0.0000000000, 'N', 0.0000000000, 0, 0, -1, 0, 0, '', 0, 0.0000000000, 96.403508771929836000, 14.0000000000, 0.0000000000, 0.0000000000
20150625 09124334 info [aaInsertLineitems] SQL : EXEC InsertLineItem 147, 3, '20150625 09:05:33', 1.0000000000, 'EL24', 'Mozzarella Extra ***', 'Lrg Piz', 29.8000000000, 29.8000000000, 0.0000000000, 0.0000000000, 'N', 0.0000000000, 0, 0, 2, 0, 0, '', 0, 0.0000000000, 26.140350877192982900, 14.0000000000, 0.0000000000, 0.0000000000
20150625 09124334 info [aaInsertLineitems] SQL : EXEC InsertLineItem 147, 4, '20150625 09:05:33', 1.0000000000, 'EL24', 'Mozzarella Extra ***', 'Lrg Piz', 0.0000000000, 0.0000000000, 0.0000000000, 0.0000000000, 'N', 0.0000000000, 0, 0, 2, 0, 0, '', 0, 0.0000000000, 0.000000000000000000, 14.0000000000, 0.0000000000, 0.0000000000
20150625 09124335 info [SaveInvoice] Setting ADC upload for lineitems
20150625 09124335 info [aaSetADCUpload] Updating ADCUpload for : 147
As you can see from the above log example, every detail of the order is captured. Including details about data uploads/downloads. Line Items, printer functions, Invoice functions etc.
Any issue that might be caused by an Online Order can be found in the log, it’s imperative for support personnel to read log files, as they are there to reveal the issue or at the least help with narrowing down the problem.
A PDF version of this guide can be found attached below.
