Not in this version. Please wait for it.
@markjw I added your requests to the list but for now I’m giving priority to bugs and stuff requested by our local team.
@emre ok just needed to know, so I can decide whether to wait for updateEntity or build my own workaround editing the database directly.
1 Like
Yes @markjw we are in the same situation.
Of course I need this expanded into createAccountDocument so I can actually start using graphQL and manipulating value against Entity Accounts 
I added a new formatting tag to create buttons that gives better feedback about state. On the gif demo you can see course selecting buttons will display in darker color to indicate selected course.
To implement it I added <if></if> tag. This tag accepts an expression and render content if expression is true.
<if 1==1><bold>Caption</bold></if><if 1==2>Caption</if>
This tag will display a caption in bold text. As we can use {LOCAL SETTING:X} tag on menu item buttons I can format the button depending on the local setting value.
<if '{LOCAL SETTING:SelectedValue}'=='1'><bold>Caption</bold></if><if '{LOCAL SETTING:SelectedValue}'!='1'>Caption</if>
So button will display in bold caption when I set SelectedValue local setting to 1.
3 Likes
On next update you can use Update Ticket Grouping action to group orders by order state. Group Parameter will be a State Name.
So order’s course is stored in Course state and using Course value will group orders by the value of Course state (for example mains, starters, etc…)
Setting an empty value will remove grouping
3 Likes
Very nice. I think this could be used to get a combo on the fly setup in a simpler automation. My combo setup was very complex.
2 Likes
I’d also be keen to get a good combo setup working. @Jesse I don’t think you ever fully shared your existing combo setup, I haven’t had time to try it myself but would you consider doing a tutorial of what you did already so can get more people trying it out and getting feedback / improvements? I have a few times needed to use it but due to time constraints ended up doing a workaround using order tags only. Using combo would be very beneficial also in cases if you have a set meal with multiple items and you need to be able to customise those items (with order tags), e.g.
Beef Curry - medium spicy, no onions
Chicken Chow Mein - no beansprouts, extra chicken
Fried Rice
Coke - no ice
Currently we have like above with one set meal product then use order tags for the items, but when doing so it is impossible (i.e. well is possible but would be too complex) to have every modification set per item. We have general modifiers for all those above already set as order tags which works fine for individual items sold.
I can yes but I never shared it due to how complex it was. It likely wouldn’t work on most other systems. I will be redoing it with this new feature soon and will share it fully then.
1 Like
We released a new beta version of SambaPOS 5.2.11. I think that’s the final before 5.2.12. Thanks for testing.
2 Likes
@Jesse it groups orders by order state so you need to uniquely set a state value to group items under their own menu (combo). Update Order Group action have Auto Key and Reset Key variables to solve that but when using new action you won’t have these.
I think new grouping feature will be useful to group orders by Courses and Seats. I was primarily thinking these cases while implementing it.
2 Likes
Could any of these ticket refresh additionas be used to smothout the refreshing of screen/ticket after updating calculations?
My discounts setup is a bit hacky in order to get calculation and total to update without preventing autoselect option.
Which ticket refresh additions?
Edit: Sorry, seems like Vehbi posted my commit messages I’ll check if something can be done to update calculation part automatically when action executes.
2 Likes
@JTRTech action already have a setting called Reset Ticket but it regenerates whole ticket display and it might be slow. When it is false it will refresh only calculations for next update. Let me know if it helps or not.
Thanks, will try.
I use that at the minute but have to have two actions with true and false.
If autoselect menu item true closes autoselect so have a selected orders count constraint, and closing the order select screen causes refresh, no autoselect needs true to refresh. But ended up with being unable to void etc multiple orders in one go, it only voids first.
Maybe be my rules and have got by for now but is messy and more complicated than it needs to be.
when orders are unselected action will work for all so sounds like something leads to change selection to first order.
It is hard to guess though. maybe you can post a gif to demonstrate the issue.
@emre Nice 
Am I correct this works only before a ticket is created, i.e. can’t change department of current ticket? I remember you said you would likely implement like that.
Is this in the release now?
Yes, It works exactly like department changing buttons. When you can’t change department with buttons you can’t change with action too.
No I recently added it. You’ll see that in release notes when we release it.
1 Like
