Awesome, thanks emre.
Im still a little lost when it comes to the diference between [:Tags] and {Tags} but this should solve RickHs question 
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] .
2 Likes
So [:Numberpad] will work in any action?
Am curious about the colon in the other {:NUMBERPAD} tag, what does this achieve?
Brill @emre thanks ill give it a try when im free wooooo 
Happy xmas
That will work for all automation commands triggered inside a ticket.
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.
Latest refresh on beta group have thisā¦
Happy Christmas to you allā¦
2 Likes
Thanks, but {:SETTING NAME} is not {SETTING:x} rightā¦
Is there a list of {:SETTING NAME} ātagsā somewhere
Well I mean {:Blah} will read Blah setting value like {SETTING:Blah} does. There is no difference when used inside rules.
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.
1 Like
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?
They stored in memory 
Thanks for that! LOL
You cant look at the list them in anyway like global ones in SQL manager?
Sorry. There is no list for them but I have a to-do item in my list to dump settings in rule debugger.
1 Like
Would be handy, I have always opted for global settings with terminal name prefix of the setting name rather than use local setting as debugging is trickier vs just looking at values in SQL manager.
For some cases having a show message for {:Setting} will be better as it shows actual value at the time show message executes. Most of the time knowing how it changes is more important than what it stores.
2 Likes
Know what your saying - usually in my case ive used the wrong tag LOL
1 Like
Hi @emre any chance of a quick tutorial for setting custom product buttons as numberpad buttons?
Ive tried what you said but either couldnt get it to work or it had the same effect and only entered 1 number and the next just replaced it
The tutorial you did for misc item uses update order action but i dont want to add an order, just set the numberpad values so i used set numberpad value action
I tried using [:Numberpad] i assumed as you used [:Name] in the action for the misc item tutorial you did that i would use [:Numberpad] in the set numberpad value action
I cant show screenshots at the moment as on phone but all i did was put the[:Numberpad] tag in the action parameter and in the custom product settings ive added the auto command name in and put 1 for the value for button 1, 2 for 2 etc
You beaut!!! I was doing it wrong in the action!! Cheers @JTRTech ill update my action tonight 