Document status: RELEASED
Date:
Prerequisites are found under Chain Web Release Notes.
Improvements
Module | Description |
---|---|
Bonus rollout | Previewing members for bonus rollout (TFS: 166545) A performance issue causing a timeout when previewing members who will receive bonus checks in the bonus rollout menu has been corrected. This issue should not occur again unless there is too much traffic on the server. |
Members | Protected member (TFS: 166838) When a member is set to Protected = 1, the member's email is blocked and it is not possible to change it. However, it will be possible to delete the email. If the member have not filled the email and is set to Protected = 1, the email field remains blocked. Setting bonus channel as “Letter” for member without address (TFS: 169539) The validation for the address has been added once the bonus channel is set to “Letter”. It is not possible to set bonus channel = Letter for a member without an address. The address is no longer required data on the member in Chain Web. It can be deleted from member details once the bonus channel is different than “Letter”. |
Member Campaign | Member campaign price rule validation (TFS: 167558) It is no longer possible to activate a Standard Campaign without setting discounted item price. Some improved translations has been added when validating price rule as well. Additionally, updating discounted item price in Standard Campaign will no longer disable the buttons in the command bar at the bottom of the screen. Minor Improvements in control group (TFS: 167603) When selecting "control group", the user is no longer required to adjust the percentage before adding the control group. The button is not greyed out when the default value (10%) is present. In addition to this, some missing Swedish translations were added. Retrying a campaign with a control group (TFS: 168311) If a member campaign with a control group for some reason failed, the retry button would cause the campaign to create duplicate control groups. This created issues with reactivating the campaign. This is corrected. UI improvements for member campaigns (TFS: 169915)
|
Member segments | Timeouts when including and excluding members in member segmentation (TFS: 167392) Due to an issue with caching in Redis, which is used in member segmentation, slowness and timeout occurred frequently for some customers when processing member segments. The performance for member segmentation should now feel significantly quicker. Requirements: Restart REDIS and clear caches in Redis-cli after installing a new POSServices. Go to path where Redis is installed and open "Redis-cli" - command prompt is open. Type FLUSHALL to clear the caches. After then go to services and restart Redis. Required versions of POSServices: 7.73.03009 or 7.74.03101. |
Member tags | Most frequently used store tag (TFS: 167103) When creating a member segment and selecting "most frequently shopped store", the value displayed contains store number and store name. Previously, only the number was displayed. Duplicate MostUsedStores tag on members (TFS: 169140) When a member's most used store was changed (when the member have more sales for another store), then the member should have been removed from the tag segment of the previous MostUsedStore. This did not happen and two different stores was shown on the member. It has now been corrected and the member can only be in one tag of type MostUsedStore at the same time. Requirements: The ReportingIntegration package version 1.9.3. |