Winter'25 Changelog
This is a list of every change made in the Winter '25 Seasonal Release of Nimble AMS.
Nimble AMS Staff View
What's New?
Enhancement: Add to Calendar Feature for Event Registrations in Experience Cloud Community Hub
We have enhanced the Experience Cloud Order Summary page by introducing the "Add to Calendar" feature for event registration products. After your members have successfully registered and completed their payments for an event, they will see an "Add to Calendar" icon next to the event details. By clicking on that icon, a .ics file will be automatically downloaded, allowing them to add the event to their Google or Outlook calendar quickly.
This enhancement aims to provide better convenience to your members and make them stay organized. Allowing the Associations to provide a better member experience. (Learn More)
Your association will benefit if you allow:
Purchase of Event Registration products
Use Experience Cloud Order Summary LWC
Enhancement: Introducing the Configurable Continue Shopping Button on the Shopping Cart page
A new Continue Shopping button is now available on the Shopping Cart page, offering members the flexibility to return to a specific shopping page defined by your Association staff. This button is point-and-click configurable, meaning it can be tailored to direct members to any desired shopping page, such as store, membership join & renew, event registrations, or donations.
This enhancement is aimed at further improving the member experience by streamlining navigation and encouraging further engagement. (Learn More)
Your association will benefit if you:
Use Experience Cloud Shopping Cart LWC
Enhancement: Introducing Inventory Alerts on the Product Item Details Page
We’ve introduced an inventory alert feature on the Product Item Details page that notifies members when a product's stock is running low. The alert displays a customizable message, such as "Hurry, only 'n' left in stock," where 'n' is the remaining quantity. This feature is controlled by the Inventory Warning Threshold property within the Product Item Details Lightning Web Component, allowing Association staff to set the specific inventory level that triggers the alert. The alert message can also be customized to better align with your Association’s communication style, ensuring members are informed and motivated to act quickly. (Learn More)
Your association will benefit if you:
Use Experience Cloud Product Item Details LWC
Enhancement: Receipt Button Redirection on My Orders LWC
We’ve introduced a new enhancement to the My Orders page, providing associations with greater control over the post-purchase experience. Previously, members were automatically redirected to the out-of-the-box Order Summary page when clicking the Receipt button for fully paid orders. With this update, association staff can now customize where the Receipt button directs members, using a point-and-click configuration. This update empowers associations to deliver a more consistent and personalized user experience, reinforcing their brand and meeting specific operational needs. (Learn More)
Dynamic Filter Enhancement: Multi-Select Picklist Support
We’ve expanded the Dynamic Filter to support multi-select picklist fields, offering associations greater flexibility in configuring their Lightning Store filters. This enhancement allows members to filter products based on multiple values within a single category. For instance, if a product is available in multiple states like California, Virginia, and Washington DC, members can now filter by these specific states to find the product relevant to their location. This streamlined filtering capability improves the user experience and simplifies the product search process, making it easier for members to find what they need.
Enhancement: Control Over Displaying Primary Affiliation on the Visualforce Order Summary page
We have introduced a new level of customization for the Visualforce Order Summary page! Association staff can now control whether the Primary Affiliation Account Name appears in the "Bill To" and "Ship To" sections of the Order Summary. This enhancement is managed through the new DisplayAffiliationonOrderSummary custom metadata tag, giving you more flexibility to align with your organization's unique business practices.
This update allows Association members to experience a more personalized and streamlined Order Summary, focusing on the details that matter most to them. For Associations, it provides enhanced control and flexibility to present relevant information that aligns with your business needs, helping to improve member satisfaction and overall experience.
To avoid any disruptions to your members' shopping experience, we’ve set the DisplayAffiliationonOrderSummary tag to On by default. This means the Primary Affiliation Account Name will continue to appear on the Order Summary page as it currently does. However, should your Association prefer not to display this information, staff can easily turn the tag Off at any time, providing the flexibility to adapt to your specific needs without impacting the member experience. (Learn More)
Your association will benefit if you:
Use Account Affiliations
Use Order Management
Use out-of-the-box Nimble AMS Visualforce Order Summary Page
Enhancement: Process Eligible Past Inst. Schedules Custom Setting
We’ve introduced a new Custom Setting, Process Eligible Past Inst. Schedules, to enhance the functionality of Payment Schedules. Previously, the nightly job would only process failed payment schedules from the past and currently qualified ones. With this new toggle, Associations can now opt to include past-dated ongoing payment schedules, ensuring that all eligible payments are automatically processed, even if they were scheduled for a previous date.
This enhancement provides Associations with more flexibility and control, allowing them to ensure that all ongoing payment commitments are met without missing any important payment dates. By enabling this toggle, you can seamlessly manage and process all payment schedules, improving cash flow and member satisfaction.
To avoid any disruption to your current payment processing workflow, we have kept the Process Eligible Past Inst. Schedules toggle off by default, ensuring that the system continues to operate as it does today. However, should your Association staff wish to take advantage of this new enhancement, they can simply turn the toggle on to automatically process past-dated ongoing payment schedules, ensuring no eligible payments are missed. (Learn More)
Your association will benefit if you:
Use Schedule Payments functionality
Enhancement: Queue Process Records Visibility for CreditCardPaymentCapturer job failures
By introducing the two new fields, we have improved the Queue Process records visibility for CreditCardPaymentCapturer job failures. When CreditCardPaymentCapturer jobs run in the system, queue process records are created. If the job succeeds, the queue records are removed. However, if the job fails, the records remain stuck in the system without clear visibility for staff or administrators to identify the cause of the failure. This lack of clarity makes addressing or resolving the underlying issues challenging.
To improve visibility into job failures, two new fields were introduced into the queue process record:
Status: Indicates whether the job passed or failed, providing a quick visual cue for staff/administrators.Error Message: Provides detailed information about the cause of the failure, helping administrators identify and address specific issues more efficiently. (Learn More)
Your association will benefit if you:
Use Queue Process
Use Scheduled Jobs
Enhancement: Introducing Orange colored icon for Grace Periods
We’ve added an orange flag to the Status Membership Flag field on the Account record to indicate when a member's membership is in the grace period. The new orange flag helps association staff easily recognize and respond to members in the grace period, enabling timely decisions such as offering discounts, extending deadlines, or providing personalized renewal options, which can enhance member retention and satisfaction. (Learn More)
Your association will benefit if you:
Use Memberships
Use Accounts
Provide grace periods for your members
Enhancement: Introducing the "Optional for Staff" Checkbox for Event Questions
We’ve added the Optional for Staff checkbox to Event questions, allowing Association staff to bypass certain mandatory questions when registering members through the Order Processor. This enhancement ensures that questions marked as Required for members on the portal can still be optional for staff, speeding up registrations without sacrificing the quality of data collected from members. This feature addresses customer needs for a more flexible and efficient registration process. (Learn More)
Your association will benefit if you:
Use Events with questions
Use staff view Order processor
Enhancement: Refunds Enabled for Prepayments with Closed Batches
Our Prepayments functionality has been upgraded to allow refunds for unused balances, even when the associated batch is closed. This improvement streamlines financial processes and ensures a smoother experience for both staff and members by enabling more timely and flexible refund handling. (Learn More)
Your association will benefit if you:
Use Prepayments
Enhancement: Cash Bulk Billing Flexibility for Optional Products
We’ve added a new "Exclude from Billing" checkbox to the MTPL record, allowing staff to prevent optional membership products from being included in automatic renewals. By default, this checkbox is unchecked. When checked, it ensures that optional products, such as one-time upgrades, are not billed repeatedly. This enhancement empowers your Association Staff to tailor cash bulk billing processes more precisely, avoiding unnecessary charges and aligning with the specific needs of optional products. (Learn More)
Your association will benefit if you:
Use Cash Bulk Billing
Sell Membership Products that are optional along with the Primary Membership products
Enhancement: Flexible Balance Payment Transfer Capabilities
We've improved our payment transfer functionality to give associations more flexibility in managing orders. Previously, you could transfer payments from a canceled cart item to an active one within the same order. Now, you can also transfer overpayments from an active cart item to cover any outstanding balance on a canceled cart item. This enhancement ensures more efficient use of funds and simplifies order adjustments, allowing for precise and effective financial management within your association's transactions.
This enhancement does not support Automatic Balance Transfer. This requires manual intervention by the Association Staff. (Learn More)
Your association will benefit if you:
Use Payment Transfers functionality
Enhancement: Direct access to Order ID from the History Records
We’ve added a new Order field to the Product Type History record page to display the associated Order number, complete with a hyperlink that takes users directly to the Order detail page. This improvement eliminates the need for staff to click through multiple layers (Order Item Lines, Order Item) to reach the Order, streamlining their workflow, and addressing customer needs for more efficient order management. (Learn More)
Your association will benefit if you:
Use Orders
Defects Fixed
Sales Tax is now applied to appropriate Orders
Staff View users create a Cart with taxable products which populates the NU_SalesTax_c field in the Cart item, however, once a nontaxable Coupon is applied to the Cart, a Tax recalculation sets the NU_SalesTax_c field to null. This causes the GL account field in the transaction record to be null. (Known Issue ID: 146331)
Your association may be affected if you:
Use Avalara
Use Coupons
Original System Design: The RecalculateTax method should have applied appropriate Sales Tax to both taxable and nontaxable products.
Solution: Updated recalculateTax method to correctly set the NU_SalesTax_c field for taxable and nontaxable Coupon products.
Module(s) impacted: Avalara, Coupons
The batch size for the Credit Card process job is now configurable
Admin users noticed the Queue process for capturing Credit Cards stopped when too many 'CapturedCreditCardPayment' records were 'pending capture' status. Error message "Batchable instance is too big" was reported. (Known Issue ID: 145970)
Your association may be affected if you:
Use Order Entry
Original System Design: The Credit Card process job should not stop while 'CapturedCreditCardPayment' records are in a 'pending capture' status.
Solution: Now, admin users can specify the batch size when running the NU.CreditCardPAymentCapturer job from the GlobalEntryPoint class.
Module(s) impacted: Order Entry
Handling Duplicate Payment Schedules
When two or more payment schedules with the same membership information are created for a single account, only one schedule successfully converts the cart into an order when processed. The other schedules, created due to lack of validation, also capture payments but remain as carts in the system. As a result, the admin must manually handle cancellations and refunds for these duplicate records. (Known Issue ID: 108456)
Your association may be affected if you:
Use Memberships
Use Scheduled Payments
Convert Cart To Order When Scheduled the checkbox is unchecked - you can find this checkbox in the Nimble AMS configure page or the Custom Settings.
Original System Design: The system should not capture the payments for the schedules that are duplicates.
Solution: Only Valid schedules are processed, payments are captured, and the cart is successfully converted into an order. Duplicate schedules are identified and run without capturing payments, thereby not deducting money from the Customer’s account. These schedules will remain in the system for the admin to clean up at their convenience.
Module(s) impacted: Memberships, Scheduled Payments
Restrict Deactivating Products Linked to Ongoing Schedules
Currently, the system permits the user to update the product record to 'Inactive' even if the product is part of an ongoing schedule. As a result, when a particular schedule is processed, the processor successfully captures the payment, but no associated records are generated in Nimble AMS. The schedule line is updated to 'Processed,' but no payments, payment lines, or transactions are recorded. (Known Issue ID: 143398)
Your association may be affected if you:
Use Orders
Use Flexible Payments (Schedules and Recurring)
Original System Design: The system should prevent a product record from being set to 'Inactive' if the product is part of an order with an ongoing schedule.
Solution: When the user tries to update the Product’s status to “Inactive“which is linked to the ongoing schedule, do not allow this change and display an error message to help guide the user.
Module(s) impacted: Orders, Flexible Payments (Schedules and Recurring)
Validation Rule to Block Account Name Reparenting on Saved Payment Profiles
The External Payment Profiles record is designed to securely store members' payment information for future use and we do not want the staff users to replace the Account Name on these records for security purposes. We have introduced the validation rule that restricts the staff users to reparent the Account Name. (Known Issue ID: 135958)
Your association may be affected if you:
Use Stored Payment Methods to save your member's payment information
Original System Design: The original design allowed system administrators to override the custom edit form, which led to the use of the standard Salesforce form for External Payment Profiles. This form permitted the editing of critical fields like Account Name, allowing the payment profile to be reassigned to a different member without any restrictions.
Solution: To address this security concern, we implemented a validation rule called AccountChangeNotPermitted. This rule is now active and prevents any changes to the Account Name field on the External Payment Profiles record. If an attempt is made to change the account, the system displays an error message: "Account change is not permitted."
Module(s) impacted: External Payment Profiles, Stored
Correction of Invoice Days Outstanding field calculation for the Fully Paid Orders
The Invoice Days Outstanding field on the Order record is designed to count the number of days an order has remained unpaid since the invoice date. However, even after an order was fully paid, the field continued to increase, leading to inaccurate tracking of payment status. (Known Issue ID: 130443)
Your association may be affected if you:
Order Management System aka Order records
Allow staff users to process unpaid Orders
Allow members to submit Orders without Payment
Original System Design: Our system allowed the Invoice Days Outstanding field to increment daily based on the invoice date, regardless of whether the order was paid or unpaid. This caused the counter to continue even after the full payment was made, resulting in incorrect data for fully paid orders.
Solution: The issue was resolved by updating the logic of the Invoice Days Outstanding field. Now, when an order is fully paid, the counter resets to 0, accurately reflecting that the order has no outstanding balance.
Module(s) impacted: Order Management
Improved Error Handling in Order Processor for Subscription Products
When Association staff used the Order Processor to place orders for Subscription products, an issue occurred if no Subscription products were linked to the selected Financial Entity. The system displayed a technical error message: "Attempt to de-reference a null object. An unexpected error has occurred. Your solution provider has been notified (NU)." This message was not user-friendly and did not offer a clear resolution path. (Known Issue ID: 146931)
Your association may be affected if you:
Use Subscription Products
Use Staff View Order Processor
Original System Design: The Order Processor would attempt to retrieve Subscription products based on the selected Financial Entity. If no Subscription products were linked to the entity, the system generated a technical error message without providing a meaningful explanation or guidance to the user.
Solution: The issue was resolved by updating the error handling mechanism. Now, when no Subscription products are linked to the selected Financial Entity, the system displays a clear and user-friendly message: "There are no subscription products set up for this entity."
Module(s) impacted: Product, Order Management
Send Order Confirmation Emails job updated to clean up stale entries
When using the Order Confirmation Scheduler to schedule the Send Order Confirmation Emails Job, occasionally the Send Order Confirmation Emails Job will be scheduled multiple times. (Known Issue ID: 126059)
Your association may be affected if you:
Use High Volume Email
Original System Design: The Send Order Confirmation Emails job should not be scheduled multiple times.
Solution: Updated logic to automatically detect and clean up stale entries of the Send Order Confirmation Emails job.
Module(s) impacted: High Volume Email
Billing History now includes all Chapter products
When running Billing History Chapter products were skipped if the previous Membership Order had additional Order item lines for the Chapter products. The Chapter product from all is added to the cart and the rest are skipped regardless of the Chapter Affiliation Status. (Known Issue ID: 147049)
Your association may be affected if you:
Use Billing History
Use Chapters
Membership
Original System Design: When running Billing History all the Chapter products should be added to the cart as the items were in the previous Membership regardless of the status (Current/Former/Future).
Solution: Billing History now includes joining Membership Order’s optional Membership products based on the stage mentioned in the MTPL record.
Module(s) impacted: Billing History, Chapters, Membership
Null “Join on date” now populates with a start date for the oldest Membership
Users experienced the error message “System.NullPointerException: Attempt to de-reference a null object” when an Account with a “Join on date” is null and the status is set to Inactive for a Membership type that had already been purchased. (Known Issue ID: 137524)
Your association may be affected if you:
Membership
Original System Design: Users should not experience an error when creating a Cart of a new Membership.
Solution: Updated logic to populate the “Join On date” with the oldest membership start date which avoids the error message.
Module(s) impacted: Membership
Skip the failed Async job & process the newly generated/scheduled Async job
If a failed Async Membership Flow Down job exists in the queue, the newly generated Async Membership Flow Down job will abort until the failure is manually resolved. (Learn More)
Your association may be affected if you:
Use Flow Down
Use Memberships
Use Affiliations
Original System Design: Bypass the failed asynchronous job in the Membership Flow queue and process the newly generated or scheduled asynchronous job.
Solution: A new tag called “Skip Failed Async Membership Flow Down” has been introduced in the Custom Metadata Types. If the staff user turns on this toggle, it skips the failed Async Membership Flow Down job and processes the newly generated or scheduled Async job.
Module(s) impacted: Flow Down, Memberships, Affiliations
Avalara now collects the appropriate Taxes on orders
When an Order is placed, Avalara's Tax calculation code is applied and remains in place until the order is submitted. However, when an existing Order is accessed through a Cart, the Sales Tax calculation field is missing or cleared. This requires the staff users to re-enter and recalculate the Sales Tax to process adjustments and convert the Cart into an Order. (Known Issue ID: 144464)
Your association may be affected if you:
Use Orders
Use Avalara Taxation
Original System Design: Avalara Tax should calculate the correct Taxes on Orders.
Solution: Updated the logic only to consider the product's Tax status (without factoring in the shipping status) when removing Sales Tax from the item.
Module(s) impacted: Orders, Avalara Taxation
Cancel Membership now avoids SOQL error
Some customers, who enabled Mutli-Currency, experienced a SOQL query error when using Cancel Membership and/or Convert Cart to Order features with Orders containing several Membership types that had additional required and optional products such as Donations and Deferred Revenue Method. (Known Issue ID: 143258)
Your association may be affected if you:
Use Cancel Membership
Use Multi-Currency
Use Convert Cart to Order
Original System Design: Enabling Multi-Currency, as well as Membership types with required and optional products should not encounter SOQL query errors.
Solution: Updated logic to avoid multiple SOQL queries when canceling Memberships.
Module(s) impacted: Cancel Membership, Multi-Currency, Convert Cart to Order
Now Credit refund records are linked for accurate reconciliation
When Staff members issue a credit refund on a negative balance for an Order against an account, the resulting 2 payment records are generated but remain unlinked which lacks details on their relationship to each other. Now, the records are linked to each other allowing an accurate reconciliation of the Credits to Credit refund payment methods for a specific Order. (Known Issue ID: 123316)
Your association may be affected if you:
Use Accounting
Use Credit Balance
Original System Design: The resulting payment records should have been linked to providing an appropriate reconciliation of Credits to Credit refunds.
Solution: Updated logic to refund payment populated with previous payment record while refunding through the Credit Refund Payment method.
Module(s) impacted: Accounting, Credit Balance
Accurate Billing History for membership renewals
Clients encountered inaccurate membership renewals while accessing Billing History. This issue stemmed from the account affiliation linked to the Chapter Membership being marked as 'Former," which led to incorrect Billing History for renewals of memberships that had expired or were within the grace period. (Known Issue ID: 138455)
Your association may be affected if you:
Use Chapters
Use Bulk Billing
Use Memberships
Original System Design: Billing History should have reflected the Chapter membership for renewal memberships regardless of the Chapter affiliation status.
Solution: The Billing History now reflects the Chapter membership product from the previous Order that is up for renewal, regardless of whether their Chapter affiliation status is 'Former".
Module(s) impacted: Chapters, Bulk Billing, Memberships
Merge Account Tool now updates Active Child Affiliation counts
When merging duplicate business accounts that both have child affiliations, all affiliations are reparented to the master account, however, the Active Child Affiliation Count field does not update to reflect the new total which includes the reparented children. This results in inaccurate reporting data. (Known Issue ID: 133997)
Your association may be affected if you:
Use Accounts
Use Merge Accounts
Original System Design: The Merge Account tool should have updated the Affiliated Accounts Count field on the Parent Account.
Solution: Now, when two or more duplicate accounts are merged the Primary and Active Affiliated Accounts Count field will update on the Parent Account.
Module(s) impacted: Accounts, Merge Accounts
Now Overpayments equal the summation of the payment lines for Orders
When using Overpayments, if a payment is applied to multiple items in the Cart, the Overpayment is not applied to any item automatically. The Payment will reflect the full payment amount. The Payment Lines will reflect the cost of paying the proper price for the items. The remaining amount of the payment vanishes and is only reflected via the Payment record's Payment Amount. The Payment is recorded as if it occurred, but the Transactions are not generated, leaving the Payment showing incorrect information and Transactions are missing. (Known Issue ID: 131746)
Your association may be affected if you:
Use Overpayments
Use Order Entry
Use Accounting
Original System Design: when using Overpayments the user should not be allowed to make a payment amount that is not equal to the summation of the payment lines.
Solution: Added validation when allowing Overpayments that the Cart's payment lines are equal to the total payment entered for the Cart.
Module(s) impacted: Accounting, Overpayments, Order Entry
Deferred Revenue Recognition 'Summarized' and 'Detail' reflect edited Order Transactions
Switching the Deferred Revenue Recognition configuration from the 'Summarized' to the 'Detail' view on the installed packages page can cause existing Orders with Deferred Revenue on the same Scheduled to fail. This prevents Transactions from being created and leaves the Order in a broken state. No error message displays for this issue. Reverting to the 'Summarized' view resolves the issue and eliminates the errors. (Known Issue ID: 145590)
Your association may be affected if you:
Use Accounting
Use deferred Revenue
Original System Design: Viewing the Deferred Revenue Recognition as 'Summarized' or 'Detail' should not prevent Transactions when editing Orders.
Solution: Now, Transactions are created when editing the same Order.
Module(s) impacted: Accounting, Deferred Revenue
Only Active events will be included in the nightly batch job for CalculateEventRevenue
The Salesforce governor limit is exceeded when the CalculateEventRevenue nightly batch job is executed for each Event record in the system with a batch size of one. This process can utilize a significant portion of the allowed maximum number of asynchronous Apex method executions within 24 hours. (Known Issue ID: 143238)
Your association may be affected if you:
Use Events
Original System Design: The CalculateEventRevenue nightly batch job should process only Events with a status of 'Active'.
Solution: Updated the CalcuateEventRevenue nightly batch job to process only Events with the status 'Active' during batch execution.
Module(s) impacted: Events
Able to successfully complete partial refunds in Community Hub
Previously, partial refunds in Community Hub were processed as full refunds when the Queue Process Object permission was removed from the Community Hub Logged-In User profile.
When an Order is processed and the respective payment is settled on the payment gateway, modify the Registration via the My Registration page and remove one product from the Order. Upon proceeding through the checkout process users would receive the following error, "Sorry, we are unable to process this refund. Please contact staff to complete the transaction, (NC)", however, contrary to the message, the entire payment gets refunded in the payment processor instead. (Known Issue ID: 137704)
Your association may be affected if you:
Use BluePay
Use Registration modifications
Use My Registration page
Original System Design: The Community Hube Logged-In User profile should successfully process a partial refund.
Solution: Removed the Queue Process Object permissions requirements on the Community Hub Logged-In User profile.
Module(s) impacted: BluePay, Registration modifications, My Registration page
Event Registration counts are now updated on demand
Event Registration counts were not kept up to date, which resulted in the Event allowing more users to register than should be allowed. (Known Issue ID: 125315)
Your association may be affected if you:
Use Events
Use Event Registration
Original System Design: Event Registration counts should be updated on demand.
Solution: Updated the logic to provide a manual launch for the EventRegistrationCountUpdater job when triggered by the anonymous apex.
Module(s) impacted: Events, Event Registration
The 'Remember Order Batch' setting keeps selection
Clients using the 'Remember Order Batch' package setting have encountered an issue requiring them to manually set the selected payment batch for each payment entry. In the past, the Batch field would automatically be set to the default value. (Known Issue ID: 144335)
Your association may be affected if you:
Use Orders
Use Batches
Original System Design: The 'Remember Order Batch' setting should keep the batch selection for each payment entry.
Solution: Removed an unnecessary check which now keeps the last Batch selection for payment entry.
Module(s) impacted: Orders, Batches
Child Affiliation record deletes successfully
When a user attempts to delete a Child Affiliation record for a specific organization from the Manage Roster page, the record is not deleted, yet a success message is displayed. (Known Issue ID: 144814)
Your association may be affected if you:
Use Accounts
Use the Manage Roster page
Original System Design: Deleting the Child Affiliation record for a specific organization from the Manage Roster page will remove the record accordingly.
Solution: Updated logic to set the removal reason as null when the affiliation status changes to active.
Module(s) impacted: Accounts, Manage roster page
$0 payments no longer generate an additional payment record
In the BluePay gateway, an additional $0 payment record was generated for Orders containing two items: one paid from the Staff View and the other through Express Payment in the Community Hub. Furthermore, the order summary page in the Community Hub failed to display the correct credit card issuer information. This issue of an extra $0 payment record also occurred in the Experience Cloud Community Hub when a user modified a processed order by adding a product and completing the payment using the Experience Cloud checkout URL. (Known Issue ID: 133726)
Your association may be affected if you:
Use Express Payment
Use BluePay
Original System Design: Additional payment records should not be generated when Orders are placed and processed.
Solution: Added a check to skip payment line creation if the calculated payment amount is $0.
Module(s) impacted: Express Payment, BluePay
Cancel Mid-Term Membership module displays End Date correctly
When an end user Cancel Mid-Term Membership the End Date field displays a date that is not the end of the month date, although the field description is ‘The end date is the last day of the selected month.’ This confuses the end user. (Known Issue ID: 138513)
Your association may be affected if you:
Use Cancel Mid-Term Membership
Original System Design: The End Date field of the Cancel Mid-Term Membership module should display the last day of the selected month.
Solution: Updated logic to use UTC methods for setting and displaying the last day of the selected month accurately.
Module(s) impacted: Cancel Mid-Term Membership
Updated and corrected the Unit Price and Quantity fields for all product type history records
Previously, the Unit Price field would fetch its value from the External Unit Price field, and if the External Unit Price field were empty, the Unit Price field would also be zero. The same applied to the Quantity and External Quantity fields. (Known Issue ID: 134861)
Your association may be affected if you:
Use Orders
Original System Design: If the external fields are empty, the Unit Price and Quantity fields should fetch the value from the Order Item Line linked to the history record.
Solution: Updated formula for the Unit Price and Quantity fields for product types such as Advertisement, Coupon, Donation, Exhibit, Membership, Merchandise, Miscellaneous, Sponsorships, and Subscription. If the external fields are empty, the Unit Price and Quantity fields should retrieve the value from the Order Item Lines. If the Order Item Line field is also empty, then the Unit Price and Quantity fields should display the value $0.
Module(s) impacted: Orders
Failure emails reduced
Daily failure emails were sent to admin users when the BatchTotalUpdater job ran, trying to process records but did not have records in the queue for processing. (Known Issue ID: 143672)
Your association may be affected if you:
Use Accounting
Use Batches
Original System Design: If the BatchTotalUpdater job should run without any queued process records to handle, it will fail and send a failure notification email to the admin users.
Solution: Now a null check is incorporated for the BatchTotalCalculator when no queue process records are handled in this job.
Module(s) impacted: Accounting, Batches
The purpose field on a Cart now resets
When all the products are deleted from a Cart and a new type of product is added, the Purpose field does not reset. This results in the field being populated incorrectly. (Known Issue ID: 101437)
Your association may be affected if you:
Use Order Entry
Use Orders & Orders Process
Original System Design: The Purpose field on a Cart should reset when all the items in the Cart are deleted and new products are added.
Solution: Now, the Purpose field will update to reflect the product type of the newly added items.
Module(s) impacted: Order Entry, Orders & Orders Process
Correct Status Display for Canceled Advertisement, Exhibit, and Sponsorship Orders
When orders with product types such as Advertisement, Exhibit, and Sponsorship are canceled, the status field on the history record incorrectly displays them as Active. This is due to a formula in the NU_Status_c field that relies on the External ID field having a value. As a result, reporting inaccuracies occur, with canceled orders appearing active. (Known Issue ID: 143255)
Your association may be affected if you:
Place Orders against the Advertisement, Exhibit, and Sponsorships product types.
Original System Design: When an order is canceled for any of the product types (Advertisement, Exhibit, and Sponsorship), the status on the history record should be updated to "Canceled."
Solution: We have corrected the NU_Status_c formula field logic to display the right status when the Order is canceled for Advertisement, Exhibit, and Sponsorship product types. This change ensures consistency and eliminates errors on Advertisement, Exhibit, and Sponsorship sObjects.
Module(s) impacted: Custom Reporting, Custom Flows, or any customizations that involve the Status field from Advertisement, Exhibit, and Sponsorship product types.
Community Hub
What's New?
Enhancement: Introducing the Ability to Exclude Organization Accounts from My Affiliation Search
We’ve added the “Exclude From Affiliation Search” field to the Organization/Company Account layout, allowing Association staff to prevent certain accounts from appearing in the My Affiliation search results within the Community Hub. This update helps reduce clutter and improve the accuracy of search results by hiding irrelevant organization accounts, such as those created for special programs or testing purposes, from member view. This enhancement streamlines the affiliation process, ensuring members can more easily find and connect with the appropriate organizations. (Learn More)
Your association may be affected if you:
Use Affiliations in Community Hub
Use Accounts
Defects Fixed
Purchasing Registration Orders with a Coupon is now error-free
In Community Hub, some clients received the error message 'Too many SOQL queries' when purchasing a Registration Order with a Coupon while Multi-currency was enabled for the org. However, the same Order with a Coupon in Staff View was processed without error. (Known Issue ID: 147874)
Your association may be affected if you:
Use Events
Use the Community Hub Dynamic Checkout page
Enable Multi-currency
Original System Design: The Registration Order with a Coupon should have been processed without error.
Solution: Now, when a Registration Order with a Coupon is purchased, users will no longer encounter the 'Too many SOQL queries' error.
Module(s) impacted: Events, Community Hub Dynamic Checkout page, Multi-currency
Community Hub Flow Cards respect the container
Community Hub users noticed fields on the Community Hub Flow Cards extending beyond the field container. This impacted fields Input, Select, Table, and Text. (Known Issue ID: 141460)
Your association may be affected if you:
Use Community Hub
Use Community Hub Flow Cards
Original System Design: The Community Hub Flow Cards should not overflow past the field.
Solution: Updated the .container styles to core.css and boldcore.css to ensure container elements maintain field width.
Module(s) impacted: Community Hub, Community Hub Flow Cards
Load More functionality on the Chapter Directory displays more than 20 affiliations
The Chapter Directory component in the Chapter Portal does not display more than 20 affiliations although a loading icon displays at the bottom of the page. (Known Issue ID: 146893)
Your association may be affected if you:
Use Chapters
Use Chapters Portal
Original System Design: The Chapter Directory should load more affiliations as the user scrolls to the bottom of the page.
Solution: The Load More functionality increases the accounts when scrolling down to the bottom of the page.
Module(s) impacted: Chapters, Chapters Portal
Event Registrations can be updated to a different account
Some Community Hub users received a null de-reference error message when utilizing the search input from the Manage Registration page to select a different account. This occurred when the manage Registration page is set to use the Choose A Colleague2 Card type. (Known Issue ID: 139374)
This issue impacted active implementations only.
Your association may be affected if you:
Use Community Hub
Use the Community Hub Card
Use Events
Use registrations
Original System Design: The Choose A Colleague2 Card type should have allowed for the updates to the event registration.
Solution: Added logic to check if the radio button on Choose A Collesgue2 Card contains an account before switching the selected value.
Module(s) impacted: Community Hub, Community Hub Card, Events, Registrations
Now account records and User records sync appropriately
The Populated checkbox values on the account record that are configured to sync to the User record, were cleared out on the account records due to the sync. This happens when the User record is manually created, or the User record is created during the password reset process, however, if the User record and the account record both exist, the fields remain synced if checked/edited as well as during the nightly sync job. (Known Issue ID: 105595)
This issue impacted active implementations only.
Your association may be affected if you:
Use Accounts
Use Community Hub Setup
Original System Design: The account record should have maintained the data or updated the data from the sync with that User record.
Solution: Added conditions to handle the checkbox field values appropriately during the sync.
Module(s) impacted: Accounts, Community Hub Setup
Nimble Communities
What's new?
See our latest enhancements on the (Win25) Major Features page.
Defects Fixed
Community Hub Logged-in Users can access the Add Group Member Action
Community Hub automations employing the Add Group Members Action encountered an INSUFFICIENT_ACCESS_ON_CROSS_REFERENCE_ENTITY error when initiated within Community Hub yet executed without issue when activated from Staff View. This action is integrated into a record-triggered flow to include an individual in a group. It is utilized inflows related to Accounts, Registration, Membership, Committee Membership, and Events. (Known Issue ID: 138843)
Your association may be affected if you:
Use Nimble Communities
Use Community Hub
Use Community Hub Logged-In User
Original System Design: Community Hub Logged-In Users should not receive an INSUFFICIENT ACCESS error when using Add Group Member Action.
Solution: Now, Community Hub Logged-In Users will not experience an INSUFFICIENT ACCESS error when using the ADD Group Member Action.
Module(s) impacted: Nimble Communities, Community Hub, Community Hub Logged-In User
SynchedLearning API
What's new?
See our latest enhancements on the (Win25) Major Features page.
Defects Fixed
The LMS Completion Date field automatically updates upon course completion
Upon completing a course in Freeston, the LMS Completion Date field failed to update. (Known Issue ID: 145012)
Your association may be affected if you:
Use SynchedLearning API
Original System Design: The Date-type data field, such as the Completion Date field should have been updated once the freestone course was completed.
Solution: The Completion Date field now updates upon the completion of a course.
Module(s) impacted: SynchedLearning API
Programs
What's new?
See our latest enhancements on the (Win25) Major Features page.
Defects Fixed
Customer Community Plus license user permissions updated
In Community Hub users with a Customer Community Plus license (CCP) received an error message, "Insufficient access rights on cross-reference ID," when trying to enroll in a Program from the My Program page. (Known Issue ID: 147116)
Your association may be affected if you:
Use Programs
Have a Customer Community Plus license (CCP)
Original System Design: The Customer Community Plus license user should have permission to enroll in programs.
Solution: Now, Community Hub users with a CCP license can submit Orders for programs.
Module(s) impacted: Programs
The program's endDate field now updates
Once a Program order is submitted and the endDateOverride field on the Program record is populated, the endDate field value should update to match the endDateOverride field. However, the endDate field did not update when the Program record endDateOverride field was populated. (Known Issue ID: 104946)
Your association may be affected if you:
Use Programs
Original System Design: The endDate field should update when the endDateOverride field is populated.
Solution: Adjusted logic to update the Program record's endDate field to the endDateOverride field when the values of these fields are different.
Module(s) impacted: Programs
Milestone components now calculate "Total Units Earned"
In Community Hub on the My Components page, the milestone "Total Units Earned" field did not calculate properly as all component statuses, such as Pending, Rejected, and Approved were included. (Known Issue ID: 105359)
Your association may be affected if you:
Use Programs
Original System Design: The "Total Units Earned" field should have calculated for the Approved components rather than components with a status of Approved, Pending, and Rejected.
Solution: Now, the "Total Units Earned" field calculates for components with an Approved status.
Module(s) impacted: Programs