Bug Fixes
Session Attendees: Mobile Check-in app users can check in Session Attendees as expected. Previously, when users tried to check in Session Attendees, the app slowed down when clicking the QR code scanner or froze when manually checking in Session Attendees. (Known Issue: 000004062)
Create an Attendee: Users can no longer create an Attendee using an invalid email address, such as one with Dotless Domain Names. Previously, entering an invalid email address caused the sync between the Mobile Check-in app and Salesforce to fail. Note: As of August 2013, the ICANN Board New gTLD Program Committee (NGPC) adopted a resolution affirming that "dotless domain names" are prohibited. Dotless domain names contain a single label (e.g., http://example, or mail@example).
Attendee List: If a user scrolls down to the bottom of the Attendee List for an Event, they can see the last Attendee’s status. Previously, the user could not see the status of the last Attendee.
External IDs
The correct Attendee will be selected when checking in an Attendee with a BT External ID. The matching logic was updated to find the Attendee using their contactId instead of their email address. Previously, the wrong Attendee was sometimes selected when multiple Attendees used the same email.
When using a Contact’s BT External ID to create a QR code and then checking in that person using the Mobile Check-in app, the existing Contact record will be related to the new Attendee record. Previously, a duplicate Contact record was created without the BT External ID value and related to the new Attendee record.
Offline Mode
Mobile Check-in app users can create a new Attendee when the app is offline. Previously, the Mobile Check-in app froze when a user tried to create an Attendee when the app was offline. NOTE: If an Event that wasn’t previously opened in online mode is now opened in offline mode, a list of Attendees won’t be visible. The list is empty because the app can’t fetch data from Salesforce when offline.
If the offline mode is enabled and a user forces the app to close, the user can still use the app in offline mode. Previously, the offline mode was disabled when a user forced the app to close.
Attendees created in offline mode will be added to the correct Event when offline mode is disabled and the app syncs to Salesforce. Previously, if the user switched to a different Event while the sync was running, the new Attendees were added to the second Event instead of the first one. To prevent this from occurring, users can no longer switch between Events while the sync process is running.
Enhancement
If a Mobile Check-in app user cannot add a new Attendee when offline, they will see the following error message. “Attendee creation failed; please try again. Cannot read properties of null (reading ‘push’)”