...
Issue key | Summary | Description | Issue Type | Components | |||||
V5-6243 | Journal entries default code | When creating a Journal entry (for Account or Wallet), then assign a unique and random 16-digit code is assigned (if no code is not provided). The Journal entry code should be is displayed in the:
| Improvement | ACCOUNTS | |||||
V5-6254 | MongoDb missing information | Missing MongoDB information produces the wrong release reports data for:
| Bug | ANALYTICS | |||||
V5-6245 | Duplicate MongoDB Events | Duplicate Events logged in MongoDB (Invoices and Payments) | Bug | ANALYTICS | |||||
V5-6234 | Missing Contact information in MongoDB | Missing Contact information in MongoDB results in empty report cells showing on the Contact summary report | Bug | ANALYTICS | |||||
V5-6115 | Issue with custom fields criteria values in the footer of reports | Issues involving the criteria values in reports footer:
| Bug | ANALYTICS | |||||
V5-6242 | Enhanced default country and currency of the signed-up business | Enhanced default country and currency of the signed-up business to default to the service owner’s country and currency if the currency isn't specified during sign-up | Improvement | BUSINESS NETWORK | |||||
V5-6241 | Communication tag for email not replaced in communication | The communication tag for the contact's email address is not replaced in sent communications. | Bug | COMMUNICATIONS | |||||
V5-6295 | Unhandled error when accessing Contact statement | Unhandled error (414) when accessing the Contact statement. | Bug | CONTACTS | |||||
V5-6276 | Missing validation for duplicate contact code when creating contacts | Contact code must be unique across all contacts of a business. Missing validation. | Bug | CONTACTS | |||||
V5-6275 | Prevent Contact deletion if the contact owns a rented device | A Contact cannot be deleted (either through the UI or the Web API) if the contact still owns or rents a rented a device. The device must first be moved back to the business’s warehouse , and then to allow contact deletion of the contact. | Improvement | CONTACTS | |||||
V5-6266 | New Zealand phone number issue | New Zealand phone numbers issue. Business user cannot add a phone number (there’s an extra “0”) | Bug | CONTACTS | |||||
V5-6223 | Inconsistency in the number of contacts included in a Segment | There is a discrepancy in the number of contacts shown in a Segment on the Segments screen compared to the number of contacts displayed when the Segment is included as recipients in a Communication Plan. | Bug | CONTACTS | |||||
V5-5513 | Contacts Summary report issues | In some cases, a contact’s primary account and/or CRM.COM Wallet are not included in the report even though the contact owns a non-terminated account and a wallet. | Bug | CONTACTS | |||||
V5-6238 | Landing Pages & Mobile Pass Cards issue |
| Bug | MOBILE PASS CARDS | V5-6194 | Ability to set up Product Categories at the Service Owner | Ability to set up Product Categories at the Service Owner level that can optionally be used by Businesses signing up under the service owner. | New Feature | PRODUCT CATALAOGUE |
V5-6111 | Ability to update multiple products using a single Web API |
| Improvement | PRODUCT CATALAOGUECATALOGUE | |||||
V5-6229 | Ability to list Charity Organisations in self-service Web APIs | Ability to list Charity Organisations in self-service Web APIs, i.e. B2B Merchants of a business for which a Donation offer is set up. | Improvement | REWARDS CORE | |||||
V5-6294 | Issue when evaluating the 'rated up to date' of a service during service delivery deactivations | Issue when evaluating the 'rated up to date' of a service during service delivery deactivations. | Bug | SUBSCRIPTIONS | |||||
V5-6280 | Wrong Subscription state compared to service state | The subscription state is set to 'Churned' whereas the service is 'active'. The issue was caused due to the scheduled addition of the service, followed by the addition of the same service, which was then cancelled.
| Bug | SUBSCRIPTIONS | |||||
V5-6262 | Enhanced preview bill functionality for post-bill subscriptions | When previewing the bill of a post-bill subscription:
| Bug | SUBSCRIPTIONS | |||||
V5-6259 | Not effective subscriptions not billed for their usage | Subscriptions that are inactive on their billing day must be included during the billing run process if they have at least one 'Effective' day during the period that they are billed on a post-bill basis (and usage was consumed during that effective period). | Bug | SUBSCRIPTIONS | |||||
V5-6246 | Service wrongly gets billed while other services are deactivated | Service wrongly gets billed while other services are deactivated | Bug | SUBSCRIPTIONS | |||||
V5-6236 | Enhancements when subscribing to a flex bundle service | Enhancements when subscribing to a flex bundle service when the bundle includes default and mandatory components. Contacts automatically register to all components marked as default and/or mandatory | Improvement | SUBSCRIPTIONS | |||||
V5-6233 | Wrong remaining usage allowance for daily allowances | When a community member has a daily usage allowance, the remaining usage allowance returns the value 0. | Bug | SUBSCRIPTIONS | |||||
V5-6232 | Cannot update scheduled action for flexible bundle | Cannot update scheduled action for a flexible bundle. Flex bundle service is scheduled to be added on contact, and its scheduled date needs to be updated. On saving the change of action, a validation message is thrown saying that the service does not have components. | Bug | SUBSCRIPTIONS | |||||
V5-4652 | Ability to import Subscriptions, Services and their Devices | Ability to import Subscriptions, Services and their Devices. New dedicated Web API to be used for migration purposes and to migrate Subscriptions, their services and devices that contacts are already subscribed to and were billed and paying for in a third party system. | Improvement | SUBSCRIPTIONS | |||||
V5-6260 | Hide CRM.COM Cash Pocket Top-ups from Activity feed | Back end used must not be able to view Cash Pocket Topups of a consumer in the Activity Feed (similar requirement as hiding the Cash Pocket balance in the back end) | Bug | WALLET | |||||
V5-6253 | Application Settings issue | When “Contacts will be identified using their Wallet code in the form of X” is NOT set in V2 Apps settings, then on the front-end, the generated barcode includes the contact’s code instead of the wallet code. In v2 apps, this option must default to barcode (default create app behaviour) | Bug | WALLET | |||||
V5-6298 | Problem when scheduling reports from masqueraded B2B Merchant | The report was sent successfully, but the file was missing. | Bug | ANALYTICS | |||||
V5-6284 | Implement Facebook OIDC Login | Implement Facebook OIDC Login | New Feature | CONTACTS | |||||
V5-6269 | Contact type 'Company' Authentication OTP issue | When a contact of type 'company' requests an OTP, the email with the OTP is sent to the Admin's email even though the company contact has their own email. Change to: If the contact of type 'company' has an email, then send the communication to that email and not to the Admin email. | Bug | COMMUNICATIONS | |||||
V5-6268 | Issue when manually resuming a service from a paused period when contact has an overdue amount | Issue when manually resuming a service from a paused period when contact has an overdue amount | Bug | SUBSCRIPTIONS | |||||
V5-6258 | Issue with payment integration when adding a card | When adding a card and the language is invalid (due to migration of contacts), defaults to EN language | Bug | UTILITIES | |||||
V5-6249 | Do not create a settlement transaction if the contribution is 0% | Do not create a settlement transaction if the contribution is 0% | Bug | ACCOUNTS | |||||
V5-6247 | Inventory Devices page issues | The inventory Devices screen is to be merged with the View Devices screen, which includes bulk changes. | Bug | INVENTORY | |||||
V5-6073 | Transfer transactions should also be visible on the Activity feed of the destination contact | Transfer transactions should also be visible on the Activity feed of the destination contact | Bug | CONTACTS | |||||
V5-6050 | Issue when deleting a stage from a Lead Queue | When deleting a stage from a Lead queue and there's at least one Lead in that stage, the stage is deleted and the Lead is moved to a new stage, but the deleted stage is still visible in the UI. | Bug | LEADS |
...