Spring'25 Maintenance Release Changelog
This is a list of every change made in the Spring '25 Maintenance Release of Nimble AMS.
Nimble AMS Staff View
What's New?
Enhancement: The new Field Name, GL Setting Name, allows multiple GL Export formats when using FieldSetBatchExporter
This enhancement allows the users to choose multiple GL Export formats when using FieldSetBatchExporter due to the addition of the new field, GL Setting Name, on the Batch Export Configuration.
Your association will benefit if you allow:
Use GL Export
Defects Fixed
Orders with more than 100 items process without error
Subscription Orders with up to 100 items that use the same Coupon were not processed due to SOQL limits. (Known Issue ID: 151011)
Your association may be affected if you:
Use Coupons
Original System Design: Applying a Coupon for an Order with over 100 items or more, should be processed without error.
Solution: Now Coupon can be applied for an Order with over 100 items in Staff View.
Module(s) impacted: Coupons
Improved error message for Failed Queue Process records
In Staff View create a Cart and use the Payment URL to process the payment in Community Hub, however, the CaptureCreditCardPayment Queue Process record fails as it is stuck in the queue to capture Credit Card payment. This results in a failure and a generic error message “Failed to capture payment.” (Known Issue: 151183)
Your association may be affected if you:
Use Accounting
Original System Design: The failure message for the failed CaptureCreditCardPayment Queue record should have additional details.
Solution: Now and updated failure message will be stored in an error message field on the queueprocess record. If the failure reason from the API is blank, then a predefined message will be stored.
Module(s) impacted: Accounting
Duplicate orders for the 'Submit as an Order' button are now prevented.
When placing an order in Staff View, users may click the “Submit as an Order” button multiple times while the page is still loading. If the button is clicked multiple times while the Business Rule “Allow Save As Pro Forma Always” is active, it can lead to the creation of multiple duplicate orders. (Known Issue ID: 145575)
Your association may be affected if you:
Use Order Entry
Use the Business Rule “Allow Save As Pro Forma Always”
Original System Design: The system should have stopped or cleaned up the creation of duplicate Orders which were created by clicking the “Submit as an Order” button.
Solution: Now, a spinner mechanism prevents the “Submit as an Order” button from being clicked multiple times.
Module(s) impacted: Order Entry
Community Hub
What's New?
Defects Fixed
Now the membership term displays correctly in the Staff View and the Community Hub.
A Community Hub Membership term is displayed incorrectly but the Membership term displayed in Staff View is correct although this is for the same Membership. As an example, the Community Hub Membership term is 07/01/2025 - 06/30/2026 while the Staff View Membership term is 07/1/1-2025 - 12/31/2025. The price of the Membership is the same in Community Hub and Staff View. (Known Issue ID: 150546)
Your association may be affected if you:
Use Memberships
Use Proration
Original System Design: When a member does not have a Membership record but the Membership flow down grants Membership benefits from the parent affiliation, then the member should go through the Join/Renew process.
Solution: After this change, users will see the correct ‘Join Now’ button in the Community Hub when the Company Account membership flows down from the parent affiliation.
Module(s) impacted: Memberships, Proration