Wow that is amazing. The last example you gave with the marketing really made my jaw drop just thinking about it. That’s something typically restricted to just big business with custom systems. The fact that it could be integrated into SambaPOS is amazing.
@Jesse I have to say the real amazing thing is the open source community. We can access any info through ready to use libs crafted by amazing people. I wish I could keep SambaPOS open source…
1 Like
You may not be able to keep it open source… but its very close to it. And it behaves similar which is amazing as well.
I agree open source is awesome. I always support it whenever I can.
1 Like
I really like where all this is going!!!
@Emre, I think that at this point SAMBA v4 is better than open source, why?, as an old programmer, I really am not in the mood of starting to learn c# or any other language, but as you can see, I am really eager to learn how to use constraints or rules or actions… I know these are two different things, but, consider this… maybe in a near future SAMBA grows enough to have some kind of scripting language. Holly grail of SOFTWARE. Imagine combining existing features like rules, actions, triggers with some sort of scripting…
G.
2 Likes
Has anyone setup waiters as Entities yet? Trying to wrap my head around this. What will it do to their printout at the end of their shift? In my restaurant every waiter is responsible for their own cash out. If I do this does that mean they have to log in as their user and again as their entity every time they start a new table? Is there any tutorials on how to accomplish this? Can I use custom reports to create a new sales report for this??
The User can be associated with the Waiter Entity automatically upon login using Automation, so there is no need for entering a PIN twice.
Create an Action of the Type Load Entity.
Create a Rule for the Event called User Login, and within that Rule, fire the Load Entity Action using [:UserName] as a parameter to the Action.
To assign the Waiter to the Ticket, create an Action of the Type Change Ticket Entity.
Create a Rule for the Event called Ticket Created, and within that Rule, fire the Change Ticket Entity Action using {:CURRENTUSER} as a parameter to the Action.
Yes, you can use Custom Reports to pull just about any data your heart desires. That said, the Work Period Report already shows Sales based on Users.
What is the process to create the entity type “waiters”. Entities make sense to me, however it is still a new concept I don’t understand how it appears in your drop down menu of “Entity Type Name:”?
Create new Entity: Manage > Entities > Entity Types
Entities can be anything you want: Customers, Tables, Employees, Suppliers, Deliverers, Waiters, Hotel Rooms, etc
I think this request (transferring tables between users) keeps popping up pretty frequently. What are the chances we can have this request as a build-in option of SambaPOS. It is a core feature for most restaurant POS systems.
I understand this can be accomplished using Entities, but it is not as end-user friendly. A manager(or any non technical person) can create a User, but it is much harder to setup Users and Entities.
Thank you,
What makes you think this is not a core feature for SambaPOS? What do you mean by core feature?
By core I meant as a built-in feature without additional configuration. We should be able to change tickets from one user to another without creating Entities.
Similar to “Change table”
Thank you in advance.
You realize tables are entities and change table is configured with entities? What makes samba unique is the fact that there are few default built in features dictating how we use the pos. I personally do not want this as a hardcoded feature because I would not use it and I do not want it in my pos screen.
What attracts me to sambapos is how its configured. If people would get past the stigma of it being different and really spend some time to study it they would find it is not hard to do these things
I want as many people using samba as possible. But I would not want samba to change its identity just to be like other pos for the sake of easy. There is a small drawback to this type of model and that’s the fact that a few people who are only interested in turnkey solutions may get disappointed. But eventually somebody will offer samba preconfigured as a service to meet these needs.
We have to realize that samba is different and it by design will move away from hard coded features. But in v5 @emre has addressed this with an upcoming feature that will auto configure shared more advanced features for you. And we as a community will be able to share these configurations. No its not the import tool this new feature is different and can give you options during the setup.
2 Likes
I understand tables are entities and I also understand SambaPOS is mature whereby this feature can be configured if you know what you are doing.
I love the way Sambapos works. The only reason why I am asking is because it keeps being requested even though we have had multiple discussions in the last twelve months the way SambaPOS works.
Thank you @Jesse, you are a great asset in these forums.
Maybe what we need is someone in the community to take enough interest to share their configuration on this. Our focus should be strengthening the community and helping it grow. I have not attempted it yet because I do not need it but maybe I will sometime.
Totally agree. 
It is a needed feature if you have over 8 server per shift. It will be even better if User Entities are created automatically when a User is created. Just my two cents!
We almost have the ability to do that now. All we would need is to capture the event of user created.
I agree, it could be built in to a DB Tools Import file.
Still, there is no way to configure it exactly and specifically for every Users need. Perhaps with support from YAML files that will be available in V5.
Exactly. The real point is that different people do things differently. So we tend to spend time on helping people help themselves by trying to teach them how SambaPOS works. That way they can build out whatever feature they want, completely to their tastes.
There is nothing special about this particular request for a built-in feature. It is not a Topic that comes up any more often than most other Topics.
What I tend to do, is that if someone has an idea on something they want to see, and I perceive it as being useful to me, I will build it, trying to make it as simple and flexible as possible. But it is the teaching process through the Tutorial that is the real value for others (and myself) - not the canned solution (even in the form of DB Tools).
This is the power of SambaPOS. It isn’t about building in features that only a percentage of people want.
2 Likes
Thanks @QMcKay I did this initially, however it didn’t appear at the drop down. I agree with comments below that I like the flexibility of SambaPOS its just a little of a learning curve. I have to put this system together for service in 2 months so I’m sure I’ll have more questions. Thank you all for all the great support, everyone.
Joe
@QMcKay - I followed your screenshots and I don’t see the Employee or Waiter above the ticket when creating or opening a new table in POS. Other than creating these two actions, two rules, and a single role type is there anything I’m missing?
Ultimately I’m trying to incorporate:
(1) Waiter is assigned to ticket upon creation based upon their user/pin login.
(2) Being able to transfer waiter entity to new user based when their shift is ending.
(3) Being able to print out a report with their sales totals after transferring waiter entity and cash out their till.
Thanks,
Joe
Be sure you have checked the Can update null entity for the Change Ticket Entity action
What do you mean by this? Every time a user logs in it will assign that user as the Entity on Ticket Creation. What are you transfering?
In his example the user IS the Entity. There is no Employee and Waiter they are both the same.
I still do not understand what you mean by transferring waiter entity. What and where are you transferring it?