Automation Key Pad

[JTRTech]

Very odd…

This works to update program setting;

However this doesnt…

Program settings…

[JTRTech]

Triggering the same rule from an automation command button works as expected;

Im guessing that for some reason the {:NUMBERPAD} tag doesn’t work in an automation command rule if triggered from a custom button.

But this doesnt work;

Think this is something @emre might need to look at.
As far as I can tell a custom button triggered automation command rule cannot pick up {:NUMBERPAD}.
If in the rule its giving blank and as Value in custom button menu settings it give the string {:NUMBERPAD} as the value so neither approach works.

[RickH]

thanks for trying it out, hopefully @emre can find or add the solution

[JTRTech]

Just tried a double automation command loop

Custom Button (Command Name=CustomKeyboard, Value = 1) -->
Rule 1 (Command Name = CustomKeyboard) --> Ex Automation Command Action (Command Name=CustomKeyboard2, Value = [:CommandValue])
Rule 2 (Command Name = CustomKeyboard2) --> Set Numberpad (Value={:NUMBERPAD}[:CommandValue])

Still doesnt work so something defiantly not liking {:NUMBERPAD} when triggered via custom button on menu.
Its not just the initial rule but even the knock on rule triggered by an exacute automation command.

As a side note the double command still works if 1st rule is set to go from the Test button with value 1 as before.

[RickH]

hopefully we can get this working as it looks pretty good on the setup im building

[emre]

I’ve explained it in this tutorial. You can read it with [:Numberpad] by 5.1.57

How to give category buttons fixed value

I’ve implemented something simple. It will work for 5.1.57 update. I’ve added misc item under general category. [image] Added Add Misc Order action to insert misc item into ticket. [image] Added another action to update item’s name. [image] This automation command mapped nowhere. It will allow us to map these actions to custom menu buttons. I only gave it a name. [image] I’ve created a custom menu category and clicked Add Custom Button link to add 5 misc item categories. [image] I…

[JTRTech]

@emre

[:Numberpad]

Awesome, thanks emre.
Im still a little lost when it comes to the diference between [:Tags] and {Tags} but this should solve RickHs question

[emre]

You can’t access it via {:NUMBERPAD} or {SETTING:NUMBERPAD} as clicking a menu item button clears numberpad value. So I’ve stored it as an action parameter so you can read it with [:Numberpad] .

[JTRTech]

So [:Numberpad] will work in any action?

Am curious about the colon in the other {:NUMBERPAD} tag, what does this achieve?

[RickH]

Brill @emre thanks ill give it a try when im free wooooo
Happy xmas

[emre]

@JTRTech

So [:Numberpad] will work in any action?

That will work for all automation commands triggered inside a ticket.

@JTRTech

Am curious about the colon in the other {:NUMBERPAD} tag, what does this achieve?

You can use {:SETTING NAME} syntax to read a setting. It uses curly brackets like printing tags but it is not a printer tag. It is a setting reading tag and works when related area does not have full printer template tag support. Rules supports both printer tags and setting tags so both tags works.

[emre]

@RickH

Brill @emre thanks ill give it a try when im free wooooo

Latest refresh on beta group have this…

@RickH

Happy xmas

Happy Christmas to you all…

[JTRTech]

@emre

{:SETTING NAME}

Thanks, but {:SETTING NAME} is not {SETTING:x} right…
Is there a list of {:SETTING NAME} ‘tags’ somewhere

[emre]

Well I mean {:Blah} will read Blah setting value like {SETTING:Blah} does. There is no difference when used inside rules.

[JTRTech]

Oh, ok, so there is a hardcoded Program Setting for NumberPad then?

[emre]

@JTRTech

Oh, ok, so there is a hardcoded Program Setting for NumberPad then?

Yes. Just like you store actual numberpad value as a setting inside “Number Pad entered” rule.

Add Constraint to action

SambaPOS already stores these local state variables by default. You can access these with setting access syntax. CURRENTUSER Stores current user name ENTITYSCREEN Stores current entity screen name DEPARTMENT Stores active department name NUMBERPAD Stores current numberpad value ISLOCKED Useful to determine if there is an active ticket.

[JTRTech]

Arr, they are local settings, makes sense since it wouldn’t make sense to have them globally…

Allong these lines, how can we see local program settings? where are they stored?

[emre]

@JTRTech

where are they stored?

They stored in memory

[JTRTech]

@emre

They stored in memory

Thanks for that! LOL
You cant look at the list them in anyway like global ones in SQL manager?

[emre]

Sorry. There is no list for them but I have a to-do item in my list to dump settings in rule debugger.