5.7.3.7

5.7.3.7

CRM.COM release 5.7.3.7 includes the following features, enhancements & bug fixes:

 

Issue key

Summary

Description

Issue Type

Components

V5-6629

Issue when topping-up the CRM.COM Wallet via the backend

Commerce Pools are not available when a back-end user Tops-up the wallet due to the fact that no Commerce Pools are designated for use in such transactions.
Three key scenarios to consider:

  • A back-end user manually tops-up the wallet

  • A contact tops up the wallet using a single Commerce Pool

  • Top-up API triggered to initiate payment driven-flows

Bug

ACCOUNTS

V5-6384

Duplicate contacts created

Create a new contact via the back end and generate the CRM.COM Wallet. The initial wallet identity was not unique, so after validation, a correct one was assigned. While the contact was successfully saved, returning to the summary screen displays two contacts - one with a wallet and another without (the initially saved contact).

Bug

CONTACTS

V5-6601

Invalid error thrown in order estimates Web API

Order estimates Web API throws error about contact/wallet id not found. All info specified in the request are valid, the issue might be due to the fact that the wallet (CRM.COM Wallet specified as the payment method of the order) does not have enough money to cover the ordered items.

Bug

ORDERS

V5-6587

Passes Analysis report issue

Passes Analysis report shows just one pass being redeemed, but 2 passes were redeemed at the organisation.

Bug

PASSES

V5-6366

Enhanced Pass Redemption Traceability

Provide improved traceability of pass redemptions in Financial Events, Activity Feed and Contact Wallet Transactions Report

Improvement

PASSES

V5-6620

Product categories issues for SKU-based offers

Product categories issues for SKU-based offers:

  1. After changing category names, the categories in the Reward Offer still show the old names

  2. Categories cannot be expanded in reward offer conditions so as to select a sub-category.

Bug

PRODUCT CATALOGUE

V5-6600

Include owner organisation in List Products Web APIs

Currently, the “owner” organisation is supported as a filter in Search products self-service Web API. The “owner” organisation must also be included in the response (response object to include the identifer and the name) so integrators can utilise this information to retrieve the organisation’s details (address, images etc) in sub-sequent calls.

Improvement

PRODUCT CATALOGUE

V5-6556

UI Issue when seaching for prices of a product and no results are returned

When searching for an advanced contact price for a product with multiple prices, the search returns no results, indicating that no specific price exists for the contact. However, the "Will this service be billed?" toggle still appears and remains editable. This toggle should only be visible when the product has no price at all, but it incorrectly appears when a search returns no results.

Additionally, check if we can display the selected filter and its value after performing a search.

Bug

PRODUCT CATALOGUE

V5-6692

Service not deactivated on its expiration date

Service activated with a 10 days termed period/billing cycle. On its expiration date it was not deactivated. Service eventually got deactivated 10 days after. Deactivation must be enforce on expiration date even if credit limit is not exceeded.

Bug

SUBSCRIPTIONS

V5-6553

Ability to enable services of a flexible bundle to devices

Ability to enable services of a flexible bundle to devices.

Improvement

SUBSCRIPTIONS

V5-6127

Enhance Application settings to offer multilingual translations for Shortcuts 

Enhance the Application settings for Contact App and Contact Portal to allow users to provide translated versions of each shortcut option. Implementation should follow the same approach for translating Embedded Browser Links. 

Improvement

UTILITIES

V5-6694

Recommended products are retrieved from offers with timing conditions

Exclude products from offers with special day conditions (such as birthdays or name days) and consider only those with availability conditions, filtering them based on the current date.

Bug

PRODUCT CATALOGUE

V5-6659

Add Validations for identities on Organisation Register API

Add Validations for identities on Organisation Register API

Bug

BUSINESS NETWORK

V5-6651

Landing page - Show an error message for inactive landing pages

When navigating to an 'inactive' landing page link, display a meaningful error message on screen. 

Bug

UTILITIES

V5-6643

App Settings - New UI for new app type "Consumer Front End" 

Ability to set up and publish a new app that includes the configuration of both a Web portal and a mobile app in a single configuration.

Improvement

UTILITIES

V5-6630

Enhance Application configuration to allow GIF & Lottie files for carousel images

Allow back-end users to upload GIF & Lottie files for the App Carousel creatives in addition to existing jpg, jpeg, svg, png files

Improvement

UTILITIES

V5-6598

Erroneous 'from date' when retrieving or creating payment intents

When validating if pending intent exists for a contact, the 'from date' checks only based on billing period, regardless if there are any udrs related to the pending intent.

Bug

SUBSCRIPTIONS

V5-6586

Ability to include a rejected payment's error code in Insights

Investigate the possibility of including a rejected payment's error code in Insights.

  • When a payment intent is rejected.

  • In Automations > Subscription Payment Failure, the error code and description are successfully included using tags in user communications.

  • The same error code should also be available in the Payments Rejected UGD Insights export.

Improvement

ANALYTICS

V5-6581

Implement API Roles

Implement API Roles similar to User Roles but to be applied on API keys.

  1. API Role should be mandatory for all API Keys

  2. Existing API Keys without API Role should be able to access all APIs

  3. To investigate which permissions should be available for API Roles it should be a subset of the User Role permissions

New Feature

SECURITY AND USERS

V5-6576

Award conditions for reward offers shouldn't allow zero values

Introduce a validation on the backend to prevent users from saving the reward offer if it has a 0 award value.

Bug

REWARD OFFERS