Summer '24 Changelog
This is a list of every change made in the Summer '24 Release of Nimble AMS.
Nimble AMS Staff View
What's new?
See our latest enhancements on the Major Features page.
Defects Fixed
The billing History Trigger now recalculates without error.
Staff users experienced a Salesforce SOQL query limitation when canceling an Order item from Bulk Billing, specifically a Billing History with over 50,000 Order items. The Bulk Billing query used the Billing History Id to search for the Order Item to cancel. (Known Issue ID: 142683)
Your association may be affected if you:
Use Orders
- Use Order Processor
- Use Bulk Billing
Original System Design: The Billing History Trigger should not hit the Salesforce query limit when recalculating Billing History for bulk Orders.
Solution: Updated the Billing History Trigger step to now initiate a batch job to perform the recalculation asynchronously and in bulk.
Module(s) impacted: Orders, Order Processor, Bulk Billing
The primary Chapter field on the Account no longer updates to null.
When updates were made to the Account affiliation object and the primary checkbox equaled true, the Primary Chapter field on the Account updated to null even if the Account had a Primary Account affiliation present. (Known Issue ID: 138153)
Your association may be affected if you:
Use Chapters
Original System Design: The Primary Chapter field on the Account should not update to null when a Primary Account affiliation is present.
Solution: Prevented the Primary Chapter field on the Account from updating to null when updates to the Account affiliation object are made.
Module(s) impacted: Chapters
Queue process records now process without error.
For some clients, Queue process records were created and captured payments, but the Queue process record remained in the queue and was never processed. This resulted in the Payment records not updating with the latest Transaction ID and other relevant information, that is tracked on the Payment after it has been captured. This caused the Payments in Nimble AMS to not be refundable without the help of the Nimble AMS support team. (Known Issue ID: 119009)
Your association may be affected if you:
Use Community Hub (CH)
- Use BluePay
- Use Authorize.Net
- Use Hosted Payment Forms
Original System Design: The Queue process records should not update if the payment is already captured.
Solution: After this change, the payment processor transaction ID and reason message will not be updated if the payment is already captured. This job will also clean up related Queue Process records.
Module(s) impacted: Community Hub, BluePay, Authorize.Net, Hosted Payment Forms
Now Sales Tax calculation remains on adjusted Orders.
Payment imports failed due to missing/mismatched taxes on Orders when using the USAvalara Tax calculation code. When an Order is placed with the Tax calculation code, USAvalara, the code remains throughout the Order process submission, however, when adjusting an existing Order, the Sales Tax calculation is removed, and the end user needs to re-enter the code to recalculate the Sales Tax. (Known Issue ID: 142643)
Your association may be affected if you:
Use Avalara
- Use Sales Tax
Original System Design: Adjusting an existing Order should not remove the calculated Sales Tax.
Solution: Added a condition to check if the account is not Tax-exempt.
Module(s) impacted: Proration, Membership
Proration Rule now updates the product price of an Order.
After a Membership product, with a set Proration Rule, is added to an Order and then edited by changing the start date, the product price does not update according to the Proration Rule. (Known Issue ID: 140557)
Your association may be affected if you:
Use Proration
- Use Membership
Original System Design: When the Order is edited the product price should update as per the Proration Rule.
Solution: Users will now see the product price update to the proration amount for products with a Proration Rule.
Module(s) impacted: Proration, Membership
Membership products reflect Price Class updates.
When Staff users edit Orders to update the Price Class for Membership Renewal Orders, the product price does not change according to the Price Class. (Known Issue ID: 139981)
Your association may be affected if you:
Use Accounts
- Use Price Class
- Use Memberships
Original System Design: The product price should have reflected the updated Price Class when existing Orders are edited.
Solution: Updated Price Class logic for existing Orders.
Module(s) impacted: Accounts, Price Class, Memberships
Stored Payment Method - eCheck now supports batch health.
After users submitted an Order using the Stored Payment Method (SPM) - eCheck type, a pop-up prompted users to maintain batch health by defaulting to today's date, however, the transaction date field allowed users to choose a future date. The future date was then captured on the Order record as the transaction date, payment date, and batch date rather than the date the Order was submitted. (Known Issue ID: 142190)
Your association may be affected if you:
Use Stored Payment Method (SPM) - eCheck payment method
Original System Design: To maintain batch health, the transaction date should not be editable once the Order is submitted.
Solution: Updated the logic to ensure batches are populated correctly for entities with either credit card or bank account payments.
Module(s) impacted: Stored Payment Method (SPM)
Deferred Schedule calculation updated.
Deferred Schedules became unhealthy when the Deferred Revenue Recognition type is set to Summary and the Deferred Schedule record has multiple Order Item Line records linked to the Deferred Schedule. This also happens if Mid-Term Cancellation is applied to Memberships included in the Deferred Schedule calculation. (Known Issue ID: 141949)
Your association may be affected if you:
Use Deferred Schedules
Original System Design: The recognition calculation should result in the recognized amount equal to the recognition amount.
Solution: Updated the Deferred Schedule calculation so that the recognized amount and recognition amount are the same to obtain healthy Deferred Schedules and accurate forecast details.
Module(s) impacted: Deferred Schedules
The currency symbol "$" will now be visible on the Net Value section of the invoice.
In a NU trial build after selecting the invoice button, the Net Value section of the invoice did not have the currency symbol "$" when the Multi-Currency tag was turned off.
Your association may be affected if you:
Use Mutli-Currency
Original System Design: The currency symbol, $, should be displayed on the Net Value section of the invoice.
Solution: Updated the invoice component by creating a formula field for the value section.
Module(s) impacted: Mutli-Currency
Export GL file now counts numbers for grouping records as provided in the CMT record.
The line counter of the GLExportBatchableJob re-set after every 200 lines or records, which did not include records across the entire process per batch ID disrupting the accounting process. The Batch File that is generated is based on time, causing multiple files to run at the same time risking overwriting each other. (Known Issue ID: 141112)
Your association may be affected if you:
Use NAMZ GL Export
Original System Design: The GLExportBatchableJob job should have run for the entire batch ID process.
Solution: The GLExportBatchableJob job now runs by grouping without resetting the count when 200 records is processed. A naming convention of a four-digit unique value is also implemented to prevent file overwriting for uploads occurring within one minute.
Module(s) impacted: NAMZ GL Export
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
Payments now apply to the product's payment gateway for Community Hub with multiple Entities.
When Hosted Payment Forms is configured for at least one Entity with multiple payment gateways (with different credentials) and an Order is processed in Community Hub (CH) against this Entity, which is not the main CH Entity, the payment will be incorrectly recorded against this secondary Entity but processed against the main CH Entity's payment processor. (Known Issue ID: 144013)
Your association may be affected if you:
- Use Hosted Payment Forms
- Use multiples Entities
- Use the Donate Now page
- Use Community Hub
Original System Design: The payment should have gone against the product's Entity's payment gateway.
Solution: Now, when using the Donate Now page to check out in a Community Hub that has Hosted Payment Forms enabled, the product's Entity determines the payment gateway.
Module(s) impacted: Community Hub, Hosted Payment Forms, multiple Entities, Donate Now page,
Profile Photo displays on the Company Snapshot page without error.
In Community Hub, the Company Snapshot page displayed text near the Profile Photo, when an affiliated individual account uploaded the Profile Photo for the Company account. This happened only when the Profile Photo field had read access on the Community Hub Login User profile. (Known Issue ID: 142237)
Your association may be affected if you:
- Use Community Hub (CH)
- Use CH Company Affiliation
Original System Design: The Profile Photo should be displayed without text when an affiliated individual account uploads the photo for the Company account.
Solution: Updated logic to display the Profile Photo on the Company Snapshot page without the text value near the photo.
Module(s) impacted: Community Hub, CH Company Affiliation
Now the Event Registration Type defaults to Registrant.
Event admins did not assign Registration Types to an event which resulted in Community Hub users being asked to choose from a picklist of values causing the Badge Class field to be null. (Known Issue ID: 142450)
Your association may be affected if you:
- Use Event Registration
- Use Events
Original System Design: The Registration Type should default to Registrant.
Solution: Updated logic to a default value when the Registration Type is not assigned on the Event Record.
Module(s) impacted: Event Registration, Events
The non-Bill Me enabled message now appears once.
The message, "The ability to pay later is not available at this time because items in your cart must be paid via credit card," appeared twice when a Community Hub user added a Bill Me enabled Registration product and a Non-Bill Me enabled Membership product to a cart then attempted to select Bill Me as the payment type. (Known Issue ID: 138901)
Your association may be affected if you:
Use Bill Me
- Use Membership
- Use Event Registration
Original System Design: The message should appear once for the Non-Bill Me enabled products.
Solution: Added the message to the payment option messages list to prevent the duplicate message.
Module(s) impacted: Bill Me, Membership, Event Registration
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 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: 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 Summer '24 Seasonal Release Permission Changes in the Security section.