Winter '24 Changelog
This is a list of every change made in the Winter '24 Release of Nimble AMS.
Nimble AMS Staff View
What's new?
Deferred Revenue Improvement:
Improved Handling of Deferred Revenue for Mid-Term Membership Cancellations.
When a membership using Deferred Revenue is canceled mid-term, it is automatically transferred to a new deferred schedule with a term that aligns with the updated membership term. This improvement paves the way for future performance enhancements in processing deferred schedules. (Known Issue ID-132625)
Your association may be affected if you:
- Use Deferred Revenue Method
- Use Cancel Membership Mid-Term
- Use Deferred Revenue Method
Original System Design: Deferred Revenue needed to account for each Order Item Line separately, as they could have varying terms following a mid-term membership cancellation.
Solution: To streamline and simplify the management of Deferred Revenue, we've introduced a solution. Order Item Lines are now seamlessly transitioned to a different deferred schedule, ensuring that all Order Item Lines within a given schedule share the same term. This enhancement optimizes the processing of deferred schedules and ensures more efficient management of your revenue data.
Module(s) impacted: Deferred Revenue Method, Cancel Membership Mid-Term
Query efficiency improved to eliminate SOQL limit errors during Cart submission with Multi-Currency enabled.
Multiple queries were executed to capture CurrencyIsoCode for multiple records during the Cart submission process when Multi-Currency is enabled. This created SOQL limit errors. (Known Issue ID-134340)
Your association may be affected if you:
- Use Multi-Currency
Original System Design: The multiple queries to capture the CurrencyIsoCode for records should not result in SOQL limitations.
Solution: Modified the precache CurrencyIsoCode for multiple objects during the Cart submission process when Multi-Currency is enabled.
Module(s) impacted: Multi-Currency
Defects Fixed
Deferred Revenue Improvement:
Enhanced Display of Deferred Forecast Details for Accurate Revenue Projections.
The Deferred Forecast Detail failed to load or users received error messages when the OrderItemLine records were 60K or 100K. (Known Issue ID-134761)
Your association may be affected if you:
- Use Deferred Revenue Method
- Use Deferred Revenue Method
Original System Design: The Deferred Forecast Details were intended to load accurately even when handling a large volume of data, ensuring precise revenue projections.
Solution: The Deferred Forecast Details will now load correctly, even when dealing with substantial data volumes. This enhancement empowers you to gain a deeper understanding of your projected income, regardless of the data scale.
Module(s) impacted: Deferred Revenue Method
Deferred Revenue Improvement:
Improved access to Deferred Revenue Transactions for precise income projections.
Deferred Schedule "Deferred Revenue Transactions" section fails to load. (Known Issue ID-123643)
Your association may be affected if you:
- Use Deferred Revenue Method
- Use Deferred Revenue Method
Original System Design: In our initial system design, the Deferred Revenue Transactions section was intended to provide a comprehensive list of transactions for more accurate income projections.
Solution: To address this issue and enhance your experience, we've introduced a convenient "View Transactions Report" button within the Deferred Schedule. Clicking this button will instantly take you to a detailed list of Deferred Transactions reports, allowing you to access the information you need more efficiently. In case you cannot find the "View Transaction Report" button on the Deferred Schedule record, edit the page and add 'displayDeferredRevenueTransactions' LWC component on the page.
Please note that while this report offers improved access, it also accommodates a maximum of 100 thousand records.
Module(s) impacted: Deferred Revenue Method
Required Event questions no longer cause cancellation error.
When a staff user edits the answer options or adds new required questions to an existing Evet, the cancellation of a pre-existing Registration Order to that Event receives an error. Users/staff users received an error because the answer options o required questions stopped the cancellation process. (Known Issue ID-123403)
Your association may be affected if you:
- Use Event Registration
- Use Event Registration
Original System Design: The required questions or answer options should not cause an error in the cancellation process.
Solution: Now an added check avoids the Event required questions/answer options while canceling the Registration.
Module(s) impacted: Events
'Copy From Mailing' checkboxes now copy State field.
For Individual accounts, using the 'Copy From Mailing' checkboxes, clears out the State field if the state is the same as the mailing address but another part of the address is different. The State field for these other addresses is also cleared out if trying to use the 'Copy from Mailing' checkbox and the address is already exactly the same as the mailing address. (Known Issue ID- 135095)
Your association may be affected if you:
- Use 'Copy From Mailing'
- Use 'Copy From Mailing'
Original System Design: The 'Copy From Mailing' checkboxes should have copied the State field regardless if the State or other parts of the address are the same.
Solution: Added logic to copy mailing address to addresses (billing, shipping, other) on the account when 'Copy From Mailing' checkbox is checked.
Module(s) impacted: 'Copy From Mailing'
Batch Cart Count null value now populates to 0.
When an existing Cart is updated to use a new Batch, an error was received if the Batch did not have the Cart Count field populated. (Known Issue ID- 134527)
Your association may be affected if you:
- Use Batches
- Use Batches
Original System Design: The Batches' Cart Count field as a null value should have assumed a 0 to continue the process as expected.
Solution: Updated the Batch's Cart Count field to 0 when a null value is present.
Module(s) impacted: Batches
Payment methods for One Payment show only Active Accounts.
When using One Payment via Staff View, you can see the Payment methods for Bank Accounts that are not Active. This is inconsistent with the normal Staff Payment process as Payment Methods associated with Bank Accounts that are inactive are not displayed. (Known Issue ID-135102)
Your association may be affected if you:
- Use One Payment
- Use One Payment
Original System Design: The Payment Methods associated with inactive Bank Accounts should not be displayed in One Payment.
Solution: Added a check for an active Bank Account when querying for entity payment methods.
Module(s) impacted: One Payment
Avalara Transactions voided if Cart submission fails.
When converting a Cart to an Order with outdated Taxes, the Avalara portal generated the Transaction but failed to void it, resulting in duplicate Transactions in Avalara. (Known Issue ID-134988)
Your association may be affected if you:
- Use Avalara (for External Taxation)
Original System Design: During Cart submission failures, the Avalara portal generated duplicate Transactions that should have been voided.
Solution: If Cart submission fails for a fresh Order (not an adjustment), the Transaction created on the Avalara portal will now be voided.
Module(s) impacted: Avalara (External Taxation)
If the 'Allow Overpayment' business rule is inactive, the schedule line should fail and display an error message when overpayments occur.
Scheduled Payments from Saved Payment Method are set up, then a partial payment with a balance less than the schedule line amount is made. The canceled schedule line is updated to pending, while the allow Overpayment business rule is inactive and the payment is made from the Pay Now button. The schedule line is processed but a payment line is not generated. (Known Issue ID-134939)
Your association may be affected if you:
- Use Saved Payment Method
- Use Scheduled Payments
Original System Design: When the Allow Overpayment business rule is inactive, and an overpayment is made the schedule line should fail and an error message is displayed.
Solution: An error message is shown when the schedule line processes an overpayment.
Module(s) impacted: Saved Payment Method, Scheduled Payments
Sales Tax calculation updated from Taxable and Non-taxable Coupons.
After applying a Coupon to an Order, the Tax was calculated on the Sub Total field value even after the Coupon was applied. (Known Issue ID-130006)
Your association may be affected if you:
- Use Value Added Tax (VAT)
- Community hub
- Orders
- Coupons
Original System Design:
- When the Coupon applied is Non-taxable, the Tax calculation should happen on the product price.
- When the Coupon applied is Taxable, the Tax calculation should happen to the discounted price.
Solution: Updated logic to calculate Sales Tax for Taxable and Non-taxable Coupons.
Module(s) impacted: Value Added Tax (VAT), Community Hub, Coupons, Orders
The Installment Payments now generate accurate Transactions.
Schedules with multiple schedule lines from the schedule job process, will run all of the payments and created a set of duplicate Transactions for each processed scheduled line resulting with incorrect Transactions. (Known Issue ID-133689)
Your association may be affected if you:
- Use Installment Payments
Original System Design: Processing multiple schedule lines within a single schedule through the scheduling job, should result in accurate Transactions and prevent any duplication.
Solution: Updated logic to avoid duplicate Transactions when a single Order has multiple payment lines.
Module(s) impacted: Installment Payments
Added an error message where shipping and Tax calculations are needed for Taxable products, but Tax has not been calculated.
When paying for Shippable and Taxable products with Flat Rate Shipping method, the user is required to populate the Shipping Form but not the 'Calculate shipping and tax' button before proceeding to payment. (Known Issue ID-123515)
Your association may be affected if you:
- Use Avalara
Original System Design: The Order submission should fail with an error message to calculate Tax.
Solution: Added error message: 'Please click the 'Calculate shipping and tax' button to calculate the Tax before proceeding to checkout.'
Module(s) impacted: Avalara
Authorize.Net payment capture now validated.
Payments processed with Authorize.Net mistakenly captured multiple times, which resulted in the Payment Processor Transaction Id to be set to 0. (Known Issue ID-133859)
Your association may be affected if you:
- Use Authorize.Net
Original System Design: Once the Payment is captured the Payment Processor Transaction Id should not change.
Solution: Added logic to validate the gateway response and avoid updating the payment record multiple times.
Module(s) impacted: Authorize.Net
Refunds to credit cards through the Stored Payment Method are now error-free.
Some users attempted to refund a Stored Payment Method by selecting credit card as the payment method and received error MethodName=validateSaveCartPaymentWithCartPaymentLines. This was caused by the Payment method selection not saving before the operation started. (Known Issue ID-127515)
Your association may be affected if you:
- Use Stored Payment Methods
Original System Design: To ensure a successful refund, it is essential to save the Payment method selection prior to initiating the refund operation.
Solution: Users will now have the option to select the Payment method for the refund from a drop-down menu. Sufficient time will be provided for the selection to save before initiating the refund operation, ensuring a successful refund.
Module(s) impacted: Order, Payments, Stored Payment Methods.
Batch Processing for schedule lines is more efficient.
Cancellation of an order while schedule processing caused unrelated records in the batch to fail. The unrelated records were then processed the next day, resulting in those customers being double charged. (Known Issue ID-129206)
Your association may be affected if you:
- Use Cancel Orders
- Use Schedule Payment
Original System Design: When an order is canceled, it should only cause the schedule line associated with that order to fail during the schedule processing job.
Solution: Increased the efficiency of the Order Processor to fail specific scheduled lines while running ScheduleLinesProcessorJob.
Module(s) impacted: Order. Schedule Payments
Generated new recurring orders now uses the Order's Entity to process payments.
While processing the schedule for a recurring donation, an error occurred. This error encountered because the organization had configured the Entity Crossovers module with two separate BluePay accounts. (Known Issue ID-133212)
Your association may be affected if you:
- Use BluePay
- Use Donations
- Use Entity Crossovers
- Use Recurring Payment
Original System Design: New recurring order is stamped with the Order Item Entity.
Solution: Updated the logic to utilize the OrderRequest for the Order's Entity to generate new recurring order.
Module(s) impacted: BluePay, Entity Crossovers, Recurring Payment
Error message on Community Hub Express Payment page updated.
Guest users and logged in users received a blank error message if the cart submission failed due to an expired coupon on the Community Hub Express Payment page. (Known Issue ID-132987)
Your association may be affected if you:
- Use Coupons
- Use Express Payment
Original System Design: If cart submission fails a warning message should populate in the pop-up message box.
Solution: Update the logic to render the warning message if cart submission fails.
Module(s) impacted: Coupons
SOQL calls lowered for Coupon use.
When users added a coupon to the cart before applying the payment for Membership and Registration products a SOQL limitation error was received. (Known Issue ID-134116)
Your association may be affected if you:
- Use Coupons
Original System Design: Coupon use for multiple products should have processed at checkout.
Solution: Reduced the SOQL calls by updating caching and precache for multiple queries and objects.
Module(s) impacted: Coupons
Improved API error limit message.
When MapQuest's free account reaches the maximum number of transactions per month, an 'Attempt to De-reference Null' error message is received. (Known Issue ID-132769)
Your association may be affected if you:
- Use Account Address
Original System Design: The 'Attempt to De-reference Null' error message should have communicated the job failed due to the API limit being reached.
Solution: Improved the error message to throw a 'Limit Exceeded' message when the API limit is reached.
Module(s) impacted: Account Address
Community Hub
What's new?
See our latest enhancements on the Major Features page.
Defects Fixed
Updated the NC_OrderDetails field set.
Staff users received an error when adding fields to the NC_OrderDetails field set on the Express Payments page. (Known Issue ID-122008)
Your association may be affected if you:
- Use Express Payment
Original System Design: Adding fields to the field set, NC_ORderDetails, should not cause an error.
Solution: Added fields for querying Orders in the OrderSelector.
Module(s) impacted: Express Payment
Guest Users are now redirected to the Express Payment page.
The payment URL on the Order page redirected Guest Users to the Community Hub login page, rather than the Express Payment page. (Known Issue ID-134927)
Your association may be affected if you:
- Use Express Payment
Original System Design: Guest Users with Express Payment setup should be redirected to the Express Payment page when submitting an Order.
Solution: Added rendering logic to enable Guest Users to access the Express Payment page.
Module(s) impacted: Express Payment
Hosted Payment form remains open until payment is complete.
The Hosted Payment modal closed if the background area was clicked before the payment processing was complete. (Known Issue ID-122278)
Your association may be affected if you:
- Use Hosted Payment
Original System Design: The Hosted Payment form modal should remain open while the payment is being processed.
Solution: Added logic to prevent the closing of the Hosted Payment form until the payment has been successfully processed.
Module(s) impacted: Hosted Payment
Now Guest Users can access the Lightning store when MultiCurrency is enabled.
When MultiCurrency is enabled the Guest Users, who are not logged in, receive an error message,"sObject row was retrieved via SOQL without querying the requested field: NU_Entity_c.CurrencyIsoCode", while trying to access the Lightning store. (Known Issue ID-134340)
Your association may be affected if you:
- Use MultiCurrency
Original System Design: When MultiCurrency is enabled, Guest Users who are not logged in, should be able to view the Lightning store without error.
Solution: Updated query to allow Guest Users, who are not logged in, to access the Lightning store when MultiCurrency is enabled.
Module(s) impacted: MultiCurrency
The platform event is received accurately when the 'Community User Created' business event is active.
Business Events for the 'Community User Created' is active, however, when the Community User was created the platform event was not triggered. (Known Issue ID-117288)
Your association may be affected if you:
- Use Business Events
Original System Design: The Business Event should have triggered a platform event once the Business Event is checked as active.
Solution: Updated Business Event Framework to enable for User Triggers.
Module(s) impacted: Business Events
Setting up a scheduled payment is required for the 'Pay Later - Schedule Payment' option.
In a Community Hub cart, when a user selected the 'Pay Later - Schedule Payment' option, the user was able to bypass the 'Configure Payment Schedule' and click the 'Submit,' resulting in the Order submitting without payment and no schedule configured. (Known Issue ID-134348)
Your association may be affected if you:
- Use Scheduled Payments
Original System Design: When 'Pay Later - Schedule Payment' is selected during the checkout, the only button that should render is 'Configure Schedule Payment.'
Solution: Removed the Submit button when the 'Pay Later - Schedule Payment' option is selected.
Module(s) impacted: Scheduled Payments
Additions to the company, now redirect to the Company Roster page.
After adding an individual to the company, through the Manage Roster page, the user was redirected to the My Affiliations page. Once the individual was added, the Manage Roster page should have redirected to the Company Roster page. (Known Issue ID-130839)
Your association may be affected if you:
- Use Community Hub Card
- Use Community Hub Setup
Original System Design: The Manage Roster page should have redirected to the Company Roster page when adding an individual to the company.
Solution: Updated the cookie service classes to render the Company Roster page.
Module(s) impacted: Community Hub
Event Registration button in Community Hub when Waitlist is enabled.
A small portion of Community Hub users, who, registered for an Event with the Registration button were presented with a message of "Add or manage registration" rather than "Register or waitlist registration." To produce this behavior, the Event would need to be Self Serviced Enabled, Is Editable, Co-Worker Registration Enabled and the Community Hub user account must have an active Primary affiliation and one other child account to the Primary affiliation needs to be registered for the Event. (Known Issue ID-132619)
Your association may be affected if you:
- Use Event Registration
- Use Waitlisting
Original System Design: The Waitlist enabled should be for Events that can be registered for.
Solution: Added a check to verify that Waitlist is enabled on the event, when verifying the event can be registered for.
Module(s) impacted: Event Registration
Improved Community Hub Event registration process.
A guest registering for an Event in Community Hub received a badge class of 'Speaker' rather than 'Guest'. (Known Issue ID-132041)
Your association may be affected if you:
- Use Event Registration
Original System Design: Registrant badge should be assigned to a badge class that matches the registration type.
Solution: Updated logic to use the registration product's Registration Type to populate the Badge Class.
Module(s) impacted: Events
Coupon code card total discount value now refreshes automatically.
When a Community Hub user makes an update to a cart after applying the coupon code card, the total discount amount did not recalculate. (Known Issue ID-129544)
Your association may be affected if you:
- Use Coupons
Original System Design: The coupon code card's total discount value should recalculate when products are added or removed from the cart.
Solution: The coupon code card's total discount value is recalculated automatically when the Cart is updated.
Module(s) impacted: Coupons
Seasonal Permission Changes
See the Winter '24 Permission Changes in the Security section.