Do we have access to Terminal Name or ID

Version 4 V4 Question
1

I try to consolidate some rule and button for printing on each terminal.
It would be nice if I can have only one rule for print bill and constraint it by Terminal ID or Name.

Tried: [:TERMINALID]-[:TerminalId]-{TERMINAL NAME}-{TERMINAL ID}-{:TERMINALID}-{:TerminalId}

2

Why do you need multiple rules? I mean I only have 1 Print Bill rule… I can not figure out why you would have more than 1 rule.

3

Each terminals have its own printer. I can’t figure it out to use only one Automation Command to print out receipt at their own terminal printer

4

You add a variable for Print Job in your action… you use 1 rule on each terminal… you write into the rule what print job to execute for that terminal.

5

How to know what terminal fire this action? What variable for Terminal ID? That why I ask if we have access to this terminal variable

Edit: that is still 1 rule per printer. I would love to have 1 rule for all printer.
I now do that 1 rule for each terminal. I now just want to add print last receipt. I have to make rules for each terminal again.

6

You dont have to know what terminal… … it knows what terminal it is when it executes the rule…

EDIT: OHH i see what your saying. Even if you fire a constraint… how would it know what printer?

7

Still have to create multiple print job for each printer and each template.
But if I have terminal ID, I can reduce Automation Commands and rules. I see no way to avoid multiple print job.

8

How would the rule know what printer to use… constraining it to just a terminal will not be enough.Or are you talking about listing ALL the actions in the rule and putting the constraints on the actual actions?

9

Yes, add all print bill action for each terminal to one rule and one automation command and constraint each action with terminal id.

10

Did you try '{TERMINAL}' is '2'

or '{TERMINALID}' is '2'

11

I did tried all of them in show message. Either output empty or what you put in. I never get terminal name or ID

Input:

{TERMINAL}-[:TERMINALID]-[:TerminalId]-{TERMINAL NAME}-{TERMINAL ID}-{:TERMINALID}-{:TerminalId}

Output:

{TERMINAL}---{TERMINAL NAME}-{TERMINAL ID}--
12

Terminal ID is on tickets as TerminalId… so it should be possible

13

the ‘’ were not optional I meant for you to type those as well. Its there on the tickets maybe he has not given a syntax for it yet

14

It should be {:CURRENTTERMINAL} It stores terminal name.

4 Likes
15

Show up empty when I use show message action.

16

You have to store it… and then pull it up…

17

How to store it because it read empty?
I tried it anyway using update program setting and ticket tag but it nothing.

Database program setting Variable ‘Terminal’ empty

18

Try storing {:CURRENTTERMINAL} in a Program Setting on Event of User Login or Ticket Created.

Even though the DB setting is blank/null, you probably still have access to it during certain events, same as {:CURRENTUSER} and {:CURRENTDEPARTMENT}.

19

No need to store it manually. Update SambaPOS if you’ve didn’t recently updated it.

20

Hmm…I install 4.1.65 again this morning. It still not showing value for {:CURRENTTERMINAL} in Show Message action.