(AMS-12681) Coupon now discounts a single product in a mixed order This is now fixed, and the registration counts are updated successfully. This allowed additional users to register for the event although max registrations were met. Registration Counts for events were not updating correctly when the Sync with LMS checkbox on event record was selected. (AMS-12653) Registration Counts for events made correct We have fixed this and the Transaction Date of the manually selected batch is respected when payment is created from the One Payment Wizard. This resulted in the Transaction Date for all of the payment transactions being set to the current date (instead of the batch date). When a user made a payment using the One Payment Wizard by selecting a batch (from a date other than today), the system ignored the batch date. (AMS-12683) One Payment Wizard now respects the Transaction Date of a Manual batch This is fixed and now the event badge will remain linked to the event registration while using coupons. In some instances, when editing the event badge, the badge became linked to the coupon rather than the event registration making it inaccessible to the registration process. (AMS-12633, NC-6234) Event badge now stays linked to the event registration record when using coupons Before this defect fix, it was possible to delete the carts with Credit card hosted payments, which was causing inconsistencies with payment entries on the BluePay payment gateway. (AMS-12638) Carts with hosted credit card as payment can no longer be deletedĬarts using Credit Card hosted payments are now prevented from deletion. (AMS-12632) The 'Is Shippable ' checkbox on the Order Item Line no longer turns to false after an express paymentĭue to a defect, the Is Shippable checkbox on the Order Item Line record was changing to false after orders were paid through an Express Payment. Deferred Forecast Detail records are now sorted by the Transaction Date and the newest record is at the bottom. Even though this was visible on the screen and did not affect the function of the software, it could have appeared like the Deferred Schedules weren’t processing appropriately. In some instances, a Deferred Forecast Detail of a Deferred Schedule sorted out of order. (AMS-12602) The Deferred Forecast Detail is now sorting correctly Users can now cancel their membership in the current month and consecutive months. When users attempted to cancel a membership with the End Date in the current month by using the Manage Membership LWC, an error generated. Note how it matches the schema discussed in the previous section.Membership cancellation is now possible in the current month Add four custom fields with the following data types.Enter a "Label" and "Plural Label" following the format below and check "Allow Reports" in "Optional Features".Select "New Custom Object" at the top of the view. In Setup, go to App Setup -> Create -> Objects.Only 200 activities can be sent in one API call so if the number of activities exceeds that, more API calls will be needed to send each set of activities. In every periodic sync iteration, Higher Logic will gather all the activities that have been triggered in the current 30-minute period and send them in one or more API calls. To create a custom object in which to store Activity Sync data, follow the rest of this documentation to completion.Īctivity sync is configured on a batch schedule that aligns with the periodic sync. Description (a specific format on how the information for the activity is displayed.Type (the unique writeback code given to Higher Logic for each kind of activity).ActivityDate (date time that the activity was triggered on Higher Logic).WhoId (Salesforce's unique 18-digit identifier).Higher Logic leverages the Salesforce SOAP API to create XML statements and writes them to a table with a specified schema: This action is known as an activity and Thrive Community is full of these triggers which record and send back these activities.Īctivity sync in Nimble AMS requires an object to handle the writeback of all selected activities. When a user in Higher Logic Thrive Community (Thrive Community) triggers an action like updating their profile or subscribing to a community, the action is packaged with relevant information like the time stamp and which user performed the action and sent back to the AMS/CRM (in this case, Nimble AMS).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |