Versions Compared

Key

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

...

  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

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

    4. 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 (?)

  4. Static Cache Guidelines

    1. 24 Hours:

      1. MetaDataTags -> 24 hours

      2. ProductMetaDataTags -> 24 hours

    2. 30 Minutes:

      1. ProductAttribute -> 30 min per product

      2. TerminalConfiguration -> 30 minutes

    3. By Setting:

      1. Inventory pools (Get Inventory For Month call) -> "ecommercesettings.productinventory.cachetime"

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

      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 (?)Dynamic pricing tables: yieldPriceListTable, yieldProductVariantTable, yieldDaysToArrivalTable -> "ecommercesettings.dynamicpricing.cachetime"

      2. Product Inventory (golf specific): -> "GolfSettings.ProductInventory.CacheTime"

    4. Logical:

      1. If catalog setting "CacheProductPrices" is set to true product prices are cached for 60 seconds

    5. 1 minute:

      1. ActivityLogType

      2. Category

      3. Category API Call (this call loads the category pages and PDP pages)

      4. CheckoutAttributes

      5. Currency

      6. Customer Household Information (name, birthdate, address, media codes, and gender, legacy contact id)

      7. CustomerRoles

      8. Discount

      9. DiscountRequirement

      10. Does a product have an attribute y/n (cached so we don't call the db to get attributes if the product doesn't have any)

      11. Languages

      12. LocalStringResource (language strings)

      13. LocalizedProperty

      14. PermissionRecord

      15. Picture (table)

      16. ProductCategory

      17. ProductManufacturer

      18. Settings

      19. SpecificationAttribute

      20. SpecificationAttributeOption

      21. Store (holds url and language info)

      22. StoreMapping

      23. TaxAddress

      24. TaxRate

      25. Url RecordsWidgets