When a user on the online 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). This action is known as an activity and the Higher Logic online community platform is full of these triggers which record and send back these activities.
Activity sync in Nimble AMS requires an object to handle the writeback of all selected activities. Higher Logic leverages the Salesforce SOAP API to create XML statements and writes them to a table with a specified schema:
- WhoId (Salesforce's unique 18-digit identifier)
- ActivityDate (date time that the activity was triggered on Higher Logic)
- Type (the unique writeback code given to Higher Logic for each kind of activity)
- Description (a specific format on how the information for the activity is displayed.
To create a custom object in which to store Activity Sync data, follow the rest of this documentation to completion.
Activity sync is configured on a batch schedule that aligns with the periodic sync. 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. 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 Setup, go to App Setup -> Create -> Objects
- Select "New Custom Object" at the top of the view.
- Enter a "Label" and "Plural Label" following the format below and check "Allow Reports" in "Optional Features"
- Add four custom fields with the following data types. Note how it matches the schema discussed in the previous section.
- "Activity Date" (Date/Time)
- "Activity Type" (Text(255))
- "Contact Id" (Lookup(Account ))
- "Description" (Long Text Area)