Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »

See also the 2.11 release guide on improvements made in the 2.11 release: 2.11 Release Guide - Performance Improvements Phase I

  1. Support for PayEezy

    1. Token now stored in database, not session

    2. Included in 2.11 release https://aspenware.atlassian.net/l/c/VQ8Jr5CL

  2. Schedule Tasks replaced with Azure functions

    1. Delete Guests, Keep Alive, email processing, order processing

    2. Can all be delivered without a release. Requires application service restart

  3. Administration and Fulfillment System Changes

    1. Administrators should not make any changes when scaled out

    2. If an admin makes any change when scaled out, it will only take effect on one application service/site in real time.  The other scaled out sites will not ‘see’ the change until the cache expires on that machine or an action is performed on that machine that causes the cache to clear. For example, if product inventory is cached for 5 minutes then the longest any machine will have to wait to see updated values is 5 minutes but it could be sooner.

    3. Some settings, such as Queue-It API key, customer ID, and secret, require an application service restart after any change (whether scaled or not).   See Queue-It Release Guide

    4. Pricing and inventory are cached ? (anything else, like prompts, waivers, delivery methods, discounts, time based activities?).

      1. In the 2.12 release, coming in late October, inventory will be enhanced so it is no longer retrieved from RTP|ONE. 

    5. Customer profile details

      1. If customer profile details are changed in the fulfillment system (RTP|ONE or Siriusware) while the guest is shopping, the changes won’t be seen until the cache is refreshed (?)

  • No labels