Authentication | Password failed requirements prompt no longer appears when you attempt to change your password to an invalid one (JMC-6652)
Customer | Clicking Edit on ValidateCustomerAddress screen on Customer-display exits out of customer sign up (JMC-6968)
Customer | Confirmation dialog for rejecting customer signup terms & conditions was errantly removed during refactor (JMC-6905)
Customer | Terms and Conditions prompting when Editing Customer (JMC-7037)
Customer | When looking up remote trx in customer's purchase history, ¯_(ツ)_/¯ when remote service offline (JMC-7000)
Customer | ¯_(ツ)_/¯ when attempting to parse invalid customer during appt checking (JMC-6813)
CX Connect | Customer display is returning to the home screen after a partial tender is completed (JMC-6909)
Internationalization | Enhance the About modal title to support i18n (JMC-6885)
Internationalization | When i18n_resource entries exist in DB for certain locales (en_US, fr_CA), resource found for other locale (es_MX) defaults to en_US entry in DB instead of entry in es_MX .properties file (JMC-6924)
Order History | NPE in order history data provider causes following data providers to not execute (JMC-6957)
Payment DeviceAurus | GetCardData doesn't account for collectTokenOnly parameter and leads to confusion with the displayed tender amount (JMC-7117)
Publisher | Financial control transactions (pay in, etc.) are being published twice (JMC-6959)
Receipt | Credit details section is printed on the Receipt for PayByLink when the tender is made through PayByLink + Cash (JMC-6992)
Returns | ParentOrderId parsed as long (JMC-6917)
Self Checkout | Quantity adjusted in Associate Mode does not display properly in SCO Mode (JMC-6859)
Tax Exempt | Tax Exempt Search allows for searching with empty values (JMC-6886)
Technical | ICustomerSaleService missing mapping for /customer (JMC-7106)
Technical | pubeng_subscriber_webhook should support URLs > 128 characters (JMC-6873)
Training Mode | Training mode causes sequence number to be reset (JMC-7149)
The ITransMgmtService.addTenderControlTrans(AddTenderControlTransRequest) API and related TenderMgmtClient.addTenderControl(String, String, String, String) method have been removed. The methods were not being used in base Commerce. (JMC-6959)
The configuration openpos.returns.splitStoreAndOrderItemsIntoSeparateReceipts and its associated logic has been removed. (JMC-6917)
Authentication | Password reset after expiration does not use the configured password validators. (JMC-6636)
Close till | Expected amount increments each time a user closes the tlll without reconciling on the same day (JMC-6775)
CX Connect | Freeze in ADP flow on customer display (JMC-6369)
CX Connect | Stops communicating when it switches from ethernet to wireless (iPorts tend to do that) (JMC-6586)
CX Connect | When a customer links their loyalty from CX Connect while the associate is performing a manual item discount the customer is never linked (JMC-6579)
Gift Card Cash Out | Canceling transaction after backing out of Add Customer on Gift Card Cash Out brings up receipt options (JMC-6685)
Orders | Buddy Store Inventory Table Not Populated on Product Details Screen Due to API Delay (JMC-5379)
Orders | Order statuses not showing correctly on sale screen when going to checkout during pickup process (JMC-6738)
Orders | Shipping Address is not being displayed on the repeat delivery flow in ADP even though it is valid on the CRM. (JMC-6719)
Orders | When adding 2nd item to order, no order ID displays on sale screen for that item (JMC-6783)
Payment | /pay/returnAuth/ endpoint is not mapping token for Adyen (JMC-6838)
Payment | Cloud and Local Adyen client can't share the same CustomerAdyenHttpClient (JMC-6726)
Payment | Swipe ahead is not working with Aurus payment provider (JMC-6776)
Personalization | Devices fail to personalize after iOS app update (JMC-6908)
Personalization | If you personalize manually after an initial load the list of business units are not available because the cache is empty (JMC-6845)
Personalization | Parameter from auto-personalization makes its way into device's tagsand is invalid column name when querying DB (JMC-6821)
Promote | When only excluded item is added in the cart for single use coupon the exclusion message is not been displayed. (JMC-6464)
Refund | Exchange being returned (original CC/exchange GC) is presenting (wrong) amount for refund to card (JMC-6258)
Returns | Processing is slow with large baskets because the transaction is looked up twice and details dialog makes too many calls to find original transactions (JMC-6711)
Returns | Return amount incorrectAmount is off by 1 cent (JMC-6852)
Returns | Sale items are being shown on the returns screen (JMC-6809)
Returns | Shrug error during receipted return when item not found (JMC-6796)
Shopkeeper | Enable Shopkeeper sale tracking features (JMC-6374)
Technical | Inaccurate printer statuses reported by POS printers (JMC-6799)
Technical | Incorrect versions are being recorded for several micro service endpoints in the xxx_microservice table. (JMC-6743)
Technical | Offline Exception not being handled when invalidating bounce backs (JMC-6758)
Technical | Operational transactions like no sale and pay in/out are not updating the client's transaction number which could cause reuse of transaction numbers when failing over to the cloud (JMC-6691)
Technical | Publisher fails to start due to missing bean (JMC-6833)
Technical | Trans_User_Action Model not created on customer signup (JMC-6761)
Technical | Transaction numbers skipped after no-sale, cash up/down, etc. (JMC-6801)
Technical | Update CustomerClient.saveContactPreferences to not reassign customer object when response does not return a customer (JMC-6840)
Technical | With immediate disconnect and reconnect dialog showing device already connected (JMC-6617)
Tender | "New Card" Tender for mixed cart containing a special order is not working (JMC-6890)
Tills | Detailed reconciliation screen shown for non-cash tenders (JMC-6780)
Tills | Till threshold config is not being honored at the database level. (JMC-6615)
Transaction History | Customer transaction history only shows 'Purchased HH:MM:SS at this store' and should include the date as well (JMC-6680)
Usability | Date Part Chooser should require that all Date parts for the selected mode have been selected before OK (JMC-6704)
Usability | Due to rendering issues on the iPad, update Add Returns Customer Form to be single column (JMC-6839)
An additional configuration has been added to allow for look-ups based on either the user's username or alternateId, openpos.user.authentication.useAlternateIdForValidation. If it is false, the user's username will always be sent as a part of the validation request even if alternateId is the entered value.The following i18n properties in the user bundle should be updated or added: login.passwordprompt should be updated with a parameter to display the username as a part of the prompt login.password.validation.give.requirements should be updated with a parameter to display the username as a part of the prompt login.password.validation.give.requirements.withUser should be added with 2 named parameters, username and alternateId, to display both the username and the alternatedId as a part of the prompt. (JMC-6470)
Use openpos.orders.bispis.billingAddressRequired and openpos.orders.shipToStore.billingAddressRequired to enable the billing addresses. Billing addresses are enabled by default. (JMC-6514)
Added a new suggestionAcceptedFlag to the billing and shipping address. (JMC-6513)
To enable validating the customer for the order with the shipping address set: openpos.orders.useShippingAddressForValidation = true for delivery orders openpos.repeatDelivery.useShippingAddressForValidation = true for repeat delivery orders. (JMC-6719)
This version and forward database downgrades will not happen automatically. For a downgrade to happen you would need to manually update the xxx_microservice.current_version table to the version you want to downgrade to. (JMC-6747)
The CUSTOMER_SEARCH transaction type that was added in 243.5 is no longer supported. It is replaced with the USER_ACTION transaction type that is only recorded at logout of a user when there are user actions that are not tied to a sale. The USER_ACTION transaction type feature is turned off by default.nullnullUse openpos.sale.userActionTrans.enabled to enable USER_ACTION transactions. SLS_TRANS are only recorded with a type of USER_ACTION if the action takes place outside of a sale. (JMC-6630)
The promotion cache is no longer keyed by the local server time only. Effective promotions are read into memory from 24 hours ago including all future dated promotions for active business units. When asking the repository for a promotion they are filtered in memory. The only setting that is still valid for configuring the promotions cache is cacheRefreshCronExpression. (JMC-6694)