That would be because the Tutorial waits for the Ticket Closing Event to change the Order KDStatus state.
You will need to find another Event or way to make that happen. I don’t know how the Gloria Food setup works so I can’t really offer any solid suggestions. The fact that the Tasks were appearing on the KDS before you modified the KD Setup suggests that you may have missed something.
I think so. And it has to do with your “Source” Ticket Tag. You should instead be able to modify your KD Printer Template to include that Tag as a Task Custom Field. As I mentioned in another Topic, you can silently create Custom Data fields in a Task without defining them in the Task Type.
So when it comes to the Template, if you have a section something like this:
[ORDERS]
++{ORDER DATE} {ORDER TIME} {ENTITY NAME:Table} {ENTITY NAME:Customer}
(Id={NAME}-{TICKET ID}-{ORDER UID})
(TID={TICKET ID})
(Color=#FF333333)
<bold>[=('{QUANTITY}'>1 ? ('{QUANTITY}'+' ').substr(0,2) : ' ')] {PRODUCT NAME}</bold>
[='{PORTION}'=='' ? '' : '<font Consolas> <color #FF55FF33><size 17><bold>{PORTION}</bold></size></color></font>']
{SORTED ORDER TAGS}
You can see these 3 things in there, which are Custom Fields:
(Id={NAME}-{TICKET ID}-{ORDER UID})
(TID={TICKET ID})
(Color=#FF333333)
Actually, Id and Color are “special” data fields, but TID is Custom and it isn’t even defined in the Task Type… but that doesn’t matter - it requires no definition So you should be able to add, for example:
(Id={NAME}-{TICKET ID}-{ORDER UID})
(TID={TICKET ID})
(Color=#FF333333)
(Source={TICKET TAG:Source})
That should populate a Task Custom Data field named “Source” with the content of your Ticket Tag (assuming your Ticket Tag Name is “Source”).
Now you should be able to use the Task Editor Widget to filter based on the Custom Data Field named “Source”.