5.6.7.0

Release CRM 5.6.7.0 includes the following features, enhancements & bug fixes:

 

Issue key

Summary

Description

Issue Type

Components

 

 

 

 

 

V5-4928

Allocation issues caused by manual journal entries

Allocation issues causes by manual journal entries. Debit journal entry not allocated to another credit journal, therefore invoices issued after that were allocated to the credit journal entry.

Bug

ACCOUNTS 

 

 

 

 

 

V5-4927

Minor UI/UX Issues & Enhancements 

  1. Remove hardcoded label 'Notes:' from journal entries records in contact and organisation statements.

  2. When making a payment, unpaid invoices are loaded, but once selected as intended invoices, their total amount is not shown in UI (although returned by the Web API).

  3. When placing an order and there’s a single allowed payment method, then select that method by default (so user does not have to manually set it on each order). 

Improvement

ACCOUNTS 

 

 

 

 

 

V5-4797

Incorrect validations thrown when placing orders/service requests

Incorrect validations thrown when placing orders/service requests. Neither can be created due to the contact having an outstanding amount:

  • Order should be allowed even if contact has outstanding amount but only as long as the credit limit is not exceeded on placing the order. If the order creates a subscription, then service delivery process might fail the service’s activation due to outstanding amount, but the order is still placed.

  • Same in Service Requests.

Bug

ACCOUNTS 

 

 

 

 

 

V5-4848

Enhancements on Activities and their Automations

  1. When creating an Activity through an entity, a user should be able to assign it to either a Team or a User

  2. When editing the scheduled date of the activity, it should default to the same date (i.e. should not need to set it again).

  3. Provide more options to set the activity details when configuring an Activity Scheduling automation. 

a) Scheduled date options: Immediately OR in X hours/minutes
b) Assign Activity  to either a team or a specific user or leave blank to assign to the user who initiates the related entity (for example the user who creates the order/service request or lead)
c) Ensure that the activity type is included in filters

Improvement

ACTIVITIES

 

 

 

 

 

V5-4986

Include Account Classification in Contacts Financial Analysis report

Include Account Classification in Contacts Financial Analysis report (filter, column, group).
Also, Wallet state filter/column must be removed, it’s no longer applicable. 

Improvement

ANALYTICS

 

 

 

 

 

V5-4957

GET Settlement Transactions API improvement

GET /settlement_transactions API enhanced to improve performance. Every API call was retrieving a lot of purchases from another microservice. Added include_purchase query param to reduce response time. 

Improvement

ANALYTICS, REWARDS CORE

 

 

 

 

 

V5-4941

Add a preview button to generate insight graphical charts

Added a 'Preview' button for graphs in Insights.

Improvement

ANALYTICS

 

 

 

 

 

V5-4933

Accessibility. Change behaviour accessibility across network to not include B2B merchants

Amend core behaviour of product accessibility

New Feature

BUSINESS NETWORK

 

 

 

 

 

V5-4889

Enhanced Contact (self-service) Communities

Ability for a contact who is a community member to leave a community that they have been added to.

Improvement

CONTACTS

 

 

 

 

 

V5-4706

Ability to support configurable device locations

Ability to maintain configurable locations for stockable items in the warehouse

Improvement

INVENTORY

 

 

 

 

 

V5-4637

Leads management issues

  • Leads detail screen- select to change the state of a Lead to Lost. Modal opens where a Lost reason should be specified. If there are no Lost Reasons configured, then there’s no need to show the modal (same change implemented for Orders).

  • Apply the same logic to the Leads Kanban & List view screens.

Bug

LEADS

 

 

 

 

 

V5-5007

Enhanced Twinsoft integration so as to avoid keeping Orders in progress.

Orders provisioned to Twinsoft remain in the 'In Progress' state due to missing information in the request sent to Twinsoft. during integration CRM.COM should also include the CustomerCardNo or CustomerCode in the request.

Bug

ORDERS

 

 

 

 

 

V5-5001

Ability to trigger Webhooks through Automations for a new event called 'Prior Order Creation'

Ability to trigger Webhooks through Automations for a new event called 'Prior Order Creation'. It's purpose is to perform custom validations before placing an order.

Improvement

ORDERS

 

 

 

 

 

V5-4969

Automations for Orders not working properly

Automation is configured so as to send email communication to the owner of the fulfilled by organisation of an Order. However, no email was sent.

Bug

ORDERS

 

 

 

 

 

V5-4998

Reward Offers usability enhancements

  1. Include a Reward Offer’s availability period in summary screen results (same as in Promotions)

  2. Enhanced default filters (2 existing and 2 new);

a) 'All Active': returns offers in Active state (regardless of availability)
b) 'All Inactive': returns all offers in Inactive state (regardless of availability)
c) 'All Running Offers': All offers in Active state and current date within their availability period (also the default filter)
d) 'All Expired': returns all offers whose availability period to date is in the past (regardless of their state)
e) 'All Future': returns all offers whose availability period start date is in the future (regardless of their state)

  1. Remove 'Expired' from the filters in the summary screen (deprecate from Web APIs as well).

Improvement

REWARDS OFFERS

 

 

 

 

 

V5-4970

Enhanced UI of Service Requests queues - Application settings

UI of Service Request queues Application settings must provide the ability to select either a 'team 'or a 'user' to assign the SR to. Currently only 'user' is available.

Improvement

SERVICE REQUESTS

 

 

 

 

 

V5-5009

On replacing a device, its distributions to services are not updated

Service is provisioned by device A. On replacing the device with another one, the service should be automatically provisioned to the new device (i.e. replacing a device also re-adjusts the distributions).

Bug

SUBSCRIPTIONS

 

 

 

 

 

V5-4921

Include 'Pending changes' badge when subscription is churned

Subscription is in churned state but there’s a scheduled addition of another service (subscriber churned the subscription and then ordered another one). User should be able to switch into viewing churned subscriptions as well and then for this subscription they will also be able to view whether there are scheduled changes (shown as a 'Pending changes' badge.

Bug

SUBSCRIPTIONS

 

 

 

 

 

V5-4849

Ability to maintain a usage record's external reference

Ability to set an external reference number for each usage record created in CRM.COM by the third party system that keeps track of this usage consumption.

Improvement

SUBSCRIPTIONS

 

 

 

 

 

V5-4671

Price change issues

Price was configured for a service, and then its trial period was changed. The Contact subscribed after the change and got the initial service’s trial period.

Bug

SUBSCRIPTIONS

 

 

 

 

 

V5-5008

License restricted access issues

Various processes cannot be performed by a back-end user due to License restrictions. Restrictions are correctly applied BUT the back-end user cannot see this unless they do an inspect and view the reason of Web API failure.
Examples:

  • Add provisioning provider settings to a product - restriction due to missing license for Subscriptions.

  • Change credit limit  - restriction due to missing license for Account based model.

Error 403 to be captured and displayed in the UI

Bug

Utilities

 

 

 

 

 

V5-4965

 Grammar & Spelling

Grammar and spelling mistakes corrected on back-end UI.

Bug

Utilities

 

 

 

 

 

V5-4938

List Wallet Journal Transactions self-service API is missing some transactions types

GET /wallets/id/transactions self service API is missing the following transaction types in the response:

  • Wallet Payment

  • Transfer

  • Manual Journal

Also check for any other types which may be missing too. 

Bug

WALLET

 

 

 

 

 

V5-4471

Block wallet funds

Ability to block a specific amount of money in the CRM.COM Wallet and for a specific period of time. Applicable for any process that requires wallet funds to pay off a contact’s purchase (purchase, orders).

Improvement

WALLET

 

 

 

 

 

V5-4997

Wrong prices retrieved on ordering service flexible bundles

Flexible bundle is configured having various components. Both the bundle and the component have various prices. On each order a different price is shown to the user. 

Bug

SUBSCRIPTIONS

 

 

 

 

 

V5-4996

Webhook Idempotency

Add an id field to each webhook which will be unique to that webhook request in order for clients to be able to handle duplicate calls. 

Task

USER EXPERIENCE AND TECHNICAL

 

 

 

 

 

V5-4988

Reward Offer availability issue

The miscalculation of reward offer availability resulted in the offer being available for one day less than intended.

Bug

REWARDS OFFERS

 

 

 

 

 

V5-4978

Segment issues

Fixed 'Save' segment issue
Fixed manual refresh segment issue
Fixed filter products on segments (remove distinct )

Bug

CONTACTS

 

 

 

 

 

V5-4973

Implement Cardlink Payment Gateway

Implement Cardlink Payment Gateway

New Feature

USER EXPERIENCE AND TECHNICAL

 

 

 

 

 

V5-4971

Lottery should run even if the validity date has passed

Remove validity date check to allow lottery draw to run

Bug

REWARDS OFFERS

 

 

 

 

 

V5-4968

Users pending invites not showing

Number of pending invites message is missing from Users screen.

Bug

SECURITY & USERS

 

 

 

 

 

V5-4967

Contact phone is removed on update contact

Contact phone is removed on update contact

Bug

CONTACTS

 

 

 

 

 

V5-4964

Merchant products issue

Issue where some products (with specific merchant accessibility) not available on merchant

Bug

BUSINESS NETWORK

 

 

 

 

 

V5-4960

Issue on response of list organisation payment methods API

The API list organisation payment methods response has an inconsistency compared to the list contact payment methods API response. Specifically, the account_debit.gateway_token array should change to match the response of the contacts payment methods API.

Bug

USER EXPERIENCE AND TECHNICAL

 

 

 

 

 

V5-4959

Add service contact page issue

Add service flexible bundle  not showing component to select

Bug

SUBSCRIPTIONS

 

 

 

 

 

V5-4952

Create Pass issue

There is an issue with POST /backoffice/v1/passes/generate related to adding custom fields on pass.
It should add the custom fields from pass plan and overwrite them with the custom fields added on the POST request.

Bug

USER EXPERIENCE AND TECHNICAL

 

 

 

 

 

V5-4947

JCC SEPA issues

  1. HTTP client not closed issue

  2. On API POST/PUT payment_gateways/payment_methods the  account_name field should be mandatory and less than 70 characters in length.

  3. Delete response file and store the response file in the DB

  4. A change to reject payment intents that do not have the required fields set, don't send them to JCC

  5. When the plugin receives POST /intent we should validate and reject the request if it's missing the account name, bankcode, iban

  6. Whenever plugin calls the PUT /payment_intents  action to reject we have to pass two new parameters - error code and error description.  

Bug

USER EXPERIENCE AND TECHNICAL

 

 

 

 

 

V5-4942

Contact page issue

  • If name is too long, use ellipsis instead of displaying th whole name

  • Update name not working

Bug

CONTACTS

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

V5-4825

V5-4937

Enhance Event to handle context type

Enhance Event to handle Context type and subtype in order for the information regarding the caller type to be transferred between microservices in cases of communication using Kafka

Task

USER EXPERIENCE AND TECHNICAL

Validate Contact in V2 SelfService APIs

When a self service api is called, the contact has to be validated against the requested resource to make sure that the contact has access to get, modify or create such a resource.

Task

CONTACTS

V5-4616

Automation Webhook use structured events

Use Dtos for webhooks data

Task

USER EXPERIENCE AND TECHNICAL

 

 

 

 

 

V5-4452

Update price only on product prices

Allow updating only price, instead of price and tiers for future prices. Also set logic for usage allowance related to price.

Bug

SUBSCRIPTIONS