I know a lot of you guys having hard time following official Gloria integration, I do too. What if I tell you, you don’t need any of those. You can do it with normal Javascript, Actions and Rules. This will give your more control of your flow.
The bad news is this will not be complete tutorial that you will copy and paste and hope it work. I will tell you just the main ingredients you need in order to make it works. You still need to connect the dots to complete the flow.
The most important thing! You must find a way to stop all of your automations that would interrupt the process. For example, When order add to ticket event or entity changed or selected and a lot more… This is only you would you.
You need to know basic Javascript and JSON object.
Install cURL for Windows
Short Outline for now…
Using Start Process Action to run cURL to download your data.
Using Script to read data. Basically, using ReadFromFile() and JSON.parse().
Manipulate your data, you may need to learn about array.push. You will need to filter out items array and keep only item type “option”. The rest remove from item array and keep whatever you need for ex, discount and delivery fee.
Using {CALL:X} to insert data into Change Ticket Entity, Loop Value & Add Order Action.
wait for some more info, as I tried 30 times with Gloria some reason its not working form me. and also I don’t need delivery setup ,as we don’t don’t deliver . this simple setup would be good like unconfirmed . than new ticket status it should done in one step hope bu need script this is what I don’t know how to? also delivery setup is another entity screen we already have tables and customers tickets ijust wanted to use within instead creating new screen.
So this means it is requiring someone to be at the terminal to complete the ticket… it does not actually create a ticket? What if two orders get sent same time? I really can’t see how this would be practical. I can see lots of potential issues happening when orders are coming in.
Well, even automate script still need someone to confirm order. I don’t think it is much different.
For multiple orders, you can write script to handle that right. I using it for a week. I still haven’t had multiple orders come in few seconds apart. So, i don’t know if how my script handle multiple orders correctly. I don’t think I (and most small restaurant) going to have a lot of multiple orders in seconds. Unless they too busy to process order but It only take less then 10 sec. to finish order.
No it does not need someone to confirm order. That is just for the entity screen flow. It is actually creating tickets. I modified my entity screen because we do not deliver. My screen just shows when a new order comes in. It auto prints ticket in kitchen and pops up on my screen when customer arrives to pay we just click on it and pay ticket. The tickets are actually already created in the system and submitted I am just using states for an entity flow.
My kitchen staff if we get busy can just simply tap accept in gloria app for each order… sambapos will print all the tickets there is 0 interaction required by SambaPOS for those tickets until customer comes to pay.
If official script works for you is great, but it doesn’t work for me and you can see a lot of ppl having problem because by nature of SambaPOS, everyone has their own way. It is still better then not be able to use it at all.
I don’t think anyone here is successful using official script. That is not the problem with script but most users lack of knowledge of higher level of script so, they can’t edit anything. That is the real problem.