To return a result if 'not found' in numberpad value entered


#1

Currently, numberpad value entered rule gives me the result of selecting a Loyalty Card.

Would there be a way of it returning a result if a Loyalty Card isn’t added? I got 1000 plastic cards with mag stripe ive programmed all to have GC20 xxxx xxxx. I have to create a new loyalty card by pressing the “Create Loyalty” button, and then go through an array of questions ive set up… which still seems to be confusing to some staff…

Would there be a way of just swiping the card, the till then realising its not an already used card and so fires off an automation command to create the Loyalty? and then all I do is enter the customers name in a popup and bingo…?

Matt


#2

Im guessing it could be something as simple as making it store the number on the card in a setting, then using the constraints on the actions added to the rule?


#3

You would want to use something like report entity details using the entered value as a constraint and base the actions/flow as to if a value is returned or not.


#4

hmm, possibly add another rule constraint like {ENTITY NAME} equals ShakesCard Customer Card

and then clone it and do a NOT EQUALS?

edit: Would be ENTITY TYPE not NAME?


#5

never heard report entity details?


#6

Got it, made it fire an AMC with the following. Seems to work :smiley:


#7

now to store the NUMBERPAD VALUE, is that simply just {NUMBERPAD VALUE}?

Matt


#8

Try using {:NUMBERPAD}


#9

was just about to say found it on one of JTR’s old Questions :smiley:

Thanks, now to hope I don’t break it whilst trading haha


#10

Hmm, seems to not work?

I have a Message popup with {SETTING:StoreCardNumber} but it returns a blank popup?

Matt


#11

I also just bypassed this and did straight up {:NUMBERPAD} in the popup but returned same blank result


#12

Think number-pad is cleared on submit.
Explain your flow?


#13

Literally as above, then fires off this:

Maybe I should change the order of actions b4 it refreshes ticket?!

Let me try that


#14

Your in a numberpad rule so should be able to use the rule based expression. in square brackets FYI.
This then shouldnt matter what happens in ticket etc since its a rule value.

Also if your firing execute automation command from that you shouldnt need to save the numberpad value to setting - you could just pass it through to the automation command rule as the command value.


#15

changing order didn’t solve.

Once I can get the numberpad value to go in the setting, I can start messing with other rules to make what I want to work, work…


#16

Whats the action off screen


#17

Execute AMC: PRMLoad


#18

Don’t follow? Squares… like? [:NUMBERPAD] ?


#19

The options which come up in the dropdown in the rule, as its numberpad entered rule it should have a built in value for it. Linke exc amc rule has command name, value etc built in.


#20

So in theory you shouldnt need to store in setting, you can just pass the numberpad value over to the automation command rule in the command value.
So command name is PRMLoad and command value is the numberpad entered value.
Then in the AMC rule rather than pulling setting you just use the command value.