Add automation command or entity button to control action constraint

josephrussell · January 3, 2019, 6:41am

Hi Samba POS Team-
Its been a long time since I posted. I’ve been busy with my regular job and only get involved with restaurant and bar at times. I worked a busy night and saw a need for an expediter station and now I need to add an IP printer which can be turned off/on on the entity screen. We only use the expo system a few times a month, so that is why I need to be able to toggle the action. Shutting off the printer still spools the print jobs so that isn’t a good solution. If we don’t have the expo station up it should be turned off. I figured putting this out on the forum would be the best way to get a good solution rather than me making a messy one. So what I need to accomplish is:

-Set an expo printer action within ticket closing rule that can be constrained based on variable or entity state which can be controlled from a single terminal (or multiple if possible).
-Control variable or entity state by automation command or entity button which can toggle and show state of the printer.

I’ll have more time later to play around with it, but I have to setup a printer before I can dig deep. Maybe somebody has dealt with this already.

Jcr

JTRTech · January 3, 2019, 12:52pm

I would use a program setting. If its a globalsetting you can make a button to update on an entity screen available on any/all terminals.
Then use that program setting as a constraint on the automation specific to the expo terminal.

josephrussell · January 3, 2019, 4:13pm

Thanks JTR. I’ll test that out later tonight.

josephrussell · January 4, 2019, 5:56am

Okay, I can’t seem to get the caption to toggle even though the global setting seems to be changing. What am I doing wrong?

Value 0

Value 1

josephrussell · January 4, 2019, 6:01am

Okay, it seems that changing the auto refresh setting from 0 to 2 gives the system enough time to read the global variable and then it updates. I’m guessing since I’m running the test system my surface that its just taking to long for the auto refresh to pickup on the newly stored variable. Although 1 second seems more than sufficient it still misses if from time to time.

JCR

josephrussell · January 4, 2019, 6:36am

I’ll try later on an actual printer, however it should be working. Here it is in case anyone needs it later.

Create Action

Create Rule

Create Automation Command Button

Add automation command button to entity screen and format it

Create the new print job/action and add constraint (GLOBAL SETTING:Expo_Status} != ‘1’

<I’ll do this later, no picture>

JCR