Release Notes Visit 5.10

Visit Create

Organisation Portfolio

We’ve introduced a new portfolio feature for organisers (Organisation > Setup > Portfolio), designed to help you categorise events and assign the appropriate responsible staff more efficiently.

This allows the creation of event portfolios based on various criteria such as brand, region, or industry. This categorisation allows for a more organised and targeted approach to event management. Additionally, it enhances security and focus by enabling restriction of staff access to only those portfolios they are responsible for managing.

Once you have defined your portfolios and have assigned the corresponding events to each of them, you can grant access to your users, ensuring they have visibility only to the portfolios that are relevant to their role and responsibilities.

Forms

We’ve added the option to have nested hierarchy for multi-select checkboxes in Forms. This new feature allows you to set up more complex profile questions with sub-branches. A question can have multiple sub-branches, and you can set up which ones are mandatory.

You now have the option to mass import/export answers to form questions from/into an Excel file. This saves time and adds flexibility when managing questions with larger number of answers.

Release Notes Visit 5.9

Visit Create API

JSON API V2

The Visit JSON API has undergone a comprehensive review and refactoring process, marking its exit from the Beta phase.

This version of the Visit API supersedes the existing JSON API, which will continue to be maintained for a while, due to compatibility with existing integrations (as will the XML API).

Benefits of the new API include:
• Support for powerful webhooks, enabling software notifications
• Increased efficiency of use by separating pre-event registration and event generated data
• Improvement and standardisation of field names and structures, in line with recommended API practices
• Resolution of known issues when manging visitors and partners using 3rd party IDs (references)

The create API is located at: https://api.visitcloud.com/create/v2

For detailed information on using the updated Visit JSON API, please refer to the latest version of our API documentation, available here.

Visit Connect API

We’ve added the ability for exhibitors to fetch leads from Visit Connect via API, so they can integrate with their own systems. Permission to use this will be granted based on licences, similar to the scan & Touchpoint ones.

The license for the Connections API enables consuming applications to:
1. Fetch leads from Visit Connect into external systems, such as CRM platforms.
2. Scan attendee QR codes using exhibitors’ own hardware and to submit to the API to generate a connection and return the associated contact properties.
Valid scans submitted to the API are available under the leads section of the Visit Connect user interface and are available for export to those users with the required permissions; in that respect they are no different to connections made by scanning with our own solutions.

Registered users may access the Visit Connect application at https://connect.visitcloud.com

Documentation is available here.

Visit Create

DTCM

The DTCM post-show report is now integrated into Visit Create.
We have further upgraded Visit to adhere to DTCM regulations. Now, when a DTCM QR code (Design > Documents > Digital Badge) is added to a digital badge, it generates a compact code that can be enlarged for use as needed.

Check-in Lite

We’ve made several improvements based on organiser feedback and our own experience aimed at improving onsite performance:

• We have improved setup by removing the email field from the initial screen, thus only a device name must be entered. We’ve also introduced the concept of device ID (similar to Check-in terminals).
• We’ve added the option to define a PIN code that prevents staff from making unwanted changes to the settings. This can be configured under the Onsite Settings in Visit Create. Once the PIN code has been defined, users must first enter the code before making any changes in the app settings.
• We have removed the health scan option, so now there’s only the access scan button available.
• We’ve also improved session management, so when the online session is expired, Check-in Lite will automatically login, without the need to scan the licence again.
• Time synchronisation has also been improved. Since Check-in Lite can work offline, we rely on device clock for badge and ticket scans. Sometimes devices used onsite are not set to UTC (which is what would be expected). To avoid being dependent on the user to take action, we now calculate an offset and correct the times so they are in UTC.
• We’ve added a Finish option to the Check-in Lite menu. When users are done scanning, they can select this option, which will mark the device as Finished in the Create status overview.
• TheVisit Check-in Lite devices overview in Visit Create has been improved by adding and changing some columns. We’ve added a preview panel which provides more diagnostics about the Check-in Lite device.