Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • I information
  • Project information
    • Project information
    • Activity
    • Members
  • Analytics
    • Analytics
    • Value stream
  • Wiki
    • Wiki
  • Activity
Collapse sidebar

webGo Information wiki

  • webGo
  • information
  • Wiki
  • Goqueue
  • Remote queue
  • Diagnostic

Diagnostic · Changes

Page history
Update Diagnostic authored Oct 10, 2018 by Martin Lam's avatar Martin Lam
Show whitespace changes
Inline Side-by-side
goQueue/Remote-Queue/Diagnostic.md
View page @ 58081798
......@@ -12,7 +12,8 @@ It means the socket-receiver for the shop was disconnected.
3. Check the internet communication for the shop
4. If you can remote access the shop. Please restart `socket-receiver` by using the **Support Tools**.
5. Assist a shop staff to check to network
5. Check the URL in ***#1*** again. It should load a correct goQueue.json data
6. Check the hardware or further support
### Please do the checking following by this flow.
---
......@@ -21,5 +22,6 @@ graph LR;
s1[Step 1]-->s2[Step 2];
s2-->s3[Step 3];
s3-- yes -->s4[Step 4];
s3-- no -->s5[Step 5];
s4-->s5[Step 5];
s3-- no -->s6[Step 6];
```
\ No newline at end of file
Clone repository
  • goFTP
    • notes
    • released apk version
  • goMenu
    • BYOD flow
    • error code UCR integration
    • experimental installation for byod
    • symlink static files list
    • uat environment
  • goPOS
    • clear test data before new shop opening
    • daily clearance run before all transactions processed tenren
    • daily clearance run before all transactions processed
    • missing handle update payment
  • goPick
    • error code table
  • goQueue
    • Components Version Compatibility
    • Features and Compatibility
    • Released APK Version
View All Pages