Summer '24 Maintenance Release Changelog
This is a list of every change made in the Summer '24 Maintenance Release of Nimble AMS.
Nimble AMS Staff View
What's new?
An orange status flag now signifies a Membership in the Grace period.
On the membership record, both Memberships with a Grace period and a Current period displayed a status flag in green color. (Learn More)
Your association may be affected if you:
Use Memberships
- Use Accounts
Original System Design: Memberships within a Grace period or the Current period should have a status flag of a different color.
Solution: Now Memberships are in a Grace period indicating the status flag in orange color.
Module(s) impacted: Memberships, Accounts
Staff users can skip the mandatory question while processing the Event Registration order.
Previously, staff members were required to respond to a question when processing an Event Registration order through the staff view. (Learn More)
Your association may be affected if you:
Use Events
- Use Registrations
Original System Design: Allow staff users to override Event questions while placing Event Registration orders from the Staff View Order Processor.
Solution: The "Optional For Staff" field has been added to the EventQuestion__c SObject. If the staff user marked the checkbox checked, then the question marked "Required" will be optional for staff users when processing Event-related orders in the staff view Order Processor.
Module(s) impacted: Events, Registrations
The product type history record page displays the 'Order' field as an Order number.
Earlier, when staff members needed to access or manage the order records, they frequently had to navigate through multiple layers, starting from the Order Item Lines to the Order Item, and then to the order itself, to find the necessary information. This process can be time-consuming. (Learn More)
Your association may be affected if you:
Use Orders
Original System Design: It should be able to redirect staff users from the product type history record page to the Order detail record page.
Solution: The 'Order' field has been added to the Product type Layout which displays the ID of the Order associated with the product's purchase. The 'Order' field is displayed for product types such as Advertisement, Donation, Exhibit, Membership, Merchandise, Miscellaneous, Registration, Sponsorships, and Subscriptions.
Module(s) impacted: Orders
Now staff members can process refunds from posted batches.
If a prepayment was partially applied and the associated batches have been posted, a staff member receives an error "Payments can only be modified if the batch is open" when attempting to refund the payment remaining balance. (Learn More)
Your association may be affected if you:
Use Batch
- Use Prepayments
Original System Design: Staff users can refund the available credit balance by choosing any open batch from an existing prepayment record for the same member who made the initial prepayment.
Solution: The logic has been updated to process refunds from post batches using pre-payment functionality.
Module(s) impacted: Batch, Prepayments
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
Payments from Active cart items can be transferred to Canceled Cart items.
When transferring funds between active and canceled items, the system sometimes processes transactions twice, leading to double payments or double refunds. This creates an outstanding balance on the canceled item, which the Order Wizard cannot resolve. Correcting this issue requires manual intervention to adjust payment records, which is inefficient and prone to error. Despite the issue, the overall order balance shows $0, whereas the order is considered fully paid or refunded. (Learn More)
Your association may be affected if you:
Use Orders
Use Payment Transfers
Original System Design: The system should allow staff users to seamlessly transfer payments from canceled Cart items to active Cart items.
Solution: Updated logic to transfer the payment from active cart items to canceled Cart items with balances.
Module(s) impacted: Orders, Payment Transfers
Now Staff users can exclude the optional membership products from the Bulk Billing process.
During the Bulk Billing process, optional membership products are by default included in the new Billing History, creating carts for the account. And if staff users wish to exclude items, they must edit the cart. This has been time-consuming for staff who want to remove specific products. (Learn More)
Your association may be affected if you:
Use Membership Types
Use Membership Type Product Links
- Use Bulk Billing
Original System Design: Staff users should be able to exclude the optional membership products while running the Bulk Billing process from the MTPL.
Solution: The "Exclude from Billing" field has been added to the MTPL layout.
Module(s) impacted: Membership Types, Membership Type Product Links, Bulk Billing
Defects Fixed
BluePay refunds are now error-free.
During the time period of June 18, 2024, and July 15, 2024. refunds through BluePay failed with the error message "cannot VOID a CAPTURED AUTH (void the CAPTURE instead). (Known Issue ID: 146321)
Your association may be affected if you:
Use BluePay
- Use refunds
- Have Payments placed during 6/18/2024 through 7/15/2024
Original System Design: During the refund the TransactionID should have updated to the original TransactionID.
Solution: Updated logic to use the original TransactionID on capture response only if the TransactionID is null/not set. Then ran a script to clean up data for payment records during the above timeframe.
Module(s) impacted: BluePay
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 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 the 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 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 did 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 cancelled 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?
Now Staff users can exclude the Organization Account from the My Affiliation Search functionality
Some organization has a special program with certain organization records that are not intended to be used for affiliation purposes by our members. These organization accounts are currently included in the Community Hub My Affiliations search, which causes clutter and makes it difficult for users to find relevant affiliations. (Learn More)
Your association may be affected if you:
Use Affiliations
- Use Accounts
Original System Design: Organization accounts not intended for affiliation purposes, should not be searchable.
Solution: “Exclude From Affiliation Search” Account SObject’s field should be placed on the Organization/Company Account Layout.
Module(s) impacted: Affiliations, Accounts
Defects Fixed
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)
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 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