Ticket Number Control (Custom Invoice Numbers with Reset)

V5 Tutorial
4

Actions

image
image870×424 16.8 KB

INUM Update Setting [Update Program Setting] (Action)

Action Name: INUM Update Setting
Action Type: Update Program Setting

Parameters:

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

image
image870×454 16.4 KB

INUM Update Ticket State [Update Ticket State] (Action)

Action Name: INUM Update Ticket State
Action Type: Update Ticket State

Parameters:

State Name: [:iNumName]
Current State:
State: [:iNumValue]
State Value:
Quantity Exp:

image
image870×364 14.2 KB

INUM Update Ticket Tag [Update Ticket Tag] (Action)

Action Name: INUM Update Ticket Tag
Action Type: Update Ticket Tag

Parameters:

Tag Name: [:iNumName]
Tag Value: [:iNumValue]
1 Like
5

Rules

Invoice A

image
image870×842 27.6 KB

INUM Update Invoice Number A [Before Ticket Closing] (Rule)

Rule Name: INUM Update Invoice Number A
Event Name: Before Ticket Closing
Rule Tags:
Custom Constraint List (3):
Execute Rule if: Matches
{TICKET STATE:InvA}Is Null
[=TN('{ORDER COUNT}')]Greater0
Ticket Type NameEqualsTicket

Actions (1):

INUM Update Setting

Constraint: (none)

settingName: INUMinvA
settingValue: {CALL:inum.upd('A')}

image
image870×985 30.3 KB

INUM Apply Invoice Number A [Ticket Closing] (Rule)

Rule Name: INUM Apply Invoice Number A
Event Name: Ticket Closing
Rule Tags:
Custom Constraint List (3):
Execute Rule if: Matches
{TICKET STATE:InvA}Is Null
[=TN('{ORDER COUNT}')]Greater0
Ticket Type NameEqualsTicket

Actions (2):

INUM Update Ticket State

Constraint: (none)

iNumName: InvA
iNumValue: {SETTING:INUMinvA}
INUM Update Ticket Tag

Constraint: (none)

iNumName: InvA
iNumValue: {SETTING:INUMinvA}

Invoice B

image
image870×842 27.6 KB

INUM Update Invoice Number B [Before Ticket Closing] (Rule)

Rule Name: INUM Update Invoice Number B
Event Name: Before Ticket Closing
Rule Tags:
Custom Constraint List (3):
Execute Rule if: Matches
{TICKET STATE:InvB}Is Null
[=TN('{ORDER COUNT}')]Greater0
Ticket Type NameEqualsTicket2

Actions (1):

INUM Update Setting

Constraint: (none)

settingName: INUMinvB
settingValue: {CALL:inum.upd('B')}

image
image870×985 30.3 KB

INUM Apply Invoice Number B [Ticket Closing] (Rule)

Rule Name: INUM Apply Invoice Number B
Event Name: Ticket Closing
Rule Tags:
Custom Constraint List (3):
Execute Rule if: Matches
{TICKET STATE:InvB}Is Null
[=TN('{ORDER COUNT}')]Greater0
Ticket Type NameEqualsTicket2

Actions (2):

INUM Update Ticket State

Constraint: (none)

iNumName: InvB
iNumValue: {SETTING:INUMinvB}
INUM Update Ticket Tag

Constraint: (none)

iNumName: InvB
iNumValue: {SETTING:INUMinvB}
6

Printer Template Tags

…

7

Printer Template Tags

We can use the Ticket State and/or the Ticket Tag when we want to show the Invoice Number on the Ticket Print.

{TICKET STATE:InvA}
{TICKET TAG:InvA}

{TICKET STATE:InvB}
{TICKET TAG:InvB}

If we use [square brackets] around the Tags, then the Tags will only print when they contain a value…

[LAYOUT]
<J00>{TICKET DATE} {TICKET TIME}|Server: {USER NAME}  #{TICKET NO}
[<J00>A# {TICKET STATE:InvA}|A# {TICKET TAG:InvA}]
[<J00>B# {TICKET STATE:InvB}|B# {TICKET TAG:InvB}]
8

DB Tools

Contains all Automation, prefixed with “INUM”.

INUM_InvoiceNumber.zip (2.3 KB)

9

Invoice Search

Because the Invoice Number is stored as a Ticket State and/or Ticket Tag, it might be difficult to locate them at a later time, because the Ticket Explorer does not display States or Tags. So here is a mechanism we can use to Search for and Display Tickets based on the Invoice Number stored in the Ticket State/Tag.

Flow

image
image1322×1004 40.1 KB

Automation Command

image
image884×1267 34 KB

INUM Ticket Search [no Category] (Automation Command)

Name: INUM Ticket Search
Category:
Button Header: Search Invoice
Color: #FF6E8E2C
Font Size: 26
Confirmation: None

Values (0): (none)

Navigation Settings
Symbol:
Image:
Auto Refresh: 0
Tile Cache: 0
Navigation Module:
Nav Module Parameter:
Template:
Mappings
Terminal User Role Department Ticket Type Enabled States Visible States Visibility
******Display on Navigation

Actions

image
image884×605 21.8 KB

INUM Ask Question [Ask Question] (Action)

Action Name: INUM Ask Question
Action Type: Ask Question

Parameters:

Question: [:question]
Buttons: [:buttons]
Description:
Automation Command Name: [:AMCname]
Execute Command In Background: False
Background Color:
Transparent Color:
Inactivity Command Name:
Inactivity Timeout Seconds:
Execute Inactivity Command In Background:

image
image884×424 16 KB

INUM ExecAMC [Execute Automation Command] (Action)

Action Name: INUM ExecAMC
Action Type: Execute Automation Command

Parameters:

Automation Command Name: [:AMCname]
Command Value: [:AMCvalue]
Background: False
Delay: 0

image
image884×575 17.2 KB

INUM Load Ticket [Load Ticket] (Action)

Action Name: INUM Load Ticket
Action Type: Load Ticket

Parameters:

Ticket Id:
Ticket Number:
Ticket Uid:
Tag Name: [:tagName]
Tag Value: [:tagValue]
State Name: [:stateName]
State: [:stateValue]
Entity Type Name:
Entity Name:

Rules

image
image884×806 25.7 KB

INUM Ticket Search [Automation Command Executed] (Rule)

Rule Name: INUM Ticket Search
Event Name: Automation Command Executed
Rule Tags:
Custom Constraint List (1):
Execute Rule if: Matches
Automation Command NameEqualsINUM Ticket Search

Actions (1):

INUM Ask Question

Constraint: (none)

question: Choose Invoice Type
buttons: Type A=A,Type B=B
AMCname: INUM Ticket Load

image
image884×980 31 KB

INUM Ticket Load [Automation Command Executed] (Rule)

Rule Name: INUM Ticket Load
Event Name: Automation Command Executed
Rule Tags:
Custom Constraint List (1):
Execute Rule if: Matches
Automation Command NameEqualsINUM Ticket Load

Actions (2):

INUM Load Ticket

Constraint: (none)

tagName: Inv[:CommandValue]
tagValue: [?Invoice Number;;;OCN]
stateName: Inv[:CommandValue]
stateValue: [?Invoice Number;;;OCN]
INUM ExecAMC

Constraint: (none)

AMCname: INUM Ticket Display
AMCvalue: {TICKET ID}

image
image884×859 27.5 KB

INUM Ticket Display [Automation Command Executed] (Rule)

Rule Name: INUM Ticket Display
Event Name: Automation Command Executed
Rule Tags:
Custom Constraint List (1):
Execute Rule if: Matches
Automation Command NameEqualsINUM Ticket Display

Actions (2):

MSG TEST

Constraint: [:CommandValue] <= 0

MessageToDisplay: No Ticket Found!
Display Ticket

Constraint: [:CommandValue] > 0

TicketId: [:CommandValue]

:bulb: TIP: The MSG TEST Action shown above is a Show Message Action using [:MessageToDisplay] as the Message parameter.

image

:bulb: TIP: The Display Ticket Action shown above is a Display Ticket Action using [:TicketId] as the Ticket Id parameter.

image

1 Like
11

… reserved for more updates …

2 Likes
12

Hi. Is this still working three years later? I have followed all of the above but am unable to get the InvA number to print on my tickets… the rest works great

Anything that might need to be altered for the most recent version?

13

Can see at a glance anything that would effect it. Likely a mistake in your automation but cant offer any sigestions without seeing your implementation.

14

Thanks for the reply. I will go back and double check everything and if no luck I will post examples

Cheers!

15

Hi,
I’m new in sambapos and is setting up my first sambapos unit.
Is this tutorial on creating own invoice number still valid for version 5.5.8.
I was about to go live using sambapos when I realize there’s a lot of 0 value on tickets that are move or merge. This will become big issue when. We get tax audited, they will said it can be a potential fraud on that ticket.

I see the tutorial is very advance and apply for 2 ticket type and using serial + number with limits for the invoice number . When my system is a very basic one. I just need the number sequence without skipping from the day the sambapos alive until forever we use it, so no need to limit it.

Can anyone help on how to do it the simplest way? As I don’t really understand the scripts command, I understand a bit on the code flow but don’t know the exact codes or tags to use.

Thanks before

16

So what is your expected result? Can you write some samples?

17

I’m hoping that the ticket number can always in sequence even though we merge the ticket, there’s no ticket with 0 value even if we merge ticket or void all item of the ticket. Cause the 0 value will become a big issue during tax audit.

Thanks

18

How is that possible? It moves items to new ticket… number is generated in sequence… old ticket is old number… there is no way to logically do that. Also for tax regulators you can add Ticket Logs to show moving of items to new tickets.

Example you start ticket 1. THen you do ticket 2, then 3 then 4. Then you decide you want t move items from ticket 2 to ticket 4. How can you ignore ticket 2? It must stay with 0 balance or the sequence is wrong.

19

As jessie says, surely if audit is that speculitave on fraud a lower ticket number date stamped after numbers following it will scream fraud just as much if in that mindset.

Perhaps you should look at stamping a sequenced number via ticket tag at time of final payment where balance greater than 0, that should give a sequence of non 0 values.

20

I’m curious how other POS’s handles this situation? (It’s not the first time this topic has been mentioned)

I believe something could be built where all the items on an original ticket could be voided (or some other similar state) and copied to a new or existing ticket. Also updating the original ticket with a ticket tag of the ticket number the ticket was transfer to…sorta like a paper trail. Maybe also creating a ticket tag on the new ticket of the old/original ticket number.

Again, I’m curious how other POS’s handles this situation.

21

Kindly point me in the right direction if you can, i have implemented everything according to the tutorial with some minor changes to suit customer request. Everything works great except i cannot close the searched ticket when i use the search feature in this tutorial without crashing the app. When ticket is opened from tickets, it closes just fine. The error looks like its expecting to land on tickets page when ticket is closed but the page is not available.
Here is part of the error:

Inner Exception 1 Type: System.Reflection.TargetInvocationException Message: Property accessor 'CommandLogs' on object 'System.Data.Entity.DynamicProxies.Ticket_CFF633D3352C757204101122CE42097AA4729BB08F1EAC362431BAE8DE9FF3DE' threw the following exception:'The ObjectContext instance has been disposed and can no longer be used for operations that require a connection.' Source: System Stack Trace: at System.ComponentModel.ReflectPropertyDescriptor.GetValue(Object component) at Omu.ValueInjecter.ConventionInjection.Inject(Object source, Object target) at Omu.ValueInjecter.ValueInjection.Map(Object source, Object target) at Omu.ValueInjecter.StaticValueInjecter.InjectFrom[T](Object target, Object[] source) at Samba.Infrastructure.Data.Serializer.ObjectCloner.Clone2[T](T item) at Samba.Services.Implementations.TicketModule.TicketServiceBase.CloseTicket(Ticket ticket, AppState appState) at Samba.Presentation.Services.Implementations.TicketModule.TicketService.CloseTicket(Ticket ticket) at Samba.Presentation.ClientLibrary.Modules.PosModule.PosViewModel.() at Samba.Presentation.ClientLibrary.Modules.PosModule.PosViewModel.(EventParameters1 )`

22

image

image

1 Like
23

Thanks @YILDIZHANPOS that actually worked! But how does the search know what ticket without passing a ticketId? Just trying to understand why the ticketId was not needed and why it crashed the application. Thanks again! really appreciate it.