Summer '23 Changelog
This is a list of every change made in the Summer '23 release of Nimble AMS.
Nimble AMS Staff View
What's new?
Configurable Batch Size for Nightly Deferred Schedule Recognition Job to process large volumes of data.
The nightly Deferred schedule recognition job is prone to failure due to various factors such as processing large volumes of data or lack of system resources and it is not possible to adjust the batch size.
Your association may be affected if you:
- Using Deferred Revenue
Original System Design: The user should be able to configure the Batch Size for the Nightly Deferred Schedule Recognition Job.
Solution: Administrators can configure the batch size for the nightly Deferred schedule recognition job. This will allow them to adjust the batch size to prevent job failures and guarantee successful completion. To learn how to change the setting, please see Configurable Batch Size for Nightly Deferred Schedule Recognition Job .
Module(s) impacted: Deferred Revenue
Defects Fixed
A deferred Schedule recognizes the correct amount when multiple orders are edited to change the price of an item.
When a user made simultaneous edits to multiple order items, the related deferred schedules did not show the correct amount. (Known Issue ID-128137)
Your association may be affected if you:
- Using the Deferred Revenue Method
Original System Design: When users make changes simultaneous to multiple order items, deferred schedules are also updated with the correct amount.
Solution: A new query with the "For Update" clause is added to address this issue.
Module(s) impacted: Deferred Revenue Method, Order.
Deferred schedules with large order item lines are accurately recognized when Cancel Membership Midterm is disabled.
Cancel Membership Midterm, while enabled or disabled, required for all the Order Item lines associated with a deferred schedule to load causing a SOQL limit error. (Known Issue ID-132334)
Your association may be affected if you:
- Use Deferred Revenue
- Use Cancel Membership Midterm
Original System Design: Deferred revenue recognition should have been completed successfully for Deferred Schedules containing large numbers of Order Item lines.
Solution: Updated logic to allow deferred schedules with large numbers of order item lines, as long as midterm membership cancellation is disabled.
Module(s) impacted: Deferred Schedules, Cancel Membership Midterm, Order Item Lines
Event Badge lookup now populates when Orders are created via the Order API.
Previously, the Event Badge field was not populated on the Order Item Line record when the Order was placed from the Order API. (Known Issue ID- 123809)
Your association may be affected if you:
- Use Event Registration
- Use Event Badge
Original System Design: The Event Badge field should populate on the Order Item Line record when an event registration order is created via the Order API.
Solution: Improved logic to populate the Event Badge field on the Order Item Line record, when a registration order is placed via the Order API.
Module(s) impacted: Event Registration, Events, Event Badges
One Payment Wizard now respects the Date of actual payment for credit/stored payment.
One Payment Enters Transactions in Wrong Batch / Date. (Known Issue ID-126054)
Your association may be affected if you:
- Use One Payment
- Create manual batches
Original System Design: If user is using One Payment with Cash or Check (non credit) and choosing a manual batch, then the date from the selected batch should be carried over as date of the payment transaction.
- If user is using One Payment with Credit Card and choosing a manual batch with a batch date of today, then the date from the selected batch should be carried over as the date of the payment transaction.
- If user is using One Payment with Credit Card and choosing a manual batch and a batch date is not today, then the payment transaction should have todays’ date.
Solution: Added a logic to check one payment with Credit Card & stored payment method.
- If payment is using Credit/Stored payment with manual batch and the batch is for Today, then use the date from the selected batch for the payment transaction.
- If payment is using Credit/Stored payment with manual batch and the batch is Not for Today, then use the batch of the current day and todays’ date will reflect on transaction record.
Module(s) impacted: One Payment, Manual Batch, Batches
Auto-renewal no longer creates duplicate schedules when clicking the Save button multiple times while setting up Recurring payments.
Duplicate renewal schedules occurs when a member selects the Auto-Renew Frequency for setting up Recurring Payment and clicks ‘Save’ multiple times. (Known Issue ID-125761)
Your association may be affected if you:
- Have members who configure Auto-Renew Frequency in Community Hub (CH)
Original System Design: The configuration of the Auto-Renew Frequency field should create 1 schedule each time when a member selects the Auto-Renew option in CH.
Solution: Configured the ‘Save’ button to disable after the first click. When members click ‘Save’ the first time, members will not get the option to click ‘Save’ again till the schedule creation/update process runs fully.
Module(s) impacted: Community Hub, Auto-Renew Membership
Coupon discount now recalculates based on the latest cart product when an order is edited.
Coupons applied on Event registration do not recalculate if the registration order and the product is changed to a different product. (Known Issue ID-129045)
Your association may be affected if you:
- Have Community Hub users who modify an Event registration order
- Use coupons
Original System Design: When a coupon gets applied on an Event registration product, while in a cart and the cart item is changed, the coupon should recalculate based on the new cart item and new total.
Solution: Added a logic to recalculate coupons on adjusted orders for Event Registration.
Module(s) impacted: Community Hub, Coupons
Resubmitting or canceling an adjusted membership order will no longer cause an error.
Error: "Problem when making a REST API call to Avalara through the SDK...uncommitted work...commit or roll back", occurs when resubmitting a membership order that was previously canceled or when canceling an adjusted cart order. (Known Issue ID-131045)
Your association may be affected if you:
- Cancel a membership order
- Have external taxation (Avalara) enabled
Original System Design: Enabling external taxation should allow for membership orders to be canceled, adjusted, or resubmitted if the membership period has not begun.
Solution: Ensure external taxation is enabled and taxes are calculated before performing payment transfer.
Module(s) impacted: Memberships, Avalara
When using One Payment, an Account's Stored Payments will not show up for a different Entity's Order.
The wrong entity’s payment method pops up on One Payment when a staff user attempts to make payment for orders. (Known Issue ID-129991)
Your association may be affected if you:
- Use One Payment
- Use Entity Crossover
- Use Stored Payment Method
Original System Design: One Payment should only show payment methods for the entity in which the order was generated.
Solution: Updated One Payment logic to only show the Stored Payment Method connected to the original order entity.
Module(s) impacted: One Payment, Entity Crossover
Guest users can now submit payments for chapter membership via Express Payment.
Guest users were getting error “FIELD_INTEGRITY_EXCEPTION, field integrity exception…” when they attempt to use Express Pay (Payment url) to pay for Chapter Membership. (Known Issue ID-130334)
Your association may be affected if you:
Use Express Payment for chapter membership
Submit payment as Guest user
Original System Design: When a Guest user applies a coupon on an event registration product while in a cart and the cart item is changed, the coupon should recalculate based on the new cart item and new total.
Solution: Updated the Chapters cart submitter logic for to allow a Guest user to submit the payment using the express payment method.
Module(s) impacted: Chapter Membership, Account Affiliation, Express Payment, Cart
Automatic Sales Tax rate calculation now applies to taxable Registration Products.
Previously, when Staff users created new Roders for non-Merchandise products (specifically Registration Products) the Sales Tax rate was not automatically selected on the Tax and Shipping page. (Known Issue ID-129169)
Your association may be affected if you:
Use Orders
Use Sales Tax
Original System Design: The Sales Tax rate should have automatically been selected if the product was taxable.
Soultion: Added support for automatic Sales Tax rate selection for taxable Registration products. The Sales Tax will be calculated on the Tax and Shipping page.
Module(s) impacted: Orders, Sales Tax
One Payment no longer duplicates charges for Sales Tax and Shipping.
One Payment function charged Sales Tax and Shipping multiple times within a transaction but did not initiate payments for those duplicate charges, creating an accounting discrepancy. (Known Issue ID-129423)
Your association may be affected if you:
Use One Payment
Collect Tax or Shipping on products
Original System Design: One Payment function should charge and collect Sales Tax and Shipping once per transaction.
Solution: Assigned the existing order items to the transaction generator requests to avoid duplicate transaction entries.
Module(s) impacted: One Payment, Order Entry
MapQuest API now accepts the address without error.
Previously, addresses were encoded prior to sending to MapQuest API, which caused an invalid request type error. (Known Issue ID- 129948)
Your association may be affected if you:
- Use Account Address
Geolocation Updater
MapQuest API
Original System Design: Addresses were encoded prior to sending to MapQuest API.
Solution: Updated logic to remove the encoding of the address.
Module(s) impacted: Account Address
Payments with expired coupons will not process.
Customers that have expired coupon applied to their cart can still process their order, if the coupon was valid at the time it was applied to the cart item, but the cart item was paid for, at a later date, after the coupon expired. (Known Issue ID-132609)
Your association may be affected if you:
Use Coupons
Original System Design: The Cart payment should have been voided if the coupon applier operation failed.
Solution: If the Coupon applier operation fails then the Cart Payment will void.
Module(s) impacted: Coupons, Community Hub
Copy from Start Date link no longer resets product selection.
When the "Copy from Start Date" link was clicked, the modified membership information on the order process page was reset, forcing customers to enter the membership dates and prices again.(Known Issue ID-117585)
Your association may be affected if you:
Use Orders
Original System Design: The system should have kept the membership dates and price after the ‘Join On’ date was adjusted.
Solution: Removed the logic to reset the membership date and price when the ‘Join On’ date is changed.
Module(s) impacted: Order Process, Membership, Orders
Guest checkout with Hosted Payment Forms updated for Sale transactions.
Staff users were confused by errors and emails that resulted from the creation of Queue records for Sale transactions. The Queue records were created when a Community Hub Guest User utilized Express Checkout with Hosted Payment Forms. BluePay processed the transaction as a Sale type and a Queue record for Credit Card capturing was created. (Known Issue ID-122798)
Your association may be affected if you:
Use BluePay
- Use Hosted Payment Forms
Original System Design: A queue process record should not be created by the system for SALE transactions.
Solution: Updated system logic to exclude the creation of queue process records for SALE transactions.
Module(s) impacted: BluePay, Hosted Payment Forms
Recurring payments with crossover entity now improved.
When flexible payment is configured with a crossover entity, the Staff users were unable to set up recurring payments for an Order when the Entity on the Order Item is different than the Entity on the stored payment bills too. (Known Issue ID-120281)
Your association may be affected if you:
Use Recurring Payments
- Use Flexible Payments
- Use Crossover Entity
Original System Design: The system should enable the Stored Payment Method to be accessible for the entity associated with the Order item within the Recurring Payment component.
Solution: The logic is now updated to retrieve the Order item Entity for the Stored Payment Methods.
Module(s) impacted: Flexible Payments, Crossover Entity
When the "Copy From Mailing Address" field is selected, the State and Country/Territory values are copied accordingly.
The State and Country/Territory values did not copy when utilizing the “Copy From Mailing To Billing”, “Copy From Mailing To Other”, Copy From Mailing To Shipping” checkboxes. (Known Issue ID-120796)
Your association may be affected if you:
Use Community Hub
Original System Design: The State and Country/Territory should have been copied over to addresses if the State and Country/Territory picklists were enabled.
Solution: Added support for the State and Country/Territory values of the mailing address to be copied when the “Copy From To Mailing” Address field is checked, and State and Country/Territory Picklists are enabled.
Module(s) impacted: Community Hub
Sales Tax now calculates from Event address when present.
Staff users creating a new Order encountered the Sales Tax being based on the Account address rather than the Event address. This occurred when selecting an event registration for an Account where the Product is taxable. (Known Issue ID-132443)
Your association may be affected if you:
Use Sales Tax
- Use Orders
- Use Order Processor
Original System Design: The system should have selected the Sales Tax of the Event address.
Solution: Added support to automatically select the Sales Tax of the Event address, if the event address is blank the account address is used.
Module(s) impacted: Sales Tax, Orders, Order Processor
For Guest Users, credit card and stored payment transactions processed through Hosted Payment are consolidated into batches based on the actual payment date.
In the past, if guest users submitted payments for carts/orders linked to a past date batch through hosted payment, it resulted in transactions being linked to an invalid batch. (Known Issue ID-132119)
Your association may be affected if you:
Hosted Payment Forms
- Batches
Original System Design: Guest users were able to submit Carts with a date in the past.
Solution: The logic has been updated to either update or create a batch, depending on the actual payment date of the Cart/Order, for Guest users when making a payment through hosted payment.
Module(s) impacted: Batches, Hosted Payment Forms
Community Hub
What's new?
Nimble AMS branded sunburst icon represents the Nimble AMS LWCs.
Previously, different icons were used to represent the Nimble AMS Lightning Web Components (LWCs). Now it's simple to recognize the Nimble AMS LWCs by the Nimble AMS branded sunburst icon.
Your association may be affected if you:
- Use Community Hub
Original System Design: Different icons were used to represent the Nimble AMS Lightning Web Components (LWCs).
Solution: The Nimble AMS branded sunburst icon represents the Nimble AMS LWCs.
Module(s) impacted: Community Hub
Defects Fixed
Community Hub users can now successfully process orders using eCheck Stored Payment.
Some Community Hub orders were declined when specifically selecting an eCheck Stored Payment Method that has a discrepancy with the Nimble AMS Record Name and Nimble AMS Record Type. For example, orders processed with an eCheck Stored Payment Method with a Record Name of ACH and a Record Type of eCheck would not be processed. (Known Issue ID- 100660)
Your association may be affected if you:
- Use Stored Payments
- Use eCheck ACH support
Original System Design: The system should have compared the Stored Payment Method to the Record Type rather than the Record Name.
Solution: Updated the logic to have Stored Payment Method reference Record Type during payment processing.
Module(s) impacted: Stored Payments, eCheck ACH Support
Error message added to Donate Now page for non-eligible donation products.
Community Hub users were able to find and process payments on Donation products that were no longer offered. The user was able to access the Donation products through the Checkout URL then fill out the Suggested Amounts section and the rest of the page. (Known Issue ID-131991)
Your association may be affected if you:
- Use Donation Products
- Use Community Hub
- Use Community Hub Donations
Original System Design: When a Donation product is not available, the page should not allow the user to process the payment.
Solution: Added an error message, "This product is no longer available for checkout" to the Donate Now page, when non-eligible donation products, such as Inactive donation products and non-self-serviced donation products, are accessed.
Module(s) impacted: Donation Products, Community Hub
Resolved 38-character restriction on the customization setting fields to only apply to Field Mapping.
Fields like google analytics and custom class names were blocked or cut off due to the 38-character limit. (Known Issue ID-131098)
Your association may be affected if you:
- Use the Customization setting
Original System Design: All Customization fields had a 38-character limit.
Solution: Limited the 38-character enforcement to 'custom setting name’ field only.
Module(s) impacted: Customization settings, Community Hub Setup
An error when using an expired Stored Payment Method to set up Recurring payments is now rectified.
When an expired Stored Payment Method (SPM) is utilized to establish Recurring payments, an error will occur during cart submission, and the data field will be labeled with the SPM ID. If the Community Hub user removes, modifies, or generates a valid SPM, the error persists since the data field retains the old SPM ID. (Known Issue ID-129462)
Your association may be affected if you:
- Use Flexible Payments
- Use Stored Payment Method
Original System Design: The data field should be updated to the new SPM ID once the Stored Payment Method becomes valid.
Solution: Updated the logic to verify the expiration date of the external payment profile record before automatically assigning it to a recurring item. This will result in the data field being updated with the new SPM ID.
Module(s) impacted: Stored Payment Method, Flexible Payments
Lightning Store now arranges the product grid by using the Display Sort Order field.
The Lightning Store product grid did not respect the Display Sort Order field when presenting the layout of merchandise/products. (Known Issue ID-120356)
Your association may be affected if you:
- Use Lightning Store
Original System Design: The Query Datasource should have sorted the products based on the Display Sort Order field on the product.
Solution: Added a query plugin while retrieving products using the SOQL data source to sort them by the DisplaySortOrder__c field.
Module(s) impacted: Lightning Store
Community Hub $0 balance Carts can now be submitted.
Community Hub user were unable to process payments when the Cart has a $0 balance due to the user of a Coupon while Hosted Payment Forms is configured. (Known Issue ID-130546)
Your association may be affected if you:
- Use Coupons
- Use Hosted Payment Forms
Original System Design: Coupons should apply to cart items even when it is a 100% off coupon that leaves the car at $0 balance.
Solution: Added a check for the Cart balance amount, if the Cart balance is $0 the Submit button will render. The user should allow the Cart to process without entering payment information.
Module(s) impacted: Hosted Payment Forms, Coupons
Allow In Place editing works for Validation Rule.
Allow In Place editing did not update fields value after the validation rule was triggered. The field values were corrected but the field did not save the new input. (Known Issue ID-129784)
Your association may be affected if you:
- Use Community Hub Card
Original System Design: The field should have been updated to the new input.
Solution: Added support to retain the updated field value after encountering a validation error.
Module(s) impacted: Community Hub
A validation error message is displayed when a validation rule fails.
When a validation rule fails, the system displays an error message stating "Duplicate ID in the list" at the top of the page instead of a validation error message. (Known Issue ID-129802)
Your association may be affected if you:
- Use Community Hub Card
Original System Design: The system should have displayed a validation error message.
Solution: Improved logic to show a validation error message when the validation rule failed.
Module(s) impacted: Community Hub
Seasonal Permission Changes
See the Summer '23 Permission Changes in the Security section.