12/27/2023 0 Comments Nimble ams renewal billing logo![]() They were also getting charged in the payment processor, but no payment was recorded in Nimble AMS, due to the error. Please contact support’, when they entered a value in the name field that exceeded fifty characters. Module(s) affected: Cancel Membership Mid-Term, Membership OrderĬommunity Hub (CH) users are now limited to 50 characters when entering Card Holder Name field for a new Credit Card.Ĭommunity Hub (CH) users encountered an error stating: ‘Something has gone wrong. Solution: Modified the system to identify the total number of transactions generated and replace the reference group numbers with the correctly generated numbers. Original System Design: When staff use 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). Place a Membership Order from Staff View.Sometimes the reference group number that represents a canceled transaction appears as ‘0’ when the Cancel Membership Mid-Term feature is used. Reference Group Number for transactions from Cancel Membership Mid-Term now generates correctly. ![]() Module(s) affected: CH shopping cart, Payment Solution: Optimized query to remove a redundant query when processing carts without previous orders. Original System Design: CH users should be able to process membership renewal payment via Express Pay or other Hosted Payment form without extreme delay or timeout error. Use Express Payment to renew membership.Made minor improvement to enhance Community Hub (CH) speed performance so payment process will now only process CH shopping carts with orders.Ĭommunity Hub (CH) users encountered slowness and error: ‘Time limit exceeded…’ when they attempt to process membership renewal via Express Payment and Hosted Payment. Module(s) affected: Order Processor, Accounting, Taxation, External Taxation For transactions that are not in a locked state in Avalara, staff users can make adjustments in Nimble AMS the same as before. Staff can then make the necessary adjustments in Avalara and update the External Taxation Status of the order in Nimble AMS to “Successful”. 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”. 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. That order could not be adjusted 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. Use Avalara Taxation to file your tax returns.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. Nimble AMS Staff View Defects Fixed Updated Nimble AMS Order Processor to verify Avalara’s transaction status (locked or unlocked).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |