5.7.2.5
CRM.COM release 5.7.2.5 includes the following features, enhancements & bug fixes:
Issue key | Summary | Description | Issue Type | Components |
V5-5924 | Payment terms are not set on the account when created through Contacts Web API | A Contact is created with an account using POST /contacts API, but the specified payment terms are not set on the account | Bug | ACCOUNTS |
V5-5887 | Include applied discounts breakdown in estimation Web APIs | Provide the ability to retrieve a breakdown of all discounts that will be applied when performing invoicing estimation. This includes invoicing estimation when previewing an invoice, an order to be placed and when previewing upcoming bills for a subscription. | Improvement | ACCOUNTS |
V5-5783 | Solidgate Payment Gateway | New Payment Gateway service: Solidgate | New Feature | ACCOUNTS |
V5-5915 | Account information not set in Mongo's Contact Profiles | Account information is not set in Mongo's Contact Profiles when a new contact with an account is created in the back-end. | Bug | ANALYTICS |
V5-5861 | Include Account Balance as a filter in the Contacts Summary report | Include Account Balance as a filter in the Contacts Summary report
| Improvement | ANALYTICS |
V5-5945 | Enhanced contact information available in CRM-entities |
| Improvement | CONTACTS |
V5-5941 | Include Contact Category in List Contacts Web API | Include Contact Category in List Contacts back-office Web API | Improvement | CONTACTS |
V5-5922 | Issue when creating a contact with a long phone number | Issue when creating a contact with a long phone number. Phone number includes 10 digits | Bug | CONTACTS |
V5-5925 | Issue when copying a Product | When copying a flexible bundle product, a validation message refers to Composite products and their modifiers. Investigate why the validation is shown and what it is trying to prevent. The expected behaviour is that the flex bundle and all of its compositions are copied to the new product. | Bug | PRODUCT CATALOGUE |
V5-5831 | Ability to view basic contact information on the Service Request screen | Ability to view basic contact (email and phone) information on the Service Request screen | Improvement | SERVICE REQUESTS |
V5-5031 | Service Request UI issue with Category | When adding or changing the category of a service request, the changes are not reflected on the UI unless you refresh the screen. | Bug | SERVICE REQUESTS |
V5-5952 | The ability for a community owner to share a usage allowance with all community members |
| Improvement | SUBSCRIPTIONS |
V5-5943 | Rounding issue in billing estimation | Rounding issue in billing estimation. Both bill preview and billing run to be checked | Bug | SUBSCRIPTIONS |
V5-5920 | Usage transaction information issue | The net amount, tax amount, and discount amount should be equal to the relevant invoice line amount. Change mongo transaction information and rating information of the get single usage api | Bug | SUBSCRIPTIONS |
V5-5919 | Issue when loading product categories on setting up usage allowance | Issue when loading product categories on setting up usage allowance. All categories must be returned when setting up:
| Bug | SUBSCRIPTIONS |
V5-5914 | Enhanced List Usage Records Web API |
| Improvement | SUBSCRIPTIONS |
V5-5913 | Ability to apply Promotions when billing rated Usage Records | Ability to apply Promotions when billing rated Usage Records. Usage to be billed based on the rated amount included in the usage record, but it is also eligible for any applicable Promotion configured in CRM.COM | Improvement | SUBSCRIPTIONS |
V5-5890 | The next payment date is not calculated correctly | The next Payment Date for a subscription is not calculated correctly. It does not consider the account’s payment terms, it’s calculated based on the default Payment Terms configured in the business rules. | Bug | SUBSCRIPTIONS |
V5-5880 | Ability to easily set up a member's allowance based on the owner's service usage allowance | Ability to easily set up a member's allowance based on the owner's service usage allowance. Instead of adding each individual product allowance per member, simply enable Usage Allowance for a community member and then specify that the member has the same usage allowance as the community owner’s service allowance. | Improvement | SUBSCRIPTIONS |
V5-5877 | Manage Community Person Usage Allowance | Provide the ability to list, query and consume a community person’s usage allowance through dedicated Web APIs. | Improvement | SUBSCRIPTIONS |
V5-5873 | Ability to perform preview billing in trial services | Ability to perform preview billing in trial services. Bill preview returns the expected date that the service will be billed and how much it will be billed (event-based/recurring charges also included). While in trial, though, the service cannot be billed in advance. | Improvement | SUBSCRIPTIONS |
V5-5868 | Enhanced Bill Preview information per subscription | Enhanced Bill Preview features:
| Improvement | SUBSCRIPTIONS |
V5-5867 | Additional Information in Usage Records Mongo Collection | Additional Information in Usage Records Mongo Collection:
| Improvement | SUBSCRIPTIONS |
V5-5929 | Issue with linking the CRM.COM Wallet | The customer registered to the front end and used a phone to create the CRM.COM Wallet. Then, a second contact tried to link their CRM.COM Wallet using the first contact’s wallet identity, which resulted in two contacts having the same wallet. Each contact should have a single CRM.COM Wallet, and the identity must be unique across businesses and within the same business. | Bug | WALLET |
V5-5921 | CRM.COM Wallet duplications | There is an issue when the POST wallets Web API is triggered twice for the same contact. The second call wrongly creates one more CRM.COM Wallet for the same contact. Validation needs to be added to prevent more than one CRM.COM Wallet for the same contact and within the same business. | Bug | WALLET |
V5-5960 | New Order webhook field name issue | Product type composition is named as typeComposition, rename to type_composition | Bug | USER EXPERIENCE AND TECHNICAL |
V5-5936 | Timezone issue in statement details api | The posted date in the statement_details API is returned in the time zone of the business instead of UTC. | Bug | USER EXPERIENCE AND TECHNICAL |
V5-5933 | Subscription action change service classification issue | When changing a service to a zero price service, the classification is not correct | Bug | SUBSCRIPTIONS |
V5-5930 | Service recommendation does not retrieve options for churned subscription | Service recommendation does not retrieve options for churned subscription | Bug | SUBSCRIPTIONS |
V5-5905 | OIDC configuration document is not cleared from redis | When the OIDC configuration for contacts is changed, the OIDC configuration document is not cleared from redis. | Bug | USER EXPERIENCE AND TECHNICAL |
V5-5891 | Issue with loading b2b organisation venues | Issue with loading b2b organisation venues | Bug | BUSINESS NETWORK |
V5-5883 | Passes report not sent | The passes report is not sent when no records are retrieved. Apply the fix to both the 'scheduled' and 'run now' options. | Bug | PASSES |
V5-5639 | Handle b2b purchase cancellation | Handle b2b purchase cancellation | Bug | CUSTOMER EVENTS |
V5-5447 | Issue when creating entities based on a queue - queue must be Active | When creating a new Service Request, the drop-down list to select the queue retrieves all service request queues. As a result, the user can select an ‘inactive’ queue, and then can’t save the Service Request unless they select one that’s ‘active’. | Bug | SERVICE REQUESTS |