Hi Jesse & all,
Have followed your hold button guideline, I did mistake unknowingly due to the status and current status positioning in my PC. However, am very happy that i could get the results. I am a non IT person, it took me days to accomplish the result as i could not realize my input mistakes.
Further, in the end of the post, you mentioned about custom cancel route, can you please help me over it.
In my situation, Hold option works great, when I Unhold ticket> the status becomes Unpaid and Hold order items becomes New Order, thereafter if I try to cancel the order item (which is now âNewâ), cancel button does not work. the Item remain in the order.
Is this a real problem or have missed or unable to follow the guidelines when setting up the hold steps.
note : please forgive me for any mistake as this is my first forum.
In my system I handled this my having a custom staye for cancel type that replicates new orders for new cancel and hold process changes that to hold cancel. Normal ticket closing changes the cancel state again, canât remember if removes or changes to submitted or something else but that then makes cancel not available once properly submitted.
I then adjusted the visibility of 2 cancel buttons, default that shows for new cancel items and one that mimics void on hold cancel items.
I tell a lie, actually I donât use origional cancel at all anymore at least, I have a cancel gstatus that is similar to void but isnât restricted like void is, that gives me simple tracking on cancells rather than just removing complely but the buttons part is relevent all the same.
The above along with organising sorting on command buttons means through the flow the spot where cancel is shows a cancel button without admin pin restriction for new and previously held but still ânewâ orders and then void with admin pin once submitted.