Posted: May 24, 2016 at 4:41 am
|
Doc do not show how to – Description does not match EE4. |
You can find one example in the documentation: https://eventespresso.com/wiki/registrations-ver-4-0/#bulk-actions |
|
|
Confusion goes on. The whole thing to handle seems very different when payment is already done? |
|
How can we imagine the effects of Registration Status in EE4 to an event process? So what is the meaning of Cancelled And how does cancellation effect the workflow for attendee if they are cancelled and what happens to invoice? Further, what to do for the situation described above, 1 of 3 Tickets is cancelled and without a complete map in mind, we do not no where to click in the backend, as there is no intuitive handling usability, and no effective real life documentation for daily situations. |
For your specific scenario you describe here, where you want to exchange in a different ticket for a transaction, your best option is to trash then delete all the registrations for that transaction, then start over with a new transaction and select the desired tickets. |
|
|
O.K. This does not work if payments are already done. I do not understand what different status like “cancellation” does anyway? Just an color indication in the backend? |
|
And how can I produce a new set in exchange for the specific Attendee? Or shall I ask the customer to buy a new set? |
|
In summary, as we are stuck during selling tickets for the event – How can we handle ticket changes like cancellation have an effect on the invoice for the attendee. Some clients did change their mind with us and we have to give a processed invoice actualized for the customer… |
|
This is the situation > http://i.share.pho.to/49684708_o.jpeg One Ticket (#2) was set to “cancelled”. Does have no effect on calculation? Question: As in the Screenshot, how to proceed, when 1 of 3 tickets is cancelled, set to cancelled by admin, now want to have a new invoice and send it to attendee… The whole transaction does not change as one ticket is cancelled but still show price of all 3 Tickets. Where is the logic and where is the workflow? Not to mention a step beyond, that means, how to exchange ticket #2 with another one? |
It turns out that the Ticket Cancellation has no affect on the Transaction. There’s an open ticket to change that. What you’ll need to do in the meantime is start a new transaction and remove the transaction. |
|
|
As we had not enough detailed answeres in our communication, we like to ask till we understand right. As we now do not know, is our understanding wrong or what do you mean exactly with: it turns out, that ticket cancellation has no effect on Transaction – is it a bug or we are dummys? |
I’d say it could be labeled a bug, or labeled a missing feature. This has nothing to do with anyone’s intelligence. The developers have worked many hours on trying to get the Ticket Cancellation feature to be able to update the transaction totals, but ran into some unexpected trouble with unit tests and now need to refactor unit tests before they can go any further. When you start a new transaction, you’re starting over with a new registration instead of trying to cancel/edit existing registrations. |
|
|
We are intelligent dummys – I know… Just we did try to find out for 24 hours, what we do wrong. So only now I know, there is a bug. A new transaction for the specific attendee – how to do this? |
You can add a new transaction for the attendee by: 1) You go to WordPress dashboard, then go to the registration list for the event that you want to add a registration. |
|
|
Another word to usability and many Confusion which arises: Only by entering Registration over Eventoverview > Attendees, there is the button to find, but if there is a reason for this, must be a very good one, kept secret. Now as we got trapped over “cancelled” function, the same questions arises to the other status of registrations and transactions: what is and what should be the function is not clear, as i said from the beginning, docs are not helpful, they are NOT self explaining. Biggest mystery to us, how are other customers work with this, i cannot imagine that “cancelled” function does not effect others, or they do use event espresseo on very very low level. |
The reason that the there isn’t an “add a new registration” button on the main Registrations view is because the main registrations view can show registrations for all events. The views where it shows registrations for one event have the button. The view where it shows registrations for many events do not have the button. By including the button only on one event’s registrations view, it removes the step of selecting an event to add the registration to from the UI. |
|
|
Is there any news or update to the Fact: Ticket Cancellation feature to be able to update the transaction totals? |
No they still need to refactor the unit tests before they can make that change. We will update this thread when there’s been some progress. |
|
|
As we had a lot of work and confusion about this task of cancellation and after the last update, I am curious to do another update. |
Hi there, The work for Refactor Unit Test Model Object Factories and Adjust Transaction Totals when Registrant Status Changed to “Declined” or “Cancelled” are not complete and thus were not included in Event Espresso 4.9. We will update this thread when there’s a release that includes these changes. |
|
Hi there, |
|
The support post ‘Ticket Canellation – Confusing Workflow’ is closed to new replies.
Have a question about this support post? Create a new support post in our support forums and include a link to this existing support post so we can help you.