Hubb Integration

Credentials

The following credentials are always required:

- EventID

- Scope

- clientId

- Secret

Do NOT edit twoWayEndPoint

Data types

Participants, Presenters, Sessions, Sponsors, Registrations

2-way sync for Registrations

2-way registration

2-way registration means that when the user tries to register in the app to a session by clicking on the 'Register' button, our system confirms with the provider if we can register the specific user to the specific session.

Based on the response we get from the provider the user is registered or not to the session.

The best way to test is to confirm with the client which user can be used for testing and then register to a session

How to configure

Credentials

Go to the API Data module > API Credentials. Click on "Hubb [UPDATE ME]".

The credentials fields to update are pre-configured: just add the credentials you have received from the provider.

Then go to Preview to check if the credentials are working (please refer to the generic Integration engine page).

Concurrent Sessions

It is possible to automatically add master sessions for concurrent sessions that have the same start time. For creating concurrent sessions on the next sync, you need to:

1. Map the `in_slot` field coming from Hubb to our own in_slot field:

2. In the API Credentials, enter a new setting called `ConcurrentSessionsTitle` and set the desired title for the master sessions:

Session registration

We support the waitlist for session registration, if in use.

Remove outdated data

• For participants: TO BE CONFIRMED

If a participant is marked as "Cancelled" or "Declined" on the client's side, it will be imported in Backstage with status "cancelled".

If the client intends to remove completely some participants data on their side, you need to make sure to tick the "Remove outdated data" box in API Data -> Data Configs -> Participants:

Upon next sync, the items deleted on the client's side will be removed from Backstage.

• For sessions: TO BE CONFIRMED

If a session is marked as "Inactive" on the client's side, it will be imported in Backstage as "Hidden" and will not appear in the agenda.

If the client intends to remove completely some sessions on their side, you need to make sure to tick the "Remove outdated data" box in API Data -> Data Configs -> Sessions.

• For sessions registrations: TO BE CONFIRMED

If a participant is registered for a session on the client's side (status "registered" in Sessions registrations preview), they will be synced in Backstage as registered for this session

If a participant is unregistered for a session on the client's side (status "unregistered" in Sessions registrations preview), they will be synced in Backstage as not registered for this session

If the client intends to remove completely some sessions registration on their side, you need to make sure to tick the "Remove outdated data" box in API Data -> Data Configs -> Sessions registrations.

Mapping

Do not change the mapping for fp_ext_id and fp_status!

New Agenda

This API integration is compatible with the new agenda (version > 3.0.0), 2 additional configs are necessary, Hubb Sync Tags and Hubb Sync Locations.

In case you don't need to add one of those, you can freely remove them from the credentials.