5.5.3.2

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

Issue key	Summary	Description	Issue Type	Components
V5-3629	Issues with the issuing and posting date of billing run invoices	Billing run was performed on 1st of November so 'Posted date' was correctly set as 1/11 but the 'Issued date' was set to 31/10 When issuing the statement of the contact, that billing run invoice is not included in November's statement (this month option) but it appears in Last month's transactions (even if we switch to October, we can see that the transaction date in the statement says 1st of Nov.) Also verify 'issue date' and 'posted date' communication tags use the correct info	Bug	ACCOUNTS
V5-3612	Introduce new payment method type: Electronic Transfer	Introduce a new payment method type called 'Electronic Transfer' that will be used to post offline payments such as Bank Transfers and POS payments	Improvement	ACCOUNTS
V5-3594	Ability to retrieve enough funds to pay off an account's balance	Ability to set up a behaviour for payments-on-file during the billing run. By default, the billing run tries to retrieve enough money in order to pay off the invoice to be generated. This behaviour can be overridden by enhanced Financial Rules according to which, on each billing run, the process requests the bill amount plus the overdue amount of the account that is being billed.	Improvement	ACCOUNTS
V5-3440	Enhancements to contact statement	Statement enhancements: Swap the 'credit' and 'debit' columns 'debit' first then 'credit' Add the ability to print from the UI Transfers In the 'Details' column show the transfer from/to (especially when transferring between accounts of different contacts Transfer EUR10 transferred from Account A0001 Transfer EUR10 to account A0002 Same applies for transfers from/to accounts/wallets Swap the places of the 'account 'and 'wallet' summaries at the top of the statement	Improvement	ACCOUNTS
V5-328	Ageing Feature	Ability to perform an analysis of aged debt of contacts The Ageing analysis is the process that identifies unsettled Invoices and classifies them as Aged Invoices. An Invoice's age denotes how long the invoice has been due for (i.e. how long it is aged since its posted date).	Story	ACCOUNTS
V5-3513	Creating an Activity for a Lead throws error 404	Creating an activity for a Lead throws error 404	Bug	ACTIVITIES
V5-3256	Activity improvements	Display activity created time alongside the date (existing) on the activity screen Display activity completed date and time on activity screen Automations a. 'Schedule Activity' renamed to 'Create Activity' b. New automation trigger event 'Activity Owner Changed' 4. New communication tags a. #linked_entity_description b. #linked_entity_contact_name c. #activity.owner (user or team assigned to the activity)	Improvement	ACTIVITIES
V5-2557	New Report: Debtors	View a list of contacts with an outstanding debt to the business. The report includes the total outstanding amount per account owner as well as for how long the debt is due, separated into 5 ageing buckets of 30 days each. Ageing analysis is performed using the transactions' posted date	New Feature	ANALYTICS
V5-959	Organisation State Enhancement	New 'state' (active, inactive) attribute added to organisations, and core behaviour (purchases, list merchants) should comply to that attribute	Improvement	BUSINESS NETWORK
V5-3621	Ability to define whether to communicate the contact statement per month or year	Ability to define whether to communicate the contact statement per month or year. In the first case, which remains as the default option, the contact receives the statement of the current month. Otherwise the contact receives the statement of the current year. New communication tags: #contact.monthly_statement #contact.annual_statement Note: If a contact has multiple accounts, then only the default (primary) account statement will be sent (via communication plans)	Improvement	COMMUNICATIONS
V5-3605	Product description missing from service request charges communication tag	Product description should be included in 'service_requests.charges' table communication tag (displayed under the product SKU/name), show the first 100 characters followed by elipses '...' - same as in invoice lines tags This should also be supported for service request templates and automations.	Bug	COMMUNICATIONS
V5-3521	Include a Service Request's Address as a communication tag	Provide the ability to include the address of a service request in the entity's communication templates	Improvement	COMMUNICATIONS
V5-3380	Ability to search for a contact using the full phone number	List Contacts' API enhanced to allow searching using a full phone number, i.e. combining the country code and the phone number (e.g. 35799778866).	Improvement	CONTACTS
V5-3341	Enhanced Contact address selection across the software	Use same address component when searching and setting a contact's address in various processes such as Activities, Orders, Service Requests and Subscriptions	Improvement	CONTACTS
V5-3603	Ability to set the date that the device was first activated on a subscription	Set the date that the device was first activated on a subscription, and the initial user that performed the activation. This should not change at any point in the future.	Improvement	INVENTORY
V5-3622	Search for orders based on their address	Ability to search for an order using its delivery address. New 'Address' filter option added	Improvement	ORDERS
V5-3604	Warehouse transactions UI enhancements	Include detailed info per warehouse transaction, like the entity for which it was issued e.g. Order / Service Request / Invoice Entity number Include it on the UI in a new box right under the description box on the left e.g. Order: O00001012	Task	ORDERS
V5-3416	Ability to change an Order's Delivery address	Ability to change an Order's Delivery address before its completion. Changing the delivery address is allowed only if no items have been sent out to the contact. Order fulfillment estimation should be triggered again to ensure that the order can still be fulfilled at the new delivery address	Improvement	ORDERS
V5-3485	Ability to redeem a pass during contact registration from a landing page	Enhance landing page configuration for Contact Registration to allow redeeming a pass. When a consumer registers through the landing page and also provides a pass code, the new contact will be created as normal, and in addition the 'redeem pass' process will also be performed. If successful, then the new contact's wallet will be credited with the value of the pass.	Improvement	PLATFORM
V5-1660	Authentication with OIDC	OIDC for authentication integration from-to 3rd party systems Self service and back office Support for SSO Initial support for Microsoft 365	Story	PLATFORM
V5-3557	Ability to support front end reduction at Transaction Processor level	If a Transaction Processor submits purchase events with a spend request then match it to the contact who submitted the spend request for the specific (one) business process the request in sync mode	New Feature	REWARDS CORE
V5-3255	Service Requests new and improved features	Ability to create a SR from the Contact screen Ability to define one or more root Categories per SR queue a. Select root category, or child of root category on SR 3. Ability to add a comment at each stage of the queue for a SR (once achieved) 4. SR automations: a. New trigger event 'SR owner changed' b. Rename all occurrences of 'status' to 'stages' in filters 5. Increase the comment size when completing the SR a. Enlarge the modal so that it fits more than 4 lines of content without having to scroll up/down	New Feature	SERVICE REQUESTS
V5-3550	Subscriptions summary screen issues & enhancements	Subscriptions state not working properly. Search for 'inactive' subscriptions only, all subscriptions are retrieved (despite state being included in the API filter) Number of services a. Should show how many 'Active', 'Inactive', 'Draft'. Now it shows all as 'Active' 3. Add new filters a. Active since b. Next renewal on	Task	SUBSCRIPTIONS
V5-2713	Ability to regret a service	Provide the ability to regret a subscription service Regretting a service is allowed only within a period of time after subscribing to it. The rules are defined in subscription settings Within the allowed period of time, the service is additionally credited. After this period, the service cannot be regretted and it has to be cancelled	New Feature	SUBSCRIPTIONS
V5-3559	Gateway Enhancements	Ability to support gateways like lambda with gateway api key	Improvement	USER EXPERIENCE AND TECHNICAL
V5-3635	Issue with wallet passes and test mode	Issue with wallet passes and test mode	Bug	PLATFORM
V5-3633	Issue when deleting a Partner	When deleting a Partner record, the corresponding Organisation Partner records are not deleted. The solution in this case is to delete those records manually (instead of validating that the Partner is not used anywhere before deleting like we usually do)	Bug	PLATFORM
V5-3624	Landing Page not activating	Can’t activate a Landing Page.	Bug	PLATFORM
V5-3623	Issue when viewing/selecting a contact's payment methods	Contact has an account debit payment method When selecting to view the contact's payment method, only the first two fields are shown as read-only, and the payment gateway appears as empty. When making a payment, user selects 'account debit' as the payment method type, however, no contact payment methods are returned.	Bug	CONTACTS
V5-3619	Images chosen according to resolution needed	For uploaded images, use the creatives array to get the image with the closest next largest size	Bug	USER EXPERIENCE AND TECHNICAL
V5-3606	Improved Orders management	Ability to amend order items and milestones, provided a point of no return is not reached	Improvement	ORDERS
V5-3595	Order view screen issue with paging		Bug	ORDERS
V5-3532	Custom Fields filtering issue on summary screens	When a Contact custom field is configured using a field 'type' which already exists as a field in Contacts, and the custom field type is selected on the summary screen, filtering throws an error because there is no way to distinguish between the custom field and the entity field.	Bug	PLATFORM