Winter '27 Seasonal Release

This is a list of every change made in the Summer '26 Seasonal Release of Nimble AMS.


Nimble AMS Staff View

Defects Fixed

Refund fails with “Above Max Amount” Error for Orders with Multiple Payments

When multiple payments exist for an order, attempting to process a refund results in the error message, "Above max amount." The system appears to select only the first payment and attempts to apply the entire refund against that payment, rather than evaluating all associated payments. As a result, the refund amount exceeds the selected payment amount, causing the error.

 

Your association may be affected if you: 

  • Use Stored Payment Method

  • Use Refunds

 

Original System Design: The refund amount should be distributed across the payment ling sequentially, respecting the remaining refundable balance for each payment line.

 

Solution: Updated logic to pull all the payment lines associated with the Order. Now staff will pick the original Stored Payment transaction from the dropdown (filtered by product), and the remaining refundable amount is tracked per transaction.

 

Module(s) impacted: Stored Payment Method, Refunds


Refund Processing Error for Apple & Google Pay Support Transactions

Staff users receive an error in the Order Processor when attempting to refund payments originally made via Apple & Google Pay Support. The issue occurs despite selecting Credit Card as the refund method.  

 

Your association may be affected if you: 

  • Use Apple & Google Pay Support

  • Use Refunds

 

Original System Design: Refunds should be successfully processed when the original Order is paid with Apply & Google Pay Support.

 

Solution: Now, the digital wallet payment lines are included in the refundable Credit Card dropdown when the original Order is paid with Apple & Google Pay Support.

 

Module(s) impacted: Apple & Google Pay Support, Refunds



Member Portal

Defects Fixed

Order Item Line Grouping Is Inconsistent Across Multiple Saves

Staff users experience inconsistent Order Item Line grouping behavior. This is seen when users start a new Order adding 2 donation products for a single account then save. Next add another donation product for the same account and hit save again.  The Order Lines are grouped under a single item only when multiple products are added during the same save action. Products added in subsequent edits are placed in separate items, even when they are for the same account and product type.  

 

Your association may be affected if you: 

  • Use Member Portal

 

Original System Design: Each Order Item Line should be grouped consistently under a single Order Item for product types regardless of being added on one save action or multiple save actions.  

 

Solution: Now, there is a single item for product types across multiple cart saves. Registration and Membership product types still create separate order items.

 

Module(s) impacted: Member Portal


Join Now Button Displays on Personal Snapshot page for Active Members

On the Member Portal Personal Snapshot page, users with active memberships continue to see the Join Now button despite already being active members. Their account also has the Member flag set to Yes. 

 

Your association may be affected if you: 

  • Use Member Portal

 

Original System Design: Users with an active membership should not see the Join Now button.

 

Solution: The Member Portal Personal Snapshot page will not display the Join Now button for active members.

 

Module(s) impacted: Member Portal


Express Payment Error When Processing Non-Self-Service Pro Forma Orders via Experience Cloud Checkout

Some Member Portal users received an error message indicating that non-Self-Service Products could not be processed through Express Payment. This issue occurs when a Pro Forma Order is created in Staff View for a non-Self-Service Product, and the user then opens the Experience Cloud Checkout URL in a new browser window to complete payment. Instead of the Order being processed successfully, the user receives an error message during checkout.

 

Your association may be affected if you: 

  • Use Member Portal

  • Use Express Payment

 

Original System Design: Pro forma Orders for a Self-Service disabled product in Staff View should process and the user should receive the Order Summary screen.

 

Solution: Users will be able to make payments for Staff View generated Pro forma Orders using Express Payment, even when the associated Product is not Self-Service enabled.

 

Module(s) impacted: Member Portal, Express Payment


Nimble Create Extension

Defects Fixed

Entity Organization-Wide Email Address Not Overriding Template Email for Order Confirmation/Invoice Emails

In Staff View, when sending an Order Confirmation or Invoice email, the email address specified in the template should be overridden by the Entity Organization-Wide Email Address. However, the template email address is being used instead of the Entity Organization-Wide Email Address.

 

Your association may be affected if you: 

  • Use Nimble Create Extensions - Email Functionality

 

Original System Design: Entity Organization-wide email address should override the template Email From field when Staff users send the Order Confirmation or Invoice.

 

Solution: Updated the logic to a global setting to be used when the entity-level and template-level OWEA are not configured.

 

Module(s) impacted: Nimble Create Extensions - Email Functionality



Seasonal Permission Changes

See the Winter '27 Seasonal Release Permission Changes in the Security section.