![]() ![]() 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. Use or have members who use credit cards with Stored Payment Method.Module(s) impacted: Cancel Order Credit card refunds for payments made through Stored Payment Method (Bluepay Gateway) are now supported.Īssociations encountered an error when they try to process a credit card refund for transactions whose initial payment was made through Stored Payment Method. Solution: Batch schedule line processing runs more efficiently and uses fewer SOQL queries, reducing failures when schedule lines error due to canceled orders. Original System Design: Cancelling an order, should only cancel the job related to that order. Cancel order(s) in Staff View or Community Hub.Module(s) impacted: Nimble AMS SynchedLearning API Improvements to Batch schedule line processing.Ĭancellation of order during schedule processing caused unrelated records in a batch to fail. Solution: Added a new parameter to filter LMS purchase data by Customer ID. Original System Design: LMS Systems should be able to narrow down customers’ LMS purchase data, by using the newly introduced Customer ID filter. Previously, LMS systems using the SynchedLearning API's purchases endpoint were not able to narrow down LMS purchase data by a specific customer. Module(s) impacted: Nimble AMS SynchedLearning API Introduced a new filter, Customer ID, to the Nimble AMS SynchedLearning API’s Purchases endpoint. 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. 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. ![]() 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. Additional LMS Purchase endpoint information has been added for the Nimble AMS SynchedLearning API. Read more about the new Re-Instate fields and Renewal Cart Deletion Job on Membership Types. Module(s) impacted: Community Hub Cart, Membership Renewal, Memberships, Order EntryĪction Required: To implement the Renewal Cart Deletion Job in your org, please Contact Support for assistance. 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. 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. ![]() 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).
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |