Versions Compared

Key

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

 9.0.0 Product Release




Production Release Date: Tuesday, January 22, 2019, Beginning at 6:30 pm PDT

Platforms: B2B, POS

Release Type: Major

Downtime: None

Environments for Testing: Sand 10, POS-Sandbox 9.0.0 (code update on 1/7/2019)



Bugs

Backoffice (B2B)

  • Canceling a membership in Salesforce or POS that was paid with more than one method of payment, is not refunding properly
    • We fixed an issue where canceling a membership that had previously included an in-cycle lifecycle action (such as an upgrade or a downgrade), and was paid with more that one payment method, could have resulted in an incorrect refund.


  • Reporting: Membership dataset appears to be out of sync with the rest of ACME for "standing" value
    • We fixed an issue where reporting on membership standing was not showing the correct "standing" value. For example, even though the expiration date was correct, memberships were reporting as "active" and not "lapsed". 


  • Renewing a standard membership and auxiliary membership in the same order, caused an incorrect open balance on that order
    • We fixed an issue where renewing a base membership and an auxiliary membership in the same order, resulted in an open balance on the order, if the auxiliary membership was a post-term renewal.

Point of Sale (POS)

  • Membership: Disabling the "manage membership" function was not restricting users from managing memberships
    • We fixed an issue where the back office setting to "disable membership management" at Point of Sale was not disabling the "manage" button properly.


  • Order Management buttons are not always appearing during transactions
    • We fixed an issue where the "void item" and "update order" buttons were not appearing in POS Order Management, when they should have.

Emails

  • E-ticket QR codes are not visible under specific order conditions
    • We have enhanced our confirmation email for orders with a large number of tickets. Emails will correctly display up to 50 tickets in an email and if more than 50 tickets are ordered, then some email clients (such as gmail) will require the user to click "view entire email" to expand the remaining tickets.

APIs

  • API Enhancement - NC and Colorado state abbreviation mapping
    • The states API was incorrectly mapping the state abbreviation of NC to the state of Colorado. This was causing issues for venues using our APIs for custom websites.

Improvements

Backoffice (B2B)

  • Clickable area for Ticket icon (e.g. Create Order icon) was too small for usability
    • We increased the clickable area around the ticket icon, so that it's easier to proceed into the cart to sell an event. Previously, users would accidentally open other links when they intended to sell a ticket because the clickable area for the ticket icon was too small.


  • Updated naming conventions to be consistent for Organizations
    • We have ensured we use consistent naming conventions for Organizations within back office. There were a few places that used the name "account", and these have all been changed to consistently say "organization".


  • Optimize performance for orders with large ticket quantities
    • We have improved the speed and performance of checkout for orders with a large number of tickets (ie 100-500 tickets/order).


  • Import/Export Tool: updated data validation process 

    • In order to prevent bad data from getting imported into ACME, we have added a new validation for users of the Import/Export tool.
       If a user imports a membership number that already exists on a different import ID, we will prevent that record from being imported and display the following error message: "Membership number conflicts with an existing membership. Please review the membership numbers and their import ids."

Apple Certificate

  • We are updating the Apple iOS certificates for the Acme Sales POS and Access Control applications to keep them running on iOS devices. We do this to stay in compliance with Apple development requirements.