Protect Change Table With Pin

[JTRTech]

Sounds like they need some new staff LOL
So people are paying a completely different bill? what about their own bill?

You might be better to look on the forum for the logging print bills.

[Ben1Nyaumwe]

I want to remove the change table button or edit it. Thats what i need JTR

[Castech]

Creating Ticket Logs to Improve Security

You need to install at least 5.1.51 version Why we need logging? SambaPOS contains improved ticket logging system to improve security. Adding Admin PIN’s or limiting staff permissions is always a good choice but each permission adds a little complexity to workflow. Instead of limiting users keeping track of how certain features used might be a better solution. By using techniques demonstrated here you can track anything done inside tickets. In this tutorial we’ll keep tra…

[JTRTech]

Select/Change Table are mapped from the ticket type settings;

If you unmap you will need to recreate the flow manually with an automation command.

You would need to make a dummy entity type, make a custom entity screen, make a table entity grid on it, then setup the automation from that grid.
Something like if ticket has no entity then set entity with selected, - if already has table entity set ask for pin before changing.
As said its not going to be a simple tick box to enable

[QMcKay]

@JTRTech, look at your screenshot again. Have you ever wondered what the purpose of the “State” column is for? Why is it there? I can only imagine it was a feature added a long time ago (V2) for a specific purpose.

Just spitballin’ here, but I bet we could put in place some form of Entity State flow in automation that stops or reverses Ticket Entity Changes…

That might be easier than trying to replace the Ticket Entity mappings. I mean, there is a lot of hard-coded mechanics behind Ticket Entity mappings that would be difficult, if not impossible, to duplicate with custom Automation Commands.

[JTRTech]

Interesting thought, never paid much attention to this screen as not faced issues like above, but interesting to see if that is the case…
Are you just guessing or have you tried?

[QMcKay]

I am guessing the State field is a constraint, similar to Enabled/Visible States on Automation Command mappings. That is, if the Entity is not in that State, the button does not work.

EDIT: seems my guess is incorrect. I set the state to “Available”, which I would have thought that in the case of a Table already having Orders, it’s State would be “New Orders”, so the Table would not be allowed to change.

EDIT2: In any case, the idea could still work using a custom State flow for Entities. When the table is first assigned, it gets something like a “Lock Status” assignment:

LStatus=Locked

Upon the event of Ticket Entity Changed, check the LStatus, and if it is Locked, prompt for PIN. If PIN is not provided, fire Change Ticket Entity action to reverse the change. Could be done with a Ticket Tag or Ticket State as well…

[QMcKay]

Accomplished this without States at all. How does this look?

The only thing it lacks is obfuscation of the PIN entry…

[JTRTech]

Would it maybe be ticket state?
As in buton is visible based on that state… only state that would work in that scenario would be ticket Id say.

[Castech]

How did you do it? I would like to do that to mine.

[JTRTech]

By looks of it he has done similar to what I said the other day with a custom entity screen and manually configured update entity flow.
If you lucky he will use his magic export thing for a basic tutorial.

[emre]

@QMcKay

The only thing it lacks is obfuscation of the PIN entry…

Can you try adding P in ?Prompt config where we define keyboards like OSC ? For example try OCP.

[emre]

@QMcKay

Have you ever wondered what the purpose of the “State” column is for? Why is it there?

When Ask Before Creating Ticket setting is enabled it lists entities which have that specific state.

[JTRTech]

@emre

Can you try adding P in ?Prompt config where we define keyboards like OSC ? For example try OCP.

Is this new? We have a pin prompt already???

[QMcKay]

@emre

Can you try adding P in ?Prompt config where we define keyboards like OSC ? For example try OCP.

Yes, that works, thank Emre.

The other thing about this particular setup is that it isn’t really an Admin PIN. It is just an arbitrary PIN used in the Rule.

This is the setup …

##Change Ticket Entity

We will use this Action to reverse the Entity change.

##EL Change Ticket Entity [Change Ticket Entity] (Action)##

Action Name:	EL Change Ticket Entity
Action Type:	Change Ticket Entity

###Parameters:###

Can Create Ticket:	True
Can Create Entity:	False
Entity Type Name:	[:entityType]
Entity Name:	[:entityName]
Entity Search Value:
Update Null Entity:
Entity Screen Name:
Entity Screen Search Value:

---

##Execute Automation Command

We will use this Action to invoke other Rules and optionally, run a process in the background.

##EL ExecAMC [Execute Automation Command] (Action)##

Action Name:	EL ExecAMC
Action Type:	Execute Automation Command

###Parameters:###

Automation Command Name:	[:AMCname]
Command Value:	[:AMCvalue]
Background:	[:runBG]
Delay:	[:delay]

---

##Update Program Setting

We will use this Action to store the Old Entity and New Entity, so that we can reverse it if PIN verification fails.

##EL Store Value [Update Program Setting] (Action)##

Action Name:	EL Store Value
Action Type:	Update Program Setting

###Parameters:###

Setting Name:	[:settingName]
Setting Value:	[:settingValue]
Update Type:	Update
Is Local:	True

---

##Update Entity State

We will use this Action to reverse the Entity State if PIN verification fails.

##EL Update Entity State [Update Entity State] (Action)##

Action Name:	EL Update Entity State
Action Type:	Update Entity State

###Parameters:###

Entity Type Name:	[:entityType]
Entity Name:	[:entityName]
Entity State Name:	[:stateName]
Current State:	[:currentState]
Entity State:	[:newState]
Quantity Exp:

---

##RULE - Ticket Entity Changed

This Rule is repsonsible for detecting the change in the Ticket Entity. It then stores the Old and New Entity Names, and prompts for a PIN. Finally, it invokes the PIN verification via Execute Automation Command Action

##EL Store Entity [Ticket Entity Changed] (Rule)##

Rule Name:	EL Store Entity
Event Name:	Ticket Entity Changed
Rule Tags:

Custom Constraint List (3):

Execute Rule if:

Matches

Entity Type Name	Equals	Tables
New Entity Name	Not Equals	{SETTING:EL_oldEntity}
Old Entity Name	Is Not Null

##Actions (4):##

EL Store Value

Constraint: (none)

settingName:	EL_oldEntity
settingValue:	[:OldEntityName]

EL Store Value

Constraint: (none)

settingName:	EL_newEntity
settingValue:	[:NewEntityName]

EL Store Value

Constraint: (none)

settingName:	EL_PIN
settingValue:	[?Enter PIN to change Table;;;OCP]

EL ExecAMC

Constraint: (none)

AMCname:	EL Confirm Entity Change
AMCvalue:	{:EL_PIN}
runBG:
delay:

##Mappings##

Mappings

Terminal	User Role	Department	Ticket Type
*	*	*	*

---

##RULE - Automation Command Executed - EL Confirm Entity Change

This Rule checks the entered PIN against a value that you set in this Rule. This Rule only fires if the PIN is incorrect. It then shows a “failure message”, then it reverses the Entity change, and finally execute another Automation Command in the background to reset the Entity State.

##EL Confirm Entity Change [Automation Command Executed] (Rule)##

Rule Name:	EL Confirm Entity Change
Event Name:	Automation Command Executed
Rule Tags:

Custom Constraint List (2):

Execute Rule if:

Matches

Automation Command Name	Equals	EL Confirm Entity Change
Command Value	Not Equals	12345

##Actions (3):##

MSG TEST

Constraint: (none)

MessageToDisplay:

Incorrect PIN for Table Change!\rOld:{:EL_oldEntity}\rNew:{:EL_newEntity}

EL Change Ticket Entity

Constraint: (none)

entityType:	Tables
entityName:	{:EL_oldEntity}

EL ExecAMC

Constraint: (none)

AMCname:	EL Update Entity State
AMCvalue:	{:EL_newEntity}
runBG:	True
delay:	0

##Mappings##

Mappings

Terminal	User Role	Department	Ticket Type
*	*	*	*

---

##RULE - Automation Command Executed - EL Update Entity State

This Rule is responsible for resetting the Entity State when PIN verification fails. It also clears our stored values for the New/Old Entity Names.

##EL Update Entity State [Automation Command Executed] (Rule)##

Rule Name:	EL Update Entity State
Event Name:	Automation Command Executed
Rule Tags:

Custom Constraint List (1):

Execute Rule if:

Matches

Automation Command Name

Equals

EL Update Entity State

##Actions (3):##

EL Update Entity State

Constraint: (none)

entityType:	Tables
entityName:	[:CommandValue]
stateName:	Status
currentState:
newState:	Available

EL Store Value

Constraint: (none)

settingName:	EL_newEntity
settingValue:

EL Store Value

Constraint: (none)

settingName:	EL_oldEntity
settingValue:

##Mappings##

Mappings

Terminal	User Role	Department	Ticket Type
*	*	*	*

---

[sukasem]

BTW QMcKay about tutorial builder that you have, can @emre host it so, every can use it.

[QMcKay]

TBH (Tutorial Builder Helper) accesses the local machine DB install, so you need to host it yourself on the same machine that runs the Database Engine. It also requires PHP. I think I released the code in the Beta Forum, did I not?

[sukasem]

Yes, you did. But I got some errors. I forgot what it is I tried long time ago.

[QMcKay]

@sukasem

Yes, you did (release the TBH code). But I got some errors. I forgot what it is I tried long time ago.

Dig up that topic and post your errors there. You still need to host it on a machine local to the DB. It isn’t something that Emre can host remotely to access your local configurations. That might be possible in the future, but that was not my intent when I built it. It is also read-only… you cannot alter any of the data using that tool, though that did cross my mind for a future enhancement.

[Castech]

Thanks to you very much