Release Notes Visit 5.1

Rules

Rules created within forms can now be saved and used at Event Level.  
When a new rule is added to a form, the user now has the option to save the rule at event level to reuse it if needed. 

UTM codes

For marketing purposes, the below UTM codes are now captured by Visit and made available in the registrant export file and via the API. 

• utm_source 
• utm_medium 
• utm_campaign 
• utm_term 
• utm_content 

Documents

We’ve added the option to set A4 and letter documents’ orientation to landscape.  

Digital badges are now available in an embeddable HTML format. 

Age Validation

We’ve added a new validation field of age check to group registration information. Age check should be valid on the date of the show (not the date of registration). 

To enable this, go to Event > Setup > Options and enter the required minimum age.

VAT Validation

We’ve added the option for VAT numbers to be checked and validated against an official VAT codes database – vatlayer. To benefit from this option, you need to create an account on vatlayer.com. 

New PSP

We’ve added Ingenico PSP to the list of direct payment integrations available in Visit. 

Team

For organisers who wish to synchronise data via the API, we have added the option to disable the add/edit Staff feature, which will remove the options to add, remove or edit staff for admins. This will also prevent admins from registering themselves as staff.

We have disabled the Delete Staff function in Visit Connect. This is to prevent QR codes from changing multiple times and the lack of control over deleted data for organisers. From now on, all requests for removing team members or changing their registration type must be addressed to visit.support@ges.com.

Improvements

• Licence QR codes – We have made the licence QR codes available for both Web App and Native App within Teams > Action in Visit Connect. Note that for the Web App, the QR code is for Scan only mode. Admins can also see each individual member’s licence QR code when they select their name from the Team list.
• Embedded Mode – To better serve its purpose, we have simplified the embedded mode (used when integrating Visit Connect into third-party apps) to only show the Leads list and the Scan lead options. 
• Improved access to Visit Connect from another device – Users will receive a QR code that they can scan with a different device – smartphone or tablet – if that’s the one they wish to use the app on.
• Improved UI in Setup Mode  – Users get a message notifying them that they are in setup mode and thus they cannot scan leads, and we have also added an icon that opens a pop-up with a message warning them that they are in Setup mode and that they need to switch to Staff mode to be able to scan leads.
• Improved UI for leads not synced – We have added a prompt to warn users when they are offline and scans won’t be saved. Users have the option to check a ‘Don’t show this warning again’ box if they do not wish to be prompted again. 
• Scanning leads without a licence – Leads collected without a Visit Connect licence are now synced to the server, but the user can only see part of the leads’ information (first name and first letter of their last name), and they get a warning message that they should add a licence if they wish to see the full details. 
• Improved behavior when upgrading from limited to unlimited licence – when a partner gets an upgrade from a limited number of licences to unlimited, the change is immediately reflected in Visit Connect, and the leads previously scanned by team members without a licence are automatically synced to the account. 
• Improved UI on capture leads permissions  – Admins have a better view of the available lead capture permissions, so they can easily decide on which team members should be able to scan. 

Emails: Confirmation emails can now be sent to registrants that have been added via the API.  

Visitor comments: Comments added to registrant records are now available in the API. 

Notifications: Moving forward, by default, notifications via the JSON API will not include visitor activity such as content scanning. They will only be triggered by new and modified registrations. 

Access: Check-in (former EventBox) unlock password and screen-lock settings have been moved from Organisation to Onsite settings. 

Manual clock set-up: We’ve added the option to manually confirm synchronisation with the Visit server to set the local clock on Visit Check-in in case NTP synchronization is not working. There are situations where the NTP port is blocked by the venue and therefore Visit Check-in can’t automatically synchronise its time.