Copy Ticket tag to Ticket note

Opps, my mistake. I was thinking he was using Ticket Tags to store CC info.


thats the action as requested

@JTRTech,am trying to check but i cannot see an update ticket name action on the list.kindly clarify this.

Think it’s a typo.
There wasnt an update ticket tag action was there in the end though.
Looks like you might need to use graphql condo pragmatically.
However sure there must be a way to show tag on ticket list

Thanks for the correction sir.I just wish someone would lead me in that direction.the tags are already captured.whats only remaining is place them in the ticket list.

This would be great,but am a little green in using ticket tags.any leads would be helpful.Thanks for the concern @Jesse,but am capturing only the last digits of the transaction number…and why i need to show on the ticket list, is simply to ease counter checking without having to open the actual ticket to view the transaction details.

Look here.

This is the tutorial I was thinking you used:

It doesn’t solve wanting to see the ticket tags on the default ticket explorer.

Thats the tutorial i used…youre right.im now stuck on showing those details on the ticket explorer.

I am away without pc.
You can add columns to ticket explorer, what are the available options?
If you have you looks at maybe using ticket lister widget on an entity screen?

when youre back,any leads will be of great help.let me try create a custom entity screen for now while i wait on you. :slightly_smiling_face:

I did a quick mock up of an Entity screen using reports. (Ticket Lister would work as well). Using reports will give an option to search with-in report results. It behaves a little different than the default Ticket Explorer.

In your dream custom ticket explorer, what fields would you like to see?

3 Likes

Wow…This is really cool.this perfectly
meets my dream…my only last wish is a search panel and id be sorted.Thanks

I’m no genie, but I think I can grant you the wishes. :rofl: …we kinda, Ticket ID does nothing visually, we just need it to load the ticket. We can hide that column. The search I’ll show you when it’s done.

I don’t have much time tonight to show you everything. I can show you a few things to get you started.

Here is the Report needed:


You may have to adjust the page size of the report to fit your screen. That can be done later.

Report

[#Ticket Explorer:1,2,1,2,1,1,1,1,1]
>Ticket No/Qty x Items|Ticket Type|Date|User|Total|CC Type|Last 4|Customer|Ticket ID
@{REPORT TICKET DETAILS:T.TicketNumber.asc::,}
{REPORT TICKET DETAILS:T.TicketNumber,T.TicketType,T.Date,T.User,T.TotalAmount,TT.CC Type,TT.CC Last 4 Digits,EC.Customers.First Name,T.Id:T.TicketNumber="$1":{0}|{1}|{2}|{3}|{4}|{5}|{6}|{7}|{8}}
{REPORT ORDER DETAILS:O.Quantity,O.MenuItemName,T.Id:T.TicketNumber="$1": {0} x {1}||||||||{2}}

Create an Entity Screen:


Name: Custom Ticket Explorer
Button Header: Custom Ticket Explorer (different from picture)
Color: (your choice)
View Mode: Custom

Automation Command:


Navigation Settings:

Mappings:

This will put a tile on the Main Menu screen.

From here you can add:

  • Report Widget: Report: Custom Ticket Explorer
  • Editor Widget with the “Local setting name”: CTEStartDate
  • Editor Widget with the “Local setting Name”: CTEEndDate
  • Label Widget, Text field: Start Date:
  • Label Widget, Text field: End Date:
    (Right click on the widget after creating, go to “Settings” on the popup.

That’s all the time I have tonight to help you. I can finish tomorrow. This should get you started and familiar with a few things. Place & size the widgets where you would like them. If you wouldn’t mind, post some screen shots.

If anybody has some improvements that I missed, I welcome them!

I have more time today. I see I made a few mistakes in the previous post. Sorry. I’ll start over using the same screenshots.

Report:


You may have to adjust the page size of the report to fit your screen. That can be done later.

Report:

[#Ticket Explorer:1,2,1,2,1,1,1,1,1]
>Ticket No/Qty x Items|Ticket Type|Date|User|Total|CC Type|Last 4|Customer|Ticket ID
@{REPORT TICKET DETAILS:T.TicketNumber::,}
{REPORT TICKET DETAILS:T.TicketNumber,T.TicketType,T.Date,T.User,T.TotalAmount,TT.CC Type,TT.CC Last 4 Digits,EC.Customers.First Name,T.Id:T.TicketNumber="$1":{0}|{1}|{2}|{3}|{4}|{5}|{6}|{7}|{8}}
{REPORT ORDER DETAILS:O.Quantity,O.MenuItemName,T.Id:T.TicketNumber="$1": {0} x {1}||||||||{2}}

(note) - Your Customers field may be different. If you want to used the primary field change EC.Customers.First Name to EN.Customers
I dropped the .asc off the T.TicketNumber field of the @` line

Entity Screen:
Manage->Entities->Entity Screens->Add Entity Screen (right side)


Name: Custom Ticket Explorer
Button Header: Custom Ticket Explorer (different from picture)
View Mode: Custom

Automation Command:
Manage->Automation->Automation Commands->Add Automation Command (right side)
(General Settings:)

(Navigation Settings:)


Navigation Module: Entity
Navigation Module Parameter: Custom Ticket Explorer

(Mappings:)


Click “Add”, change last column under Visibility to: Display on Navigation
This will put a tile on the Main Menu screen.

Entity screen widgets:
Navigating to new Custom Ticket Explorer (Main Menu->Custom Ticket Explorer)
Right click any blank area. Select Design Mode
You will know you are in design mode with a red line around the screen and also if you right click there will be a check mark next to Design Mode
oQKurHfE2i

From here you can add widget, position after creating :

  • 1 - Report Widget
  • 2 - Editor Widgets
  • 2 - Label Widgets
  • 2 - Automation Command Button

Left click on each widget, then right click select Setting [<widget name>]
Report Widget:
AOxfCqLeuV
Report Widget: Report: Custom Ticket Explorer
Parameters: (blank)
Setting mappings: CTETicketNo=Ticket Explorer.9
Refreshing widgets: CTELoadTicket
click OK
— Additional step: Right click again. Select Property [Custom Ticket Explorer]
BJN1wrcWoi
Id: (leave as is)
Name: CTEReport
click OK

Editor Widgets:


Editor Widget with the “Local setting name”: CTEStartDate
Editor Type: Date Edit
Edit Mask: MM\/dd\/yyyy

Editor Widget with the “Local setting Name”: CTEEndDate
Editor Type: Date Edit
Edit Mask: MM\/dd\/yyyy

Label Widget:


Label Widget, Text field: Start Date:
Font Size: 16
Alignment: Right

Label Widget, Text field: End Date:
Font Size: 16
Alignment: Right
(click OK to close)

Automation Command Buttons:


Command Name: CTE Display Ticket
Value: {LOCAL SETTING:CTETicketNo}
Caption: Load Ticket
Button Color: (your choice)

Command Name: CTE Report Refresh
Value: (blank)
Caption: <bold>Refresh</bold>
Font Size: 16

Right click on screen, Select “Design Mode” to exit out of design mode.

Actions


Action Name: CTE Custom Ticket Explorer Report Refresh
Action Type: Refresh Custom Report Widget
Widget Name: CETReport
Report Name: Custom Ticket Explorer
Report Parameters: [:report parameters]
Date Filter: [:date filter]
Reset Cache: `[:Reset Cache T/F]’

Rules (1 of 2)


Rule Name: CTE Report Refresh
Event: Automation Command Executed
Constraints: Automation Command Name **Equals** CTE Report Refresh
Action: CTE Custom Ticket Explorer Report Refresh
report parameters: (blank)
date filter: {LOCAL SETTING:CTEStartDate} <> {LOCAL SETTING:CTEEndDate}
Reset Cache T/F: True

Rule (2 of 2)


Rule Name: CTE Display Ticket
Event Name: Automation Command Executed
Constraints: Automation Command Name Equals CTE Display Ticket
Command Value Is Not Null (blank)
Action: Display Ticket (this should be an existing action)
Ticket ID: [:CommandValue]

Hiding the Ticket ID Column:


Right click anywhere on the Column Headers. A popup will appear. Select Show Column Chooser (blue outline box).

A small popup window will appear.


Click and hold the Ticket ID column and drag it into the small window. Close the window.

Search


Right click again in the Column Header bar. Select Show Search Panel (green box in the above picture)
Type any info you want to search for in the box.

Column Adjustment
Right Click on the column header bar again, Select Best Fit (all columns)

Saving Settings
Right Click anywhere in the report body. Select Save Changes. Exit and restart SambaPOS.

To Use:

  • Type or select from the drop down boxes the dates. Click Refresh to run the report. (there may be a pause while it loads, depending how big the report is)
  • Highlight any row, then click Load Ticket to view the ticket.

A few limitation of this explorer

  • You can sort by column, however the Orders row line(s) will not maintain their position with respect to the Ticket row information line. To get back to the default view, log out then back into SambaPOS.
  • Closing the ticket after viewing it will not bring you back to the custom ticket explorer. You will have to navigate back to it.

If anybody has some improvements that I missed, I welcome them!

2 Likes

Hello there, when i paste the report format it gives that error.am wondering tho i may be wrong…is this line @{REPORT TICKET DETAILS:T.TicketNumber::,} calling a script that i dont have?
i have changed to the names of the tags am using.see below:

[#Ticket Explorer:1,2,1,2,1,1,1,1,1]

Ticket No/Qty x Items|Ticket Type|Date|User|Total|CC Type|Last 4|Customer|Ticket ID
@{REPORT TICKET DETAILS:T.TicketNumber::,}
{REPORT TICKET DETAILS:T.TicketNumber,T.TicketType,T.Date,T.User,T.TotalAmount,TT.CCtype,TT.CCdigits,EN.Customers,T.Id:T.TicketNumber="$1":{0}|{1}|{2}|{3}|{4}|{5}|{6}|{7}|{8}}
{REPORT ORDER DETAILS:O.Quantity,O.MenuItemName,T.Id:T.TicketNumber="$1": {0} x {1}||||||||{2}}

Save the report. Then reopen it to see if it works. The reason it needs to be saved is because of the # before the report name. It gets treated different than a normal report.

The @{REPORT TICKET DETAILS:T.TicketNumber::,} is building a list of Ticket Numbers. That list then is ran through the other reports everywhere there is a $1 (it will replace the $1 with every Ticket Number from the list). If we were running just the ticket report we wouldn’t necessary need to use the @ & $1. But because we also have an Orders report, the @ & $1 will keep both reports results grouped together.

If you want to see what the list looks like, just copy the report info after the @ and paste it a new report. It’s a good idea to do when building reports to make sure the list you get is the list you want.

1 Like

Awesome.it worksThanks.now lemmi work on the Screen.

It worked like charm! Thanks a lot everyone.
@Bob_be…Special Thanks

3 Likes

:+1: Glad you got it working! :+1:

I missed this on Sat. Great Job! That’s exactly what you were suppose to do!