Spring '23 Changelog

This is a list of every change made in the Spring '23 release of Nimble AMS.

Nimble AMS Staff View

What's new?

Introduced Renewal Cart Deletion Job for Membership Renewal Carts.

Associations that had abandoned renewal carts that was not processed into orders, were getting double charged (for Renew and Join fees), when they attempt to rejoin membership in Community Hub after the expiration of their membership (including the grace period). (AMS-12964, NC-6264, NC-6263)

Your association may be affected if you: 
•    Have unsubmitted renewal carts
•    Use the Standard Join/Renew page in Nimble AMS

Original System Design: When a constituent already has an existing renewal cart and he/she tries to JOIN the membership after the membership has lapsed, he/she was charged double (Join fees + Renew fees).

Solution: Implemented a Cart Clean-up job to run on a schedule (defined by the association), and delete the existing renewal carts, to avoid duplicate charges and help clean up the abandoned carts in the association’s environment. We also provided 2 new fields called ‘Re-Instate Period’ & ‘Re-Instate Unit’ on Membership Types set up, so associations can extend memberships beyond the grace period, if desired.

Module(s) impacted: Community Hub Cart, Membership Renewal, Memberships, Order Entry

Action Required: To implement the Renewal Cart Deletion Job in your org, please Contact Support for assistance. Read more about the new Re-Instate fields and Renewal Cart Deletion Job on Membership Types.

Additional LMS Purchase endpoint information has been added for the Nimble AMS SynchedLearning API.

Previously, the LMS Purchase endpoint returned only specific purchase details from the LMS integration such as: Id, Product, Sync Status, Complete Status, and External Id. (NAMS-1167)

Your association may be affected if you: 
•    Use Nimble AMS SynchedLearning API 

Original System Design: The LMS integration should return relevant purchase details from the LMS Purchase endpoint, such as Id, Product, Sync Status, Complete Status, and External Id.

Solution: Purchase details such as Customer Id and Order Item Line Status, are now included with the returned information from the LMS Purchases API Get response endpoint.

Module(s) impacted: Nimble AMS SynchedLearning API 

Introduced a new filter, Customer ID, to the Nimble AMS SynchedLearning API’s Purchases endpoint.

Previously, LMS systems using the SynchedLearning API's purchases endpoint were not able to narrow down LMS purchase data by a specific customer. (NAMS-1217)

Your association may be affected if you: 
•     Use Nimble AMS SynchedLearning API

Original System Design: LMS Systems should be able to narrow down customers’ LMS purchase data, by using the newly introduced Customer ID filter.

Solution: Added a new parameter to filter LMS purchase data by Customer ID.

Module(s) impacted:  Nimble AMS SynchedLearning API

Improvements to Batch schedule line processing.

Cancellation of order during schedule processing caused unrelated records in a batch to fail. (AMS-12624) 

Your association may be affected if you: 
• Cancel order(s) in Staff View or Community Hub

Original System Design: Cancelling an order, should only cancel the job related to that order.

Solution: Batch schedule line processing runs more efficiently and uses fewer SOQL queries, reducing failures when schedule lines error due to canceled orders.

Module(s) impacted: Cancel Order

Credit card refunds for payments made through Stored Payment Method (Bluepay Gateway) are now supported.

Associations encountered an error when they try to process a credit card refund for transactions whose initial payment was made through Stored Payment Method. (AMS-12967)

Your association may be affected if you: 
•    Use or have members who use credit cards with Stored Payment Method
•    Use Bluepay Gateway
•    Processed a credit card refund

Original System Design: Credit card refunds to the same credit card or a different credit card were allowed but the Stored Payment Method option was not supported.

Solution: The option to choose a Stored Payment Method, for which the payment was made, is now available when processing credit card refunds.

Module(s) impacted: Stored Payment Method, Credit Card Refunds

Defects Fixed

Scheduled job processor has been updated to accommodate Daylight Savings Time (DST).

The scheduled job processor intermittently missed scheduled payments when Daylight Savings Time starts. (AMS-12198)

Your association may be affected if you: 
•    Use Flexible payments
•    Run Scheduled jobs

Original System Design: The scheduled job processor should run all the scheduled payments irrespective of Daylight Savings Time (DST).

Solution: Adjusted the timing for scheduled job runs to accommodate Daylight Savings Time (DST).

Module(s) impacted: Scheduled Payments, Scheduled Jobs, Company Setup 

Improve DATEVALUE() accuracy for DST

To improve DST consistency, we recommend activating Salesforce improved functionality for Date Value Accuracy. 

GL Export fields and field set can now be deployed in associations' Production Org

Previously, GL export and field set deployment failed in associations' Production Org. This was encountered with the GL Export Pilot feature. (NAMS-1482)

Your association may be affected if you: 
•   Deployed GL export or field set in your Org

Original System Design: Pre-created custom field and field sets should deploy when a user attempts to deploy GL Export.

Solution: Modified the system to allow deployment of GL export fields and field set in Production Org.

Module(s) impacted: Accounting, Batch, GL Export

Removed blank pop-up for unpaid Orders with Locked transactions in Avalara.

If an unpaid Order with a Locked Transaction (in Avalara) was submitted for payment from Community Hub (CH) My-Orders page, the locked transactions caused a blank pop-up message. (AMS-12984)

Your association may be affected if you: 
•    Use Locked transactions in Avalara
•    Use Express Payments
•    Use the Community Hub My-Orders page to pay for Orders

Original System Design: The unpaid Orders should be submitted without error or blank pop-up.

Solution: Removed the pop-up warning so the transaction continues to process the Order Payment for Community Hub users.

Module(s) impacted: Avalara taxation API

Coupon logic now calculates the subtotal of Cart items from the latest Cart item lines within a Transaction

A Merchandise linked coupon incorrectly applied to a Cart resulted in a balance on the Order. (AMS-12974)

Your association may be affected if you: 
•    Use Coupons
•    Use Community Hub Orders
•    Use the Community Hub Dynamic Checkout Page

Original System Design: The CartItemTriggerHandlers class re-applies coupons after each Cart item is inserted, updated, or deleted. Then the Cart subtotal was read from the Cart item record in a separate Transaction.

Solution: Updated the Coupon logic to query the latest Cart item lines to then calculate the subtotal for the items within the same transaction.

Module(s) impacted: Coupons, Community Hub Dynamic Checkout Page

Clicking 'Register' on events in Community Hub (CH) now allows users to proceed to the event registration page.

Previously, when users clicked 'Register', the event page would sometimes reload the same page instead of proceeding to registration. This occurred if an 'Event' was created in Staff View and 'Total Registrants' field was left blank or filled with a value <=0. (AMS-12975)

Your association may be affected if you: 
•    Left 'Total Registrants' field blank during Event Setup in Staff View
•    Have users who register for events through CH

Original System Design: When a new event is created the 'Total Registrants' field on the event object defaults to 0, if left blank. Staff users should always fill in a numerical value in 'Total Registrants' field when creating an event.

Solution: A validation rule has been added to the 'Total Registrants' field on the event object. When an event is created in Staff View, an error message will display if the 'Total Registrants' field is blank or less than 0.

Module(s) impacted: Event Registration

Updated Nimble AMS Order Processor to verify Avalara’s transaction status (locked or unlocked).

Organizations using External Taxation with Avalara who also file tax records using the Avalara service would receive an error when adjusting an order in Nimble AMS when the associated transaction was “locked” in Avalara. (AMS-12874)

Your association may be affected if you:
•    Use Avalara Taxation to file your tax returns
•    Adjust transactions in Nimble AMS

Original System Design: When using Advanced Taxation-Avalara, Nimble AMS would display an error when adjusting an order with a locked transaction in Avalara. That order could not be adjusted in Nimble AMS.

Solution: Updated the Order Processor to display a warning message when a staff user attempts to adjust an order that has an associated transaction that is locked in Avalara. Staff can make the adjustment in Nimble AMS, but the changes will not be committed to Avalara and the External Taxation Status field on the Nimble AMS order will be updated to “Needs Adjustment”. Staff can then make the necessary adjustments in Avalara and update the External Taxation Status of the order in Nimble AMS to “Successful”. For transactions that are not in a locked state in Avalara, staff users can make adjustments in Nimble AMS the same as before.

Module(s) impacted: Order Processor, Accounting, Taxation, External Taxation

Made minor improvement to enhance Community Hub (CH) speed performance so payment process will now only process CH shopping carts with orders.

Community Hub (CH) users encountered slowness and error: ‘Time limit exceeded…’ when they attempt to process membership renewal via Express Payment and Hosted Payment. (AMS-12830) 

Your association may be affected if you:
•    Use Express Payment to renew membership
•    Use Payment Manager

Original System Design: CH users should be able to process membership renewal payments via Express Pay or another Hosted Payment form without extreme delay or timeout error.

Solution: Optimized query to remove a redundant query when processing carts without previous orders.

Module(s) impacted: CH shopping cart, Payment

Reference Group Number for transactions from Cancel Membership Mid-Term now generates correctly.

Sometimes the reference group number that represents a canceled transaction appears as ‘0’ when the Cancel Membership Mid-Term feature is used. (AMS-12789, AMS-12763)

Your association may be affected if you:
•    Use the Cancel Membership Mid-Term feature
•    Place a Membership Order from Staff View

Original System Design:  When staff uses the Cancel Membership Mid-Term feature to cancel a membership, a new transaction reference group number, not equal to or less than 0, should be generated for the canceled transaction(s).

Solution: Modified the system to identify the total number of transactions generated and replace the reference group numbers with the correctly generated numbers.

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

Community Hub (CH) users are now limited to 50 characters when entering Card Holder Name field for a new Credit Card.

Community Hub (CH) users encountered an error stating: ‘Something has gone wrong. Please contact support’, when they entered a value in the name field that exceeded fifty characters. They were also getting charged in the payment processor, but no payment was recorded in Nimble AMS, due to the error. (AMS-12829)

Your association may be affected if you:
•    Have CH users who make a payment with a new Credit Card
•    Have association staff who make a payment

Original System Design: Payments recorded in processor should be voided if a CH user encounters an error, during a payment transaction.

Solution: Enforced a maximum character restriction of 50 characters on Card Holder Name field. When entering credit card name details in CH and Staff View (SV), users will be limited to 50 characters. If the card holder name exceeds 50 characters, the system will not record characters exceeding 50 but payments will continue to process, and this will be recorded in Nimble AMS.

Module(s) impacted: Payment, Accounting, Community Hub

Hosted Payment Form update now uses the correct GL account for Cross Entity orders.

Associations encountered issues where a Cross Entity order was paid using a credit card, but the payment transaction debited the wrong entity’s GL account. (AMS-12834)

Your association may be affected if you: 
•    Have more than one entity
•    Use Cross Entity orders
•    Use Hosted Payment Form

Original System Design:  Cross Entity order(s) should use the correct GL account when a payment is made in Staff View and Community Hub (CH).

Solution: Updated the Hosted Payment Form to send the payment form’s entity ID when the cart’s entity does not contain the payment method.

Module(s) impacted: Cross Entity orders, Hosted Payment Forms

Failed schedule job counts are now recorded to limit the number of times failed jobs run.

When users ran a scheduled job and it failed, and then attempted to retry the process. The system processed indefinite re-try of schedule runs, even when users were no longer performing deliberate actions to run the schedule. (AMS-12822)

Your association may be affected if you:
•    Run a scheduled job and encounter failure
•    Have recurring scheduled job(s)

Original System Design: There should be an incremental record count of schedules that run and fail, so that it does not automatically run indefinitely. 

Solution: The system was updated to keep an incremental record of retries for failed schedules, before generating the order items.

Module(s) impacted: Scheduled Payments, Scheduled Payment Methods

One Payment wizard is now compatible with Lightning Web Security.

The One Payment wizard search for Accounts and Orders was not working as designed, when Lightning Web Security was enabled by default with the Salesforce Winter '23 release. (AMS-12880)

Your association may be affected if you:
•    Use the One Payment wizard and have Lightning Web Security enabled

Original System Design: The One Payment wizard search functioned as designed, before the Lightning Web Security was turned on.

Solution: The One Payment wizard search has been updated to work with Lightning Web Security enabled.

Module(s) impacted: One Payment wizard

Add to Cart button Override in Product Details LWC.

Associations and their members have an improved experience when working with the Lighting Store on Community Hub. Association staff and admin users can now define and set the destination behavior of the ‘Add to Cart' button for Products through staff view. The Add to Cart button on the Product Details LWC respects the configured destination behavior. The feature provides opportunities for Associations to offer product types other than Merchandise through the Lightning Store and control the next steps in the purchase process. As an example, Events could now be listed in the Lightning Store (with a custom data source) and the ‘Add to Cart' button on the Product Details could direct the member to the registration process. (NC-6279)

Your association may be affected if you: 
•    Use Lightning Store.
•    Use Products

Original System Design: The Add to Cart button in the Product Details LWC was previously designed to add the selected products to the user's cart.

Solution: The Add to Cart button has been made flexible to respect the destination behavior as configured by the staff admin on the product record.

Module(s) impacted: Products, Lightning Store, Product Details

Google is retiring Universal Analytics and replacing it with Google Analytics 4 (GA4).

Universal Analytics will be deprecated by July 2023 and will no longer be functional. We updated Community Hub to support Google Analytics 4 by migrating the Universal Analytics implementation to Google Analytics 4. This release update will be available when your org is upgraded to the Spring '23 release. Salesforce enforces this release update in Summer '23. (NC-6288) 

Your association may be affected if you: 
•    Use Google Analytics to collect analytics data.

Original System Design: Association's web pages currently use Universal Analytics which will be deprecated in Summer '23. Google Analytics 4 (GA4) should replace Universal Analytics.

Solution: Updated web pages to replace analytics.js with gtag.js for the following actions: measure page views, user timings, exceptions, and events and to send custom dimensions and metrics.

Module(s) impacted: Google Analytics, Community Hub

Defects Fixed

A donation made in Community Hub with or without the “About Your Donation” card now creates a Donation record when processed.

Donation records were not created when the “About Your Donation” card was removed from the Donate Now page in Community Hub. (NC-6282)

Your association may be affected if you: 
•    Use Donate Now Page in Community Hub and
•    Removed the “About Your Donation” card from Donate Now Page

Original System Design: Donation records should be created when a donation is created from Community Hub. Donation records should not be dependent on the availability of the “About Your Donation” card on the Donate Now page.

Solution: Removed the dependency on the “About Your Donation” card so that donations can be created with orders, regardless of having the “About Your Donation” card on the Donate Now page.

Module(s) impacted: Community Hub, Donate Now

Added a character limit to the Name field on the Community Hub Field Mapping

The Name field on the Community Hub Field Mapping did not have a character limit which caused an error message when attempting to save. (NC-6299)

Your association may be affected if you: 
•    Use Community Hub - Field Mapping

Original System Design: The Name field, found in the Community Hub Field Mapping module, did not have a character limitation. When saving the Field Mapping, a generic message would be displayed and not allow the Field Mapping to be saved if the Name entry exceeded 38 characters.

Solution: Added a character limit to not allow more than 38 characters to the Name field of the custom setting component.

Module(s) impacted: Community Hub - Field Mapping

Updated Labels for Field Mapping used in Single Sign-On (SSO) Community Hub (CH) setup.

Field Mapping labels appeared to be reversed for source and destination fields. Association members encountered confusion on the previous labeling for field mapping on SSO because the fields labeled: ‘Record Source’, ‘Source Field’, ‘Source Linking Field’, ‘Record Destination’, ‘Destination Field’, ‘Destination Linking Field’, ‘Name’, were reverted in the opposite direction. (NC-6270)

Your association may be affected if you:  

•    Attempted to set up SSO for Community Hub (CH)
•    Created a Field Mapping record

Original System Design: Field labels should correctly map to their respective source and destination fields during SSO Community Hub (CH) setup.

Solution: Reconfigured and relabeled Field names for Field Mapping to navigate to the appropriate source and destination fields.

Modules(s) affected: Field Mapping in CH settings, CH setup, SSO

Organizations with over 1,000 objects can now create and edit Buttons in Community Hub (CH) Setup.

Organizations with over 1,000 objects encountered an error, “Collection size 1,00xxx exceeds maximum size of 1,000” when they attempt to create or edit button records in Community Hub (CH) Setup. (NC-6277)

Your association may be affected if you: 
•    Have over 1,000 objects in your Nimble AMS org
•    Create buttons in CH Setup
•    Edit buttons in CH Setup

Original System Design: Organizations that have over 1,000 objects should be able to create or edit button records without error.

Solution: Improved CH Setup to ensure buttons can be created or edited.

Module(s) impacted: CH Setup

Read Only Field Set cards now support HTML tags in description label.

Some associations encountered issues with viewing descriptions on the Community Hub (CH) card that supports the hyperlink (HTML-based information or images) because Read Only Field Set card type did not support HTML-based descriptions. (NS-5834)

Your association may be affected if you: 
•    Use Read Only Field Set cards and want to use HTML-based descriptions

Original System Design: CH users should be able to view text and images embedded in an HTML-based description when association staff configures a Read Only Field Set card for HTML tags.

Solution: We improved the Read Only Field Set component to support HTML tags so users can get the appropriate output based on HTML tags.

Module(s) impacted: Community Hub Configuration, HTML Tag, Card Layout

Developed a membership extension period to make ‘Renew’ button available to Community Hub (CH) association members when membership is in a grace period or has lapsed.

Community Hub (CH) users were made to rejoin memberships when their membership was in a grace period or had lapsed since only the ‘Join’ button was available. Also, CH users who left unsubmitted membership renewals in their cart were double charged (Renew and Join fees) when they rejoined. (NC-6263, NC-6264)

Your association may be affected if you:  

•    Have association members that leave unsubmitted membership renewals in their cart
•    Have association members who renew their memberships after memberships had lapsed or were in a grace period

Original System Design: CH users should use the Renew button to renew their membership when the membership has lapsed or was in a grace period and was within the reinstatement period (decided by the association). Members should be charged only once, when they renew or rejoin their membership, even if they had left a membership cart unsubmitted.

Solution: Updated staff view with ‘Re-instate period’ and ‘Re-instate period unit’ fields to provide membership extension (Renew button in CH), when memberships have lapsed or were within a grace period. Associations will determine their Re-instate period (just like Grace period). For unsubmitted cart orders, staff can go into the Billing History to clean up carts as needed, to avoid double membership charges.

Module(s) impacted: Community Hub Cart, Membership Renewal, Memberships, Order Entry

Updated availability status on Donation Products that are no longer offered.

Association members were erroneously able to process payments for donation products that were no longer offered in Community Hub (CH). (NC-6250)

Your association may be affected if you:  

•    Have members that purchase the donation products in CH
•    Have donation products that were discontinued

Original System Design: When users process payments for donation products that are no longer offered, then they should get an error message and the payment button should not be visible on the Donation Checkout page.

Solution: Updated system to show an error message, “This product is no longer available for checkout”, when a donation product is no longer available for purchase.

Module(s) impacted: Donations, Payments, Community Hub

Add to Cart’ button has been removed from Lightning Store’s Product grid in Community Hub

The ‘Add to Cart’ button behavior on the Lightning Store’s Product grid was confusing. Clicking the button added the product to the cart but directed users to the product details page where they see the add to cart button again. Clicking on the button would add the product again to the cart thereby causing confusion. (NC-6280)

Your association may be affected if you:
•    Use Lightning Store on Community Hub

Original System Design: 'Add to Cart’ button within the Product grid was meant to provide an easy way to add a product to the shopping cart.

Solution: At this time, the ‘Add to Cart’ button has been removed from the Product grid to improve functionality and in the future, align it with the Experience Cloud Community Hub features.

Module(s) impacted: Community Hub Lightning Store

Seasonal Permission Changes

See the Spring '23 Permission Changes in the Security section.