Summer'25 Changelog
This is a list of every change made in the Summer '25 Seasonal Release of Nimble AMS.
Nimble AMS Staff View
What's New?
Enhancement: Re-Instate functionality improvements
The Re-Instate functionality now reflects accurate renewal dates. the Membership type and Re-Instatement timing are factored into the logic to ensure accurate renewal dates. This ensures continuity of membership history and eligibility for benefits, while enforcing the appropriate inactive period without benefits.
Your association will benefit if you allow:
Use Re-Instate functionality
Enhancement: Credit card payment improvements
The CreditCardPaymentCapturer job now processes more than 50,000 records at a time, allowing more credit card payments to complete. This includes changes to the error email. The email now only contains counts for records processed. The email categories for the counts are successes, failures, which remain for automated re-try or manual resolution, and then failures which can never succeed. The Full raw response errors are now logged to the Queue Process record as “Full Error” in the new long text field.
Your association will benefit if you allow:
Use Credit card payments
Enhancement: The new OriginalJoinOn_c field allows tracking of the Account’s Original Join Date
This new custom field, OriginalJoin_On_c, added to the Account object, now allows the tracking of the account’s Original Join Date. This field is automatically populated for the first time based on the ‘Join On’ field if it is empty. Once populated the field will no longer be updated. This allows staff to report accurately on an account’s original join on date, without it being overwritten by a new membership record.
Note: This field can be manually updated, allowing legacy join data to be recorded as well.
Your association will benefit if you allow:
Use Memberships
Report on Join Dates
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
Scheduled Payments Number of Retries field now incremented
When Scheduled Payments have the Number of Retries field set to 0, the schedule attempts to retry at least once in addition to the initial run when there is a failure. If the initial run fails, then the Schedule will repeat the next day, even when the Number of Retries field is set to 0.
Your association may be affected if you:
Use Scheduled Payments
Original System Design: All Scheduled Payments should have the Number of Retries field incremented to avoid unnecessary retries.
Solution: Now, the Number of Retries field is incremented when a schedule fails.
Module(s) impacted: Scheduled Payments
Proration Rules respect Start Control Date
Proration Rules do not respect the Start Control Date. Proration of the membership term with a Start Control Date of the 15th of a month, should have shortened the membership term with a decrease cost. However, the membership term increased as well as the cost of the membership.
Your association may be affected if you:
Use Proration Rules
Original System Design: The Proration Rule should have respected the Start Control Date for membership term and membership cost.
Solution: Now, membership term and price calculate based on the Proration Rule and Start Control Date.
Module(s) impacted: Proration Rules
Invoice Dates are now stamped
When a user creates an Order by applying payment to the Cart from the Express Payment page, the Invoice Date field on the Order record retained the Cart creation date rather than the date the Order was created.
Your association may be affected if you:
Use Orders
Use Express Payment page
Original System Design: The Invoice Date field should remain the date the Order is created regardless of when a full or partial payment is made.
Solution: Now, the Invoice Date field is stamped by default when the Order is created.
Module(s) impacted: Orders
One Payment wizard now closes without error message
End users experienced a One Payment error message when cancelling or completing a payment from the Order record. In the One Payment wizard a component error message displayed after clicking the cancel button or the Complete Payment button after the payment completed.
Your association may be affected if you:
Use One Payment Wizard
Use Orders
Use Accounts
Original System Design: The One Payment wizard should refresh data in the record detail page and close once the payment is complete.
Solution: Now, the One Payment wizard closes without an error message.
Module(s) impacted: One Payment Wizard, Orders, Accounts
Nimble AMS Merge Task record captures Name field
While using the Nimble AMS Merge functionality to merge two individual accounts, a task record was created without a Name field, although the Name field is populated on the Master Record.
Your association may be affected if you:
Use Nimble AMS Merge
Use Accounts
Original System Design: The Task record should have retained and populated the Name field as the record captures names and IDs of the non-master records that are merged.
Solution: Now, the Name field is populated on the Task record when merging accounts.
Module(s) impacted: Nimble AMS Merge, Accounts
Error message resolved for Recurring Schedules
A recurring schedule fails when the original order item is edited to remove the OIL. When the OIL is cancelled, the quantity is set to 0. While the recurring schedule is still processed, it fails with the error message: “The quantity must be greater than zero”.
Your association may be affected if you:
Use Recurring Schedules
Original System Design: Adjustments to an order item for a recurring schedule should not cause the process to fail.
Solution: Now, cancelled lines in a recurring order will not cause an error message.
Module(s) impacted: Recurring Schedule
Billing History now checks the Term Override on the MTPL
When a user joins during a month that results in a membership with a term that does not match the Term Override on the renew Membership Type Product Link (MTPL), Billing History does not find a matching MTPL and creates an empty cart and cart item.
Your association may be affected if you:
Use Billing History
Use Membership Term Override
Original System Design: Billing History used the start and end dates of the current membership record when determining the MTPL to use for renewal.
Solution: Now, Billing History will use the same MTPL as the current membership regardless of membership term length (assuming it isn’t configured for transitions).
Module(s) impacted: Billing History, Membership Term Override
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
Seasonal Permission Changes
See the Summer '25 Seasonal Release Permission Changes in the Security section.