Skip to main content
Skip table of contents

Spring '24 Maintenance Release

This is a list of every change made in the Spring '24 Release of Nimble AMS.

Nimble AMS Staff View

What's new?

See our latest enhancements on the (SPR24) Major Features page.


Defects Fixed

 

GL Export feature with QuickBooks is now error-free.

QuickBooks Desktop users encountered an error when attempting to import the GL Export predefined package due to SPILD in the file header. (Known Issue ID: 139849)


Your association may be affected if you: 

    • Use GL Export

    • Use QuickBooks Desktop


Original System Design: The GL Export batch header should be imported to QuickBooks Desktop without error.


Solution: Updated the file header to change SPLID to !SPL.


Module(s) impacted: GL Export

LWC component error resolved.

After the user clicks the close button on the Cancel Membership Mid-Term or One Payment modals, a LWC component error is displayed. (Known Issue ID: 138510, 140747)


Your association may be affected if you: 

    • Use Cancel Membership Mid-Term

    • Use One Payment


Original System Design: The user should be able to close the modal without error.


Solution: Resolved the error component message.


Module(s) impacted: Cancel Membership Mid-Term, One Payment

Express Payment page is now error free for Guest users.

Guest users and users who were not logged into Community Hub received an error when trying to pay for Orders/Carts while using the Express Payment page. (Known Issue ID: 141502)


Your association may be affected if you: 

    • Use Express Payments


Original System Design: The Guest users and users not logged into Community Hub should have access to the Express Payment page without error.


Solution: Removed the check for Guest user object permission while loading the page. Now, Guest users can see the Express Payment page without errors.


Module(s) impacted: Express Payments

Updated Orders are now reflected in the Avalara portal transactions.

After the successful submission of an Order with a Taxable product, a transaction on the Avalara portal will have a status of committed. If this same Order is adjusted to change the quantity or price of the Taxable items re-submitted, the re-submission fails in Staff View but the Tax amount updates in the Avalara portal which causes a mismatch of records between the Avalara portal and Staff View. (Known Issue ID: 135371)


Your association may be affected if you: 

    • Use Avalara

    • Use Tax


Original System Design: If an Order submission fails then the Tax amount should not be updated on the Avalara portal.


Solution: Added a job to make adjustments to the transaction on the Avalara portal when an Order submission fails for updated Orders.


Module(s) impacted: Avalara, Tax

eCheck - Stored Payment Method transaction dates are now the date of payment.

When a user submits an Order and makes a payment with the eCheck - Stored Payment Method (SPM), the transaction date appears as the date chosen rather than the date the payment is made. (Known Issue ID: 130423)


Your association may be affected if you: 

    • Use Stored Payment Method (SPM)

    • Use eCheck ACH Support


Original System Design: The eCheck SPM transaction date should be the date the payment is made.


Solution: Added a solution to update the Order's transaction date when eCheck Payment Methods is used.


Module(s) impacted: Stored Payment Method (SPM), eCheck ACH Support

Schedule payments now present a warning message when canceling.

An issue was observed when a scheduled payment was created for an Order that was later updated by adding a new case-based payment like a check, then deleting the payment resulting in the scheduled payment being cancelled and no payment made on the Order. (Known Issue ID: 139270)


Your association may be affected if you: 

    • Use Flexible Payments


Original System Design: In this scenario, the scheduled payment should be canceled only after the Order is submitted successfully.


Solution: Added a warning message when deleting payment if the payment method is a scheduled payment.


Module(s) impacted: Flexible Payments

Community Hub

What's new?

 

Quantity Limit removed for product purchase when Order Item Line is present.

Some end users were unable to check out in Community Hub because the Order contained a product quantity greater than the Quantity Limit permitted for a Community Hub user to purchase. (Known Issue ID: 140839)


Your association may be affected if you: 

    • Use Community Hub

    • Use Orders


Original System Design: The Quantity Limit should not prevent an end user from purchasing an Order created by a Staff user.


Solution: Removed the Quantity Limit on the product purchase using the Express Payment Order.


Module(s) impacted: Community Hub, Orders


Defects Fixed

 

Community Hub no longer redirects to the login page for logged-in users.

While a user is in Community Hub on an event detail page and clicks the 'Log In to Register' button, the user logs in with their credentials and then is redirected back to the login page. If the user tries to log in again this error message is received "Error occurred while loading a Visualforce page. The page you submitted was invalid for your session. Please refresh your page and try again." (Known Issue ID: 140458)


Your association may be affected if you: 

    • Use Community Hub

    • Use Events


Original System Design: Once a Community Hub user logs in there should not be a redirect to log in a second time.


Solution: Updates the codes by removing the cache for the pages that are redirected from the login page.


Module(s) impacted: Community Hub, Events

Chapter Directory listing loads more individuals.

Users experienced the Chapter Directory list only displaying 20 individuals with a loading icon continuing the spin at the bottom of the page. (Known Issue ID: 140493)


Your association may be affected if you: 

    • Use Chapters


Original System Design: The Chapter Directory should load and display individuals as the user scrolls to the bottom of the page.


Solution: 'Load More' function now works properly, loading more accounts when scrolling to the bottom of the page.


Module(s) impacted: Chapters

 

Colleague registrations can only be updated by the purchaser.

Registrants, who were registered for an event by a colleague, were able to see and click the Edit and Cancel buttons for that event. However, after clicking either button, the registrant received an error not allowing the registration to be adjusted as the registration can only be updated by the individual who placed the Order. (Known Issue ID: 139071)


Your association may be affected if you: 

    • Use Events

    • Use Colleague Registration


Original System Design: The Edit and Cancel button should only display to the individual who placed the Order.


Solution: Revised the logic to render the Edit and Cancel buttons to the purchaser of the Order.


Module(s) impacted: Events, Colleague Registration

Express Payment URL link now directs to the checkout page.

The Community Hub Express Payment page gave an error when an Order was submitted for recurring eligible membership after the user edited the Order by adding a different membership product and canceling the recurring eligible product from the Order. When the user clicks the Express Payment URL from the edit Order cart the error is received rather than displaying the checkout page. (Known Issue ID: 140668)


Your association may be affected if you: 

    • Use Express Payment


Original System Design: The Community Hub Express Payment URL link should display the Checkout page regardless of the type of membership product. 


Solution: Removed the requirement on the 'Auto Renew' button to render when a cart contains a recurring eligible product. Now, a check will properly display the 'Auto Renew' button.


Module(s) impacted: Express Payment

Community Hub no longer redirects to login page for logged-in users.

While a user is in Community Hub on an event detail page and clicks the 'Log In to Register' button, the user logs in with their credentials, then is redirected back to the login page. If the user tries to login again this error message is received " Error occurred while loading a Visualforce page. the page you submitted was invalid for your session. Please refresh your page and try again."(Known Issue ID: 140458)


Your association may be affected if you: 

    • Use Community Hub

    • Use Events


Original System Design: Once a Community Hub user logs in there should not be a redirect to log in a second time.


Solution: Updated the code by removing the cache for the pages that are redirected from the login page.


Module(s) impacted: Community Hub, Events

Company Profile Photo is now visible to all company managers.

The Company Profile Photo was only visible to the company manager who uploaded the profile photo. A broken image was shown for the other company managers when attempting to view the profile photo. (Known Issue ID: 139101)


Your association may be affected if you: 

    • Use Community Hub

    • Use CH Card


Original System Design: The Company Profile Photo should be visible to all company managers or affiliated individuals.


Solution: The Company Profile Photo is visible for all company managers by adding the Profile Photo field, PublicProfilePhoto_c, to the 'Upload Company Photo' care fieldset.


Module(s) impacted: Community Hub, CH Card


Nimble Create

What's new

See our latest enhancements on the (SPR24) Major Features page.


Defects

 

Nimble Create Template now uses additional HREF web protocols.

Users attempting to hyperlink text in the Nimble Create Template using the mailto, Email, or Href tags experienced a warning about the security screening process and after saving the template the tags were replaced with empty tags. (Known Issue ID: 105641, 141969)


Your association may be affected if you: 

    • Use Nimble Create


Original System Design: The Nimble Create Template should have kept the additional HREF web protocols for email and web development.


Solution: Updated the Nimble Create Template to support additional HREF we protocols (#, mailto, tel) that are standard to email and web-development.


Module(s) impacted: Nimble Create


Seasonal Permission Changes

See the (SPR24) Spring '24 Maintenance Release Permission Changes in the Security section.


JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.