
TOT-3313 - Customer Account Invoice Line Report content managed web page areaA new content managed web page area has been created called "Customer Account Invoice Line Report". This area can be used to show a list of invoice lines that have been obtained via a request the Connector software, which has been configured to obtain a list invoice lines for the user's customer account based on a specific report. This allows the area to show reports such as "Top Ordered Products" or "Ordered Products Awaiting Delivery". These reports can be generated based on data in a given Enterprise Resource Planning or Accounting System. Or otherwise from an ODBC database, or spreadsheet file.
Once the invoice line data is returned the area can optionally match the invoice lines to products in the TOTECS project, which can then allow the user to add the product lines in the report to their basket and purchase more products.The are contains the following formats:
TOT-3314 - Sales Rep Customer Account Selection content managed web page areaThere is now the ability to create a Sales Rep Customer Account Selection content managed web page area, that can show a list of users and associated customer accounts that a sales rep user can switch to.
The area will only display if the user viewing it is set as a sales rep user, and that they are assigned to a facility permission role that has the "View Sales Representative Briefcase section" permission set to Allow.
The are contains the following formats:
TOT-3317 - Sales Rep Basket Selection content managed web page areaThere is now the ability to create a Sales Rep Basket Selection content managed web page area, that can show a list of baskets that a sales rep user can create, delete, or switch between.
The area will only display if the user viewing it is set as a sales rep user, and that they are assigned to a facility permission role that has the "View Sales Representative Briefcase section" permission set to Allow.
The are contains the following formats:
TOT-3266 - Product Search Results Listing content managed webpage area to allow a combination product to be added to basket when it contains a default combinationOn a content managed web page showing areas that display combination products in Product Search Results Listing content managed web page area, or Category Listing areas we have added the ability to allow users to use and add the product to basket if the combination product has a default child product assigned to it.
Within the Administration Centre, from the Websites menu, in the Websites settings interface the setting labelled "Allow Default Combination Products To Add To Basket In Search" has been created.
This setting controls whether or not combination products can show the quantity box in content managed web page areas that use the Product Search Record format when the combination product has a default child product assigned.
If this does occur and the setting is set to Yes then when a user adds the combination product to basket they will be actually adding the default child product to basket.
Note that when this setting is set to Yes that it may add extra processing time to show product search results when there is combination products showing in the results.
Functionality Affected: Product Search Results Listing content managed web page area, Category Listing content managed web page area
Impact: Normal
TOT-3273 - Reference field set for credit card payments submitted through TNS payment gatewayWithin a TOTECS project, if it has been configured to use the TNS Payment Gateway to handle credit card payments for orders and invoices, the reference field for payments is now set the transaction number.
This ensures that any reports generated in TNS's web interface can show reference identifiers back to the payment in TOTECS for order payments, customer account invoice payments, or custom payments through the Payments administration centre interface.
Functionality Affected: Credit Card Order Payment process, Credit Card Invoice Payment process, Customer Credit Card Payment process
Impact: Normal
TOT-3300 - Show baskets in Basket Statistics Administration Centre interface assigned to users containing accounts assigned different from their basketWithin the Administration Centre, under the Statistics menu, in the Baskets Statistics interface it has now been modified to be able to show baskets of registered users, regardless of whether the user's current assigned account matches the account assigned to the basket.
This change ensures that baskets can show for sales rep users or users who are assigned to a different account.
Functionality Affected: Basket Statistics Administration Centre interface
Impact: Minor
TOT-3303 - Setting to control the sorting of addresses displayed in Order Detail and User DetailsOn a content managed website, there is now the ability to alphabetically sort the delivery address drop down menu based on the address name, in an Order Details Form web format area as well as the User Details form web format area.
This allows users to more easily find addresses when they have a long list of addresses to choose from.
Within the Administration Centre under the Stores menu, in the Order settings interface, a setting labelled "Address Drop Down Ordering" has been added that controls how addresses are ordered in the following places:
TOT-3197 - Contracts unable to load in Customer Account Contracts administration centre interface that contain new line characters in contract IDWithin the Administration Centre, under the Users menu, in the Customer Account Contracts interface, upon expanding the Mirrored contracts tree node, an error could display advising that the contracts could not be loaded. This error would occur in projects where a new line character existed in a contract's contract ID field.
The Customer Account Contracts Administration Centre interface has been modified to ensure that it can correctly handle loading contract data from the server that contains new line characters in the contract ID.
Functionality Affected: Customer Account Contracts Administration Centre interface
Impact: Normal
TOT-3274 - Customer account enquiry invoice payment missing information and failing to send to the ConnectorFrom a content managed web page containing a Customer Account Invoice Payment Form area, after a user successfully submitted a credit card payment and the payment was successfully processed by the payment gateway, the payment failed to be sent to the Connector software, and the details of the payment, as well as associated invoice data were missing when viewing the payment with in the Payments Administration Centre interface.
Within the invoice credit card payment process this issue was occurring due to the platform's database not correctly updating the details of a credit card payment after it was successfully processed by the payment gateway. Because of this the details of payment, and its invoices were not being saved to the database, which caused an attempt to never be allowed to occur for sending the payment data to the Connector application. This issue was introduced when the new high availability Galera database was implemented on the platform.
The invoice credit card payment process has been modified to ensure that all payment record data is fully written to the database before trying to update it and send the payment to the Connector software.
Functionality Affected: Invoice credit card payment submission process
Impact: Critical
TOT-3295 - Order status not updating to submitted after a credit card payment successfully processedOn a content managed web page containing a Order Checkout/Submission area, after a user has successfully paid for an order using the credit card payment method, the order's status could sometimes fail to change to unsent, and subsequently the order would not be attempted to be sent to the Connector.
This issue was caused by the order submission process trying to submit an order before its payment data was completely updated in the platform's new high availability database. This would infrequently occur based on the traffic load of the database servers at the time the order credit card was submitted.
The order submission process has now been modified to force it to wait for the database to fully update the payment status of an order before trying to submit the order to the Connector software.
Functionality Affected: Order submission process
Impact: Critical
TOT-3304 - Product not displaying in order confirmation Email notification or order detail after the product was deletedWithin the trade interface if an order was created that contained a product that was deleted from the project before the order was submitted, after the order was submitted the Email confirmation notification would not show the product however it was still contained in the order data that was sent to the Connector software. Additionally the deleted product did not show when viewing the order's details within the Administration Centre, or from the Trade interface's Order History page.
The Order Review page in the Trade interface, and the Order Checkout/Submission content managed web page areas have been modified to allow product data associated with the order to display even if no product exists any more in the project with the associated item ID. When an ordered product cannot be matched then its relevant data will be empty such as name and description.
Note: It is advisable to inactivate products instead of delete them from the project since otherwise certain product information will no longer show for users in their order history.
Functionality Affected: Order Checkout/Submission content managed web page area, Order Review Trade interface page, Order History Trade interface page, Order Detail Administration Centre interface, Order Confirmation Email notification
Impact: Normal
TOT-3312 - Guest users overwriting other guest user order data when an unconfirmed order exists with the same customer accountOn a content managed web page containing a Guest Order Checkout/Submission area if two different guest users were creating an order simultaneously it was possible that one guest user could overwrite the order details of the other user's orders.
This issue was caused due to the guest users being able to reset and overwrite an existing unconfirmed order if the order was assigned to the same guest login ID and customer account.
The order checkout process has been modified for both the Trade interface and the content managed order checkout/submission area to ensure that if guest users are proceeding with the order checkout, that the user can only reset an order which they have created previously when the order was created in their current session. If no order has been created during their session then a new order will be automatically created.
Functionality Affected: Order Checkout/Submission content managed web page area, Order Submission process
Impact: Critical
TOT-3316 - User Registration content managed web page area does not display success message if area security is set to public or privateOn a content managed web page area containing a User Registration area that has its security set to public or private, if the user had filled out the registration form and successfully submitted the form, the area was automatically reloading the form with cleared fields, instead of displaying the success message.
The User Registration area was modified so that it loads the registration success message when the area's security status is set to public or private.
Functionality Affected: User Registration content managed web page area
Impact: Normal
TOT-3318 - Users not notified of orders successfully submittedIn both the Trade interface and on content managed websites if a user had created and submitted an order, the user may have been notified that a critical error had occurred and were never receiving an Email notification of the order submission. Additionally the administrator user was not receiving the Email notification either however the orders were successfully being sent to the Connector as well as being marked as sent.
This issue would only occur if the platform's outgoing Email server was unavailable or too busy to send out anymore Emails.
The Email sending process has been modified to be able to capture more errors if an Email could not be sent out. This should ensure that the order submission process does not abort if an Email could not be sent out, and because of that the user will still be notified that an order successfully processed even if an Email notification could not be sent out. Additionally the order will still be sent to the Connector software.
Functionality Affected: Order Submission process
Impact: Major