Not with the implementation described in this Tutorial, since the Account and Entity Creation is done upon Settlement. However, if you understand the flow of how this works, it could be done with some alterations.
This is what currently happens:
- GC is added to Ticket, and receives
Order Stateof Ordered. - Ticket is Settled. This invokes the Event called
Before Ticket Closing. - The Rule called GC Update States captures this event and changes the
Order Stateto Printed. This invokes the Event calledOrder State Updated. - The Rule called GC Purchased & Printed captures this event and does the work of creating the Entity and Account, creating the Credit Transaction to the Account, and setting the
Entity Stateto Purchased.
So what can we do to change this? Here is one idea…
EDIT: This addition is so simple, that I am going to add it to my system. One reason for being able to do this (for me) is when I donate a GC to a charity, and I don’t want tender any cash for it or show it as a Sale.
- Create an
Automation Commandcalled GC manual create, map it to Order Line, and set theEnabled StatesandVisible Statesto Ordered. - For security purposes, it may be wise to also either map the
Automation Commandto AdministratorUser Roleand/or set theConfirmationto Admin PIN. - Create a
Ruleto capture theAutomation Commandand fire the Action GC Update Order State to switch the State fromOrderedtoPrinted.
Automation Command:
Rule:
Operation:
- Enter the value of the GC into the Numpad area, then select the GC Product.
- Highlight/select the GC
Order linein the Ticket. - Click GC Create … all the magic happens here automatically.
- Highlight/select the GC
Order linein the Ticket again. - Click Cancel.
- Click Close.
FLOW:
GC Entity Search:
Accounts:
The Cash Sale for 50.00 was for another product for illustrative purposes. Notice there is no Sale nor Cash visible for the GC Creation of 700.
Work Period Report:
Again, notice the GC Create is not reported here…
