5.7.4.1
CRM.COM release 5.7.4.1 includes the following features, enhancements & bug fixes:
Issue key | Summary | Description | Issue Type | Components |
V5-7301 | Avalara taxes were not applied due to missing country code in contact's address | Avalara taxes were not applied due to missing country code in contact's address | Bug | ACCOUNTS |
V5-7363 | Ability to include the entity for which a Credit Note was issued in Insights exports | Ability to include the entity for which a Credit Note was issued in Insights exports
| Improvement | ANALYTICS |
V5-7360 | Service Recommendation Web API not applicable for the guest contact | Service Recommendation Web API not applicable for the guest contact | Bug | APP & PORTAL NG V2 |
V5-7340 | Ability to search for Merchant and Venue using TAP codes | A user can search for a Merchant or Venue from the respective Business Network screens using a TAP code. Also supported when masquerading. | Improvement | BUSINESS NETWORK |
V5-7065 | Ability to set up multiple email aliases when sending email communications | Ability to send more context-appropriate and professional communications to contacts by using dedicated sender identities (e.g. billing@business.com, sales@business.com, marketing@business.com), while maintaining compliance with SMTP verification rules. | Improvement | COMMUNICATIONS |
V5-7107 | Ability to dispatch traceable, non-stockable physical goods | Provide the ability to fulfil Orders for traceable, yet non-stockable physical goods for the business, i.e. physical goods for which the business does not maintain stock balances in its CRM.COM Inventory. | Improvement | INVENTORY |
V5-7264 | Ability to have initial payment for an Order when it reaches its Point of no Return | Ability to have initial payment for an Order when it reaches its Point of no Return, i.e. the Order is invoiced not upfront (on placing the order) but automatically when the Order reaches the stage which is marked as the PoNR. | Improvement | ORDERS |
V5-6826 | Ability to support multiple Delivery Methods | Ability for an organisation fulfilling Orders to determine the method of delivering orders with the Delivery supply method; either Direct Delivery, Courier Service or Pick-up point. | New Feature | ORDERS |
V5-7315 | Reward Tier not downgraded after purchase was cancelled | Reward Tier not downgraded after purchase was cancelled | Bug | REWARDS OFFERS |
V5-7350 | Issue when setting and updating subscription-related information in MongoDB | Issue when setting and updating subscription-related information in MongoDB | Bug | SUBSCRIPTIONS |
V5-7335 | Issue when order completed and topup fired at the same time | Issue when order is completed and top-up is fired at the same time | Bug | SUBSCRIPTIONS |
V5-7263 | Ability for contacts to provide comments when rejecting an Approval Request | Ability to provide comments when rejecting a Contact or User Approval Request | Improvement | Utilities |
V5-7262 | Ability for back-end users to accept or reject a Contact's Approval Request | Ability for back-end users to accept or reject a Contact's Approval Request, i.e. provide a response for the approval on behalf of the customer. | Improvement | Utilities |
V5-7356 | Fix OTP Estimation Blocking Rejection & Add Contact Tracking to Unblock Funds | When an estimation with OTP is created during a purchase flow, the blocking process does not correctly handle rejection. As a result, blocked amounts are not linked back to the originating contact, preventing proper unblocking. This enhancement will introduce the contact ID into the estimation information so we can always identify the source contact and unblock funds reliably. This also resolves the edge case where a user generates an OTP, performs an estimation, and then waits too long—leading to an OTP failure during purchase creation. With the contact ID stored on the estimation, the OTP state will no longer break the flow. Additionally, once the OTP is used for blocking, it must be deleted immediately to avoid reuse. | Bug | ORDERS |
V5-7353 | Ability to keep track of an error during approval accept/reject | Currently, if something goes wrong while accepting or rejecting an approval request, the contact sees a generic message saying that something went wrong. We should notify the contact that their approval/rejection did go through, but we should keep track of the error during the process. On the back-end for example we will show that Order has been approved but also show the error for the user to investigate | Improvement | Utilities |
V5-7351 | Credit note created after cancellation of order is not linked to order number | Add relation information on the credit note based on the invoice that is cancelled | Bug | ORDERS |
V5-7347 | Product Synchronisation issue | Product Synchronisation issue with images. If an image is provided but it's the same as the existing one, don't delete the previous and then add the new one | Bug | Utilities |
V5-7337 | Issue when redeeming a single pass code for multiple contacts | A pass plan is configured for a promotion using a single pass code. User manually redeems the pass for the contact’s subscription service. After the first two passes, the error ‘Cannot redeem the pass. Is not applicable for any subscription service’ is thrown. Also, for the first two passes that were redeemed, the pass value is not shown on the ‘Manage Passes’ screen (The issue with the contact details of the pass redeemer not appearing on the ‘Manage Passes’ screen is being addressed in another ticket (UX/UI issues). | Bug | PASSES |
V5-7323 | Merchant to contact transfer not shown on merchant's Activity Feed | When a Merchant performs a transfer of funds from their Account to a Contact’s Wallet, the transfer is shown correctly on both statements and the contact’s Activity Feed, but not the Merchant’s Activity Feed. | Bug | BUSINESS NETWORK |
V5-7289 | Commerce Balance Not Blocked During Wallet Funds Blocking | When the block wallet funds process was triggered (for example, during an estimate purchase), only the total wallet balance was being blocked. | Bug | ORDERS |
V5-7244 | Lottery offer - ability to exclude products for transaction amount | For Lottery offers, provide the ability to exclude certain products (based on SKU, product family, product brand, product type and product category) from the transaction amount being evaluated. | Improvement | REWARDS OFFERS |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|