Winter'25 Maintenance Release Changelog
This is a list of every change made in the Winter '25 Maintenance Release of Nimble AMS.
Nimble AMS Staff View
What's New?
Enhancement: Introduced a new field, Opportunity Amount on the Opportunity Detail Record Page
We have enhanced the Sales Cloud Connector feature by introducing an "Opportunity Amount" field to the Opportunity sObject. The Opportunity Amount field on the Opportunity automatically calculates and displays the total cost of Nimble AMS products linked to each Opportunity providing a quick and accurate view of the aggregate opportunity cost. (Learn More)
Your association will benefit if you allow:
Use the Sales Cloud Connector
Enhancement: Nicknames for Stored Payment Cards
Association members can now assign nicknames to their stored credit or debit cards, making it easier to quickly identify and select the right card during checkout. Whether they’re using the checkout page or managing cards on the My Payment Methods page in the new Member Portal, members can label cards as “Business Card,” “Personal Card,” etc., streamlining the shopping experience—especially when multiple cards are saved. If no nickname is set, the card details will appear as usual in the dropdown. (Learn More)
Your association will benefit if you:
Use Stored Payment Methods
Use My Payment Methods in Experience Cloud
Use the Experience Cloud Checkout page.
Enhancement: Order API with Order Item Line Cancellation Capability
The Order API has been enhanced to allow the cancellation of individual Order Item Lines within an order, providing associations with more granular control over order management. Previously, only entire Order Items could be canceled, which meant any order item line adjustments required canceling the whole Order Item. Now, association staff can directly cancel specific Order Item Lines without impacting other items in the same order. This added flexibility reduces operational complexity and enhances the precision of order management workflows.
Your association will benefit if you:
Use Order API
Have need to Cancel specific Order Item Line
Defects Fixed
Enhanced Deferred Schedule Recognition for Schedules (Imported and Non-Imported)
Deferred Revenue Methods for imported schedules break financial calculations, when the schedule has started to recognize monies, and a new Order is added to the assigned Deferred Revenue Method. The new Order is added to the imported schedule and does not properly recognize the monies as it can be removed. Unhealthy Deferred Schedules result from the imported schedule that has new transactions added before the recognition of the schedule which generates incorrect transactions. (Known Issue ID: 147831)
Your association may be affected if you:
Use Accounting
Use Deferred Schedules
Use the Deferred Revenue Method
Original System Design: New Order transactions should not break financial calculations for Deferred Schedules.
Solution: Added a check to see if the externalTransactionDate field is null, before setting the initialTransactionDate field to prevent overlapping with imported schedules.
Module(s) impacted: Accounting, Deferred Schedules, Deferred Revenue Method
Event counts now update
When staff users delete an Event, it can cause an error with the EventRegisterationCount Updater batch Apex job. The error causes the EventRegistrationCountUpdater job to not run for other records, which then sends error emails until the issue is resolved. This is resolved by finding the related Queue Process record to update the Purpose, so it will not run, or it will delete the record. (Known Issue ID: 148147)
Your association may be affected if you:
Use Events
Original System Design: The EventRegistrationCountUpdater job should delete the Event Queue Process record without impacting the other records.
Solution: After this change, deleted Events Queue Process records will be cleared without error from the EventRegistrationCountUpdater job.
Module(s) impacted: Events
Orders with Chapters can now be adjusted
Staff members are unable to edit Orders when a customer requests a transfer from one state Chapter to another. In this case, staff members need to edit the existing paid membership Order for 2024. However, the staff member is unable to add a new line item to the adjustment Cart via the order processor. (Known Issue ID: 148260)
Your association may be affected if you:
Use Chapters
Use Order Entry
Use Customer Membership Order Processor
Original System Design: Staff users should have the capability to modify Orders with Chapters by adjusting the individual Cart Item lines.
Solution: Staff users can now update Orders with Chapters by adjusting Cart Item lines
Module(s) impacted: Chapters, Order Entry, Custom Membership Order Processor
BluePay Payment Settlement Date field now populates
BluePay Payment Settlement Date field was not populating for payments settled within the reconciliation period. These Payment records were not marked as failed and did not have an error message. (Known Issue ID: 148398)
Your association may be affected if you:
Use Order Entry
Use BluePay
Use Stored Payment Method (SPM)
Original System Design: The Payment Settlement Date field should be populated and if there is a failure then the Payment record should be marked as failed.
Solution: Updated logic to check if a Stored Payment Method is the same for multiple Payment records to avoid duplicate values in the reconciled Payment records.
Module(s) impacted: Order Entry, BluePay
Guest Users can apply Coupon discount links successfully for Express Payment Carts
Guest Users attempted to apply a Coupon discount link to an Express Payment Cart but received a login screen. After logging in, the user was redirected to the Community Hub login with a startURL parameter of the Community Hub CheckoutDynamicPage + Express Payment Cart parameters, which then resulted in an error stating the current page couldn’t be found due to the incorrect redirect. (Known Issue ID: 148514)
Your association may be affected if you:
Use Coupons
Original System Design: Guest Users should successfully apply Coupon links to an Express Payment Cart.
Solution: Updated the selector method of the SOQL query to prevent record access issues.
Module(s) impacted: Coupons
Accrual Dues now support Tiered pricing
Staff users observed that Accrual Dues did not support Tiered pricing when Accrual Dues was run by selecting membership type and end date. (Known Issue ID: 132034)
Your association may be affected if you:
Use Accrual Dues
Use Tiered pricing
Original System Design: Accrual Dues should have supported Tiered pricing.
Solution: Now Accrual Dues respects Tiered pricing after running billing.
Module(s) impacted: Accrual Dues, Tiered pricing
Subscription coverage for the same Order Item with different start dates is now gap-free
In the Staff View Order processor, several Subscriptions can be selected and applied to the same Order item. However, if the start dates are different values, then the processing job for the Schedules will create a gap in the Subscription coverage causing customers to be incorrectly excluded. (Known Issue ID: 138124)
Your association may be affected if you:
Use Subscriptions
Original System Design: Once a recurring Subscription is set up there should be no gap in the Subscription coverage.
Solution: Now Subscription Schedules will process multiple Subscriptions under the same Order Item with appropriate start and end dates for future recurring Subscriptions.
Module(s) impacted: Subscriptions
EventRegistrationCountUpdater Job now runs when Event records are present.
Customers received an error message email when the EventRegistrationCountUpdater Job runs but there are no queue process records. The null error message states the batch apex job processed 0 batches with 0 failed batches. (Known Issue ID: 148640)
Your association may be affected if you:
Use Events
Original System Design: The EventRegistrationCountUpdater Job should run when there are Event records to process.
Solution: Updated logic to check for Event records before running the EventRegistrationCountUpdater Job.
Module(s) impacted: Events
The Stored Payment Method ‘Updated On’ field now populates when the BluePay Account Updater job runs.
The BluePay Account Updater job does not refresh the Nimble AMS Stored Payment Method (SPM) ‘Updated On’ field, which makes it difficult for clients to see when the SPM has been automatically updated. (Known Issue ID: 147471)
Your association may be affected if you:
Use BluePay
Use Stored Payment Method (SPM)
Original System Design: The Store Payment Method ‘Updated On’ field should have been populated by the BluePay Account Updater job.
Solution: Now, the ‘Updated On'’ field will populate when the BluePay Account Updater runs.
Module(s) impacted: BluePay, Stored Payment Method
Community Hub
What's New?
Defects Fixed
Inactive products no longer allow Order submission
In Community Hub, if a Staff user marks a Product as Inactive but does not realize there are outstanding Orders then the customer/payor will run into a failure when trying to pay for the related Order. If the client is using Hosted Payments, then the Payment will be recorded but the Order will remain unpaid in Nimble AMS. (Known Issue ID: 146719)
Your association may be affected if you:
Use Community Hub
Use Hosted Payments
Use Express Payments
Original System Design: Inactive product Orders should not allow the Order to be submitted.
Solution: Now, when an Express Payment Order is for an Inactive product, the Express Payment Card is prevented from rendering.
Module(s) impacted: Community Hub, Hosted Payments, Express Payments
Community Hub Mobile View now displays Personal Snapshot in Navigation
Users utilizing the Community Hub in mobile view have noticed that the display differs slightly from the desktop view. Specifically, the Personal Snapshot, which appears as the top left navigation link in the desktop version, was not visible in the mobile view. (Known Issue ID: 147872)
Your association may be affected if you:
Use Community Hub in Mobile View
Original System Design: The Community Hub Mobile View should display the Personal Snapshot as the first navigation item on the menu.
Solution: Updated logic makes the Personal Snapshot, the first navigation item to be visible.
Module(s) impacted: Community Hub in Mobile View
Community Hub Mobile View now displays the Checkout Button
In the Mobile View of Community Hub, users encountered an issue where the Checkout Button extended off-screen. However, when the Checkout Button was clicked, users were successfully redirected to the checkout page. (Known Issue ID: 147610)
Your association may be affected if you:
Use the Community Hub Dynamic Checkout page
Original System Design: The margin for the Checkout Button styling should adjust for the Mobile View.
Solution: Adjusted the margin from the Checkout Button styling to make the Checkout Button visible in Mobile View.
Module(s) impacted: Community Hub Dynamic Checkout page
Community Hub Background color now updates on Mobile device
In Community Hub the ‘Off Canvas Background Color’ setting in Theme Settings did not update the Background color when viewing Community Hub on a Mobile device. The Mobile device displays an aqua/turquoise color regardless of the chosen color for the ‘Off Canvas Background Color’ setting. (Known Issue ID: 133084)
Your association may be affected if you:
Use Community Hub Setup
Original System Design: The Theme Settings for the ‘Off Canvas Background Color’ setting should update the font color when viewing Community Hub on a Mobile device.
Solution: Enabled the ‘Off Canvas Background Color’ and list group items to dynamically update based on the ‘Off Canvas Background Color Setting’ in Community Hub Theme Settings.
Module(s) impacted: Community Hub Setup
Event Registration with Registration Types now reflects special pricing
While using Registration Types for Event Registration, the special prices for registration products were not honored because the price class was set on the Cart item, causing the Community Hub user to receive an incorrect price. (Known Issue ID: 148849)
Your association may be affected if you:
Use Events
Use Registration Types
Original System Design: When the Registration Type is set, the user should be required to select a Registration type via the ChooseRegistrationType page which provides the special pricing.
Solution: Now, the correct price class will be applied to the Registration record if the Registration Type is selected during the Community Hub Registration process.
Module(s) impacted: Registration Types, Events