Content >

Version 0.11.0

Version 0.11.0

  • 4441: OnLoyalty integration
    • OnLoyalty source code has been moved to this repo
    • Removed Bepoz gift card integration code
    • Removed Bepoz POS integration code
    • Removed TCard gift card integration code
    • Removed other unused code
    • ONL card types are now read-only

To import OnLoyalty data, see the Import OnLoyalty SQL script.

  • 4403: Integrated app login
    • Mobile app users can use POS member sign-in to sign in to the app.
    • Support: ensure the OpenID Authorization Server and OpenID Token
      Validation features are enabled and configured according to the
    • The role and configuration of the OpenID Token Validation feature
      has changed; this should now be configured to validate tokens from
      the POS server.
    • The POS License Management feature now handles license token validation;
      no configuration is needed (outside of configuring the server’s license).
  • 4497: Simplify/unify permission checks for licensed clients
    • this change should be transparent; just implementation is changed
    • QA can test POS sync to verify existing functionality
  • 4406: Gift Card Codes & API changes
    • Gift cards now have one more codes that can be associated with them.
    • Added external and short-personal code types
    • Replaced ‘PIN’ values with ‘claim code’ code type
    • Updated ONL admin console and API to work with the new approach, although changes
      are backward-compatible (no changes to the API interface)
    • Added POS GraphQL Query endpoints: ‘giftcards’ and ‘my/giftcards’. Mutation endpoints will
      be added in a later release.
    • Support: there are a series of migration scripts, found in the tools/OnLoyalty folder, to
      migrate data.

      • Read them before running, to understand what they are doing – you may need
        to make some changes.
      • In particular, PIN values must be unique across all code values.
  • 4485: Move loyalty points processing to POS
    • ONL stores are now read-only; they should be managed in POS.
    • Store groups and regions are still maintained in ONL. These need to be defined first
      in ONL, then selected in the POS Locations edit page.
    • Support: for any existing deployments, you must re-publish any Locations that have
      already been published in POS.
    • added Fusion.POS.Purchases module
    • Support: these modules may need to be manually enabled for existing deployments that
      have already enabled Fusion.XMS.LoyaltyPoints.
    • QA/Support: purchases and point records are ONLY created for XAct transactions that have been
      posted – i.e. they have a status of posted. If the ASI is not posting transactions,
      purchase rows (and things like points) are not created.
  • cache db connection wrapper in ISessionDb
    • developer & testing note: ensure that we do not get any odd data-related issues or
      exceptions, including ‘object already disposed’ exceptions
  • 4582: new Fusion POS Base module
    • this should fix some odd bugs with server-to-server connections, that could show up
      in multi-tenant environments
    • including situation where the wrong client license is used to connect to a server!
    • this module is an ‘Always Enabled’ module
    • QA/Support: however, for existing deployments, make sure this module is enabled. If this
      is not enabled, you may get a “No implementation for IVersionProvider can be found” error
      on the dashboard home page; if this is the case, you will need to manually enable this module
      through the ‘Features’ page.
  • 4631: New CORP Build
    • We’ve added a new CORP build – this is for the Corporate edition of POS, which is what we
      are deploying to client sites and (currently) AWS. You’ll see a new ReleaseCorp that you
      should be using when deploying this edition.
    • For the meantime, do not use CLOUD or ReleaseCloud any more. We will use this build later,
      but not now.
    • When deployed, the POS admin home page should say “Corporate Edition” – not “Cloud Edition”.
  • 4631: Migration Diagnostics
    • there is a new diagnostic that shows a warning if there are any out-of-date migrations
    • migrations can become out-of-date if there is an error running them; you can check the logs
      for errors and warnings to see the details of why the migrations fail.
  • 4631: Moved various “POS” features to their parent modules.
    • QA/Support: we’ve moved functionality in many POS modules to their ‘parent’ modules, e.g.
      “Fusion.XMS.POS.Locations” functionality is now in “Fusion.XMS.Locations”, with the idea
      that POS-related functionality is only enabled if “Fusion.XMS.POS” feature is also enabled.
      This means that you’ll have to worry less about ensuring that POS features are enabled for
      each ‘main’ feature.
    • In general, these changes are transparent. However there a few things that will require your
    • First review the background task schedule settings. These may have reverted to their default
      values, if you have made changes. You may need to re-apply your changes.
    • Second, check your migrations to ensure they have worked – and that there are no exceptions
      in the logs. We made a change to where migrations are located, and while everything should be
      handled automatically, it’s good to check.
  • 4631: Fusion.XMS.BasicTax feature
    • This is a new module, and the Fusion.XMS.POS.BasicTax features have been moved to it.
    • Support: if Fusion.XMS.POS.BasicTax was enabled for a client, you MUST enable this new module
      manually after you upgrade the client.
  • 4631: Added Code field to Locations.
    • This replaces the POS Store ID field; to the end user, not much has changed – but many changes
      were required internally, so locations should be tested thoroughly (i.e. manual edits of locations,
      as well as the Store Background task should create locations correctly).
    • Support/QA: the date change should be seamless, and handled automatically.
    • However, quickly review locations to ensure that Code values are correctly entered.
    • If OnLoyalty integration was enabled, also open OnLoyalty and verify that stores have been
      updated with the Code values in their POS ID fields. These should not be random Content IDs.
      If this is not correct, just re-publish the offending locations in POS.
  • 4686: Redeem loyalty points for gift cards.
    • QA: do some quick re-tests to ensure that purchase processing & points generation is still working.
    • QA: check OnLoyalty to ensure that gift card transactions, gift card balances, points records, points
      balances, and customer balances (total points, amount redeemed total/YTD/MTD) are all updated correctly.
    • QA: test OnLoyalty’s admin console Redeem Points feature