The "Activity Log" and "Back-office Activity Log" reports are tracking tools that record the actions taken in the corresponding systems of a business. They provide a detailed audit of user actions, allowing administrators to monitor the usage of the application and back-office, identify operational issues, and maintain system security.

ACTIVITY LOG

Note: The registration and movements of a command will only be visible during the first 15 days.

Once inside the activity log, select the desired dates through a custom range. In this same section, you shall also find a series of filters (optional) available to streamline your search. Among them:

1.- Filter by employee

2.- Action:Enter the bug you want to look for.

3.- ID:Detail the ID of our command.

DETAILS FROM EACH BUG

Next, find the name of the bug with its explanation, in order to easily interpret the data registered in a command.

Note: The "%@" icon shown below is a dynamic variable field that changes according to the bug.

• Add default item: (%@) %@: Product added by default to the order.
• Added (%@): Product added to order.
• Added discount (%@): Discount added to the order.
• App background task expired:
• App becomes active:
• App enters background
• Apply discount %@ to %@":
• Apply general discount to each content: General discount applied to the entire order.
• Authorized action:
• Backgorund expired:
• Cannot check if locked by me: %@:
• Cannot lock because it is locked by: %@: Can not save the order because it is blocked by another user.
• Cancel order: The order has been canceled.
• Cancel retry! %@:
• Cashier canceled: Process canceled at the cashier.
• Cashier charge completed: %.2f: The cash load in the cashier has been successfully completed.
• Cashier charge failed: %@: The cash load in the cashier has NOT been completed.
• Cashier charge: %.2f:
• Cashkeeper gives change:
• Change payment method %@ from %@ to %@:
• Change payment method: Modification in the payment method of the order.
• Change table name to %@: Change table name.
• Charge with AEVI Terminal finished ok:
• Charge with AEVI Terminal finished with error: %@:
• Charge with AEVI Terminal:
• Charge with mPOS finished Ok: %@:
• Charge with mPOS finished with error: %@:
• Charge with mPOS: Activated the payment with mPOS.
• Charged with (payment method): Payment method used for the collection of the order.
• Check if locked: Checking if the order is blocked.
• Close without saving yet: Order closed without having saved yet.
• Close: Close order
• Comes from refund of %@:
• Content ids from server not the same as invoice:
• Content ids from server not the same as order contents:
• Delete invoice with id: %@: Elimination of the invoice.
• Delete payment with id: %@: Elimination of payment.
• Delete App\Models\Orders\OrderContent(S):
• Discount removed: Discount removed from the order.
• Duplicate to offline POS:
• Exit kiosk mode: Closed session of the kiosk mode.
• Failed to get %@ Hash:
• Failed to get new invoice id: Unable to obtain a new invoice.
• Failed to link invoice with contents:
• Fast Cash: Quick charge.
• Fast print check: Fast printing.
• Force unlock: Force unlock of a table with an existing order.
• Invoice created: Invoice created.
• Kitchen note printed: %@ to %@: Error printing the note to the kitchen.
• Loaded table:(name of table) with (number of products) items: Table loaded correctly.
• Lock: Order locked
• Login(S): Login to the account.
• Logout(S): Log out of the account.
• Merge with %@: Order merged with another.
• Move content %@ to new table %@: Move the contents of an order to an empty table.
• Move content %@ to table %@: Move the contents of an order to an open table.
• Move from %@ to %@:
• Move to virtual %@: Move a table to virtual.
• No need to save to server, order has not been changed: The order has not been modified.
• No Network, went offline: No connection. Working in offline mode.
• Not locked by me:
• Open cash drawer: Cash drawer open.
• Order emptied: Order without items.
• Order NOT recovered: Order has NOT been retrieved.
• Order recovered: The order has been recovered correctly.
• Presence: autoStart with result number:
• Preview: Preview of the order.
• Print check from preview: Print the ticket from the preview section.
• Print check splited:
• Print check status reverted:
• Print check
• Print copy: Copy
• Print kitchen note:%@: Note print in kitchen.
• Print to kitchen failed: Kitchen printing error.
• Print: Print order.
• Quantity updated for product from quantity to quantity: Modified quantities of the product in the order.
• Refund pressed:
• Removed item: %@ (%@) with quantity: %@: Product removed from the order.
• Reopen and delete invoices: Order reopened and invoices deleted.
• Reopened: Order opened again.
• Reprinted invoice from tables layout: Reprint invoice from the table.
• Retry to save: Retry of order saving.
• Save failed! %@: Error saving the order.
• Save: Save
• Send invoice by mail: Invoice sent correctly by email.
• Set free 2: You have left the order without adding any added product.
• Set free: You have left the order without adding any added product.
• Toggle splited items: Products divided in the order.
• Try to print when locked by another: Trying to print, but the order is blocked by another user.
• Trying to save when still saving ...: Trying to save the order when you are still saving it.
• Unlock: Order unlocked
• Updated status: Update of the data.
• User changed to: %@:
• Went online: Internet connection. You are online again
• WS: Error sending ticket:
• WS: Ticket sent:

Activity log example

You have selected below a couple of orders to analyze your actions.

Follow the steps in this order.

1. Open Table B-23 with 0 products.
2. Add 1 COCA COLA.
3. Add 1 IBERIAN HAM SANDWICH.
4. The device checks if the table is locked.
5. Print to kitchen.
6. Save order on the device.
7. Save order on the server.
8. Display order from the "Preview" screen.
9. Print ticket from that same screen.
10. Print order ticket.
11. Update order status.
12. Display order from the "Preview" screen.
13. Block order.
14. Open Table B-23 with 2 products.
15. Charge it with the payment method "Cash".
16. Close it on the server.
17. Close it on the premises.
18. Save.

This is the process that has a simple order. Now we are going to see a more complex one.

1. Open Table 93 with 0 products.
2. Add 1 BROCKMANS.
3. Add 1 JOHNNIE WALKER RED.
4. The device checks if the table is locked.
5. Print to kitchen.
6. Save order on the device.
7. Save order on the server.
8. Display order from the "Preview" screen.
9. Display order from the "Preview" screen, but from another device.
10. Print account through the "Preview" screen.
11. Run account printing.
12. Update order status.
13. Display order from the "Preview" screen.
14. Block order.

15. Open Table 93 with 7 items.
16. Move a product (virtual ID 614107) to table 60B.
17. Display order from the "Preview" screen.
18. Block order.
19. Open Order 93 with 6 items.
20. The device checks if the table is locked.
21. Save order on the server.
22. Save order on the device.
23. Display order from the "Preview" screen.
24. Print order from the "Preview" screen.
25. Run account printing.
26. Update order status.
27. Display order from the "Preview" screen.
28. Block order.
29. Open Table 93 with 5 products.
30. Add discount called "INVITATION".
31. Print order ticket.
32. The device checks if it is locked.
33. Save order on the device.
34. Save order on the server.

In this order you could see one more case (Discounts, table movement ...).