Periodic Refresh

Every 30 minutes, Higher Logic calls the stored procedure hlGetChangedMembers to return a list of changed users. The procedure targets several tables within iMIS, such as Activity, Orders, and Name.

• Activity offers transaction dates for purchasing products within the iMIS system, such as membership packages and committee memberships.
• The Name table offers a LastUpdated field to query based on any changes to the user profile within iMIS.
• Orders represents the current outstanding memberships to the various iMIS modules, such as committees and chapters. Each of these objects encompass many of the various actions that would need to be factored within the stored procedure. The default stored procedure covers the basic SQL that is provided for the iMIS integration.

For any customized logic that is added and that exceeds the scope of the basic SQL stored procedures and views, corresponding logic must be added to the periodic refresh and the existing criteria needs to be updated to encompass the new customized logic. Below is a sample format for adding customized logic to this stored procedure.

SELECT {iMIS ID} AS MemberKey, {Datetime Field} AS LastUpdated
FROM {Table with Datetime Field}
WHERE {Datetime Field} >= @ChangedSince

• The SELECT statement must return the iMIS ID and the datetime field for when a change has happened.
• The FROM statement needs to target the database table that houses the iMIS ID and the datetime field.
• The WHERE statement must use that datetime field relative to the ChangedSince variable. That variable is the date and time that Higher Logic is sending over with each periodic refresh.

Custom Demographics

Base information for a user includes first name, last name, phone numbers. This information comes from the hlGetMemberDetails stored procedure. The logic provided can be modified, but the schema must remain the same.

hlGetMemberDetails

Community Groups

hlMemberCommunityGroups

NOTE: Fields in bold text are required.

Assume a test user with an iMIS ID of 10000 and the current date is 01/01/2019.

SELECT *
FROM hlMemberCommunityGroups
WHERE MemberKey = '10000'

Running the above SQL query displays all community memberships that will be returned to Higher Logic for the test user. Here’s a sample output with some important scenarios to be aware of. Any columns that are left out are assumed to be NULL or are not relevant in this example.

User 10000 will be added to one community in Higher Logic. Community memberships with invalid date ranges (e.g., a BeginDate in the future or an EndDate in the past) are excluded. The memberships to "Test Community 2" and "Test Chapter" are invalid because the values of BeginDate and EndDate are invalid. The first membership is valid, so User 10000 will appear in the roster of the "Test Community 1" integrated community with a unique identifier of TEST-COMM between the BeginDate and EndDate returned by the view.

Security Groups

hlMemberSecurityGroups

NOTE: Fields in bold text are required.

The same idea applies to this example. The integration filters for invalid date ranges when applying security group memberships. The SQL query is also similar:

SELECT *
FROM hlMemberCommunityGroups
WHERE MemberKey = '10000'

Events

The schema for what constitutes an event in Higher Logic is within the API Bridge. Higher Logic pulls all iMIS data from the iMIS event table, MEET_MASTER. The API Bridge will transform the data into the schema below. This schema is normally not modified.

Event Schema

NOTE: Fields in bold text are required.

Every event can have mini-events that are called event sessions. For example, Higher Logic Super Forum represents the main event. The many breakout sessions (speaker presentations, consulting sessions) that happen during Super Forum are the event sessions. In iMIS they are called event functions. Higher Logic performs a lookup on all event functions/sessions in the PRODUCT and PRODUCT_FUNCTION SQL tables using the iMIS MEETING field or the LegacyEventKey. Sessions are created the same way as events. The schema below is not modified.

Event Session Schema

NOTE: Fields in bold text are required.

Related articles

The following articles have supporting information for the iMIS integration.

• iMIS Integration: Higher Logic API Bridge Methods
• iMIS Integration FAQs