Overview

This document provides high-level information about new features and improvements implemented in this release of Volanté Account Management System (AMS). 

New Features

This section covers newly added features and improvements in the build release.

Guest User Sign Up

We have made improvements to AMS so it will serve as a central platform, making it a point of contact for external users at any site. In this release, we have added the ability for guest users to create an account on AMS. These additions support sign in for employees and guests. 

The Guest User Sign Up feature includes the following enhancements: 

• Guests/Employees can select Guest/Employee Sign Up to register. Guest and Employee fields are configurable.
• Enables logins using either account ID or email.
• Introduces a “Forgot Password” flow for easy account recovery.
• Supports Recaptcha validation for guest sign up and two-factor authentication for guest and employee email before proceeding with account creation on the BO.

Documentation:

My Volanté (AMS) - Enabling Guest Sign In

My Volanté (AMS) - User Guide (PDF) - Volanté Systems Documentation - Confluence

Webhook Changes for CentricOS

The following outlines the Webhook changes for CentricOS:

1. When a change happens on CentricOS, Volante receives a Webhook request on the AMS endpoint. 
2. AMS adapter then routes CentricOS Webhook requests to the correct BO. 
3. Volante stores these requests in a queue and processes them sequentially.
4. Volante receives a process ID for each sync request. 
5. When the Webhook request is sent to the Volante endpoint, the sync status is posted, including successful and failed statuses.

For more information, see CentricOS documentation. 

Documentation: CentricOS Integration - Internal Space - Confluence

We improved the card validation process by checking card details immediately upon entry and providing detailed error messages when the card information is incomplete/incorrect. 

• When a user adds a new payment method (My Profile → Payment) with incorrect or incomplete information, they will receive the appropriate error message, i.e., 'Invalid card number', 'Expiration date cannot be in the past', 'Please enter the CVV code', 'Unsupported card type', etc.).
• When the user selects a new payment method under My Profile → Payment, a dialog displays with the following message "Adding a new payment method would replace the existing saved payment method under user profile" if an existing payment method has been saved. 
• Payment details are securely stored in the user's AMS profile under Saved Payment Methods.

Purchase Points - Improvement

The following improvements have been made to the Purchase Points feature:

• AMS displays success/failure message for several seconds after the user has loaded points to their account.

• The success/failure banner font size has increased to improve visibility.

• The Points balance page immediately displays the updated balance after the user loads points.

• Verified that the customized label values for the Balance and Points text on the UI are functioning as required.

Documentation:

My Volanté (AMS) - User Guide (PDF)

My Volanté (AMS) - Points Account Configuration | Step 5. Setting the customized points text label

Bug Fixes

This section lists bugs that have been fixed in this release.

→ Internal Volanté team only.

(VOL-18781 - [AMS] Autoload failed on Reg-Mayo and Customer is auto refunded instead.)

• The system now correctly sends low balance notifications and triggers the autoload, followed by a confirmation email after successful autoload.

(VOL-18769 - [AMS] Notification Settings are Transient)

• Settings are now saved as expected and remain consistent across tabs without resetting, even if the user logs out and logs back in.

(VOL-18768 - [AMS] Unable to add payment method as 'Iframe' would not load)

• Updated request parameters to prevent conflicts, allowing the IFrame to load and enable users to add payment methods.

(VOL-18767 - [AMS] Employee email used for sign up does not show in Profile section of AMS)

• Profile now displays the employee's email and other details entered during signup as expected.

(VOL-18766 - [AMS Waiver] AMS Waiver opt in/opt out not recorded properly on AMS)

• Added missing code to record opt-in/opt-out selections correctly, ensuring that selections are retained for subsequent logins.

(VOL-18763 - [AMS][Employee Signup] Employee signed up on AMS without an existing CDB customer.)

• Implemented validation to prevent signup if an employee is not pre-registered in the CDB.

(VOL-18773 - Clicking on expired verification email shows incorrect error)

• Updated the error message to correctly indicate that the link has expired and prompt users to request a new one.

(VOL-18706 - [CentricOS][Webhook][AMS] connectorId not required for centricOSConfigs)

• Confirmed and enforced requirement for connectorId, boUser, and boUserPassword in CentricOS Webhook configurations.

(VOL-18690 - [AMS] Webhook response code for CentricOS)

• Modified response to correctly return a 401 Unauthorized status for invalid credentials.

(VOL-18725 - [AMS] Sign-up missing userType cause exception)

• Added a default value for missing userType fields to ensure compatibility with existing signup flows.

(VOL-18741- AMS Exception when defaultGuestGroupId is missing)

• Set a default value of "-1" when defaultGuestGroupId is not configured, preventing exceptions.