Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

 8.9.0 Product Release

...

Environments for Testing: Sand 10 (code update EOD 11/06/2018), POS-Sandbox 8.9.0


...

Bugs

Point of Sales (POS)

  • Calendar 'Stick' Issue
    • We have fixed an issue at the POS where using the calendar to sell an event in a future month resulted in the future month's days showing on the calendar, but the current month's label was incorrectly displaying. Now, when you complete a sale for an event in a future month the calendar will default back to the current day on the retail screen.


  • POS is not properly displaying Vanity Express error messages (Applicable only to those using an Ingenico CC device)
    • In a scenario where a card is declined (e.g. due to being expired or having insufficient funds), an error message will show so the agent knows why the card did not work. Also, should the visitor cancel it was declined. This same error message will also show if the visitor cancels the card processing for any reason , a message will display informing the agent of this(e.g. pulls card out too quickly).

Backoffice (B2B)

  • Resource related error preventing payment on orders with balance due
    • We have fixed a bug where orders with open balances were not able to collect payment if the type of resourced tied to the event had been edited.


  • Fix JAVA API servers OOM and CPU Spikes Performance Optimization
    • An issue was found with the audit trail on event templates, where if viewed, would cause a high load on the servers. The link to view the audit trail has been removed temporarily while we put the fix in place. The link for the audit trail will be placed back in an upcoming release.
    Ticket durration incorrectly showing as unlinked 
    • .


  • Mass event un-link unable to be re-linked.
    • An issue was found when the ticket purchase availability was set to the Event Duration. It wast incorrectly reported as unlinked when it did not change from the template, which would result in the a mass un-linking of the Events. This has been resolved and will no longer happen.