Scan Simulation

The powerful simulation function enables you to validate your event access configuration without the need of setting up the associated onsite systems (Visit Check-In or Visit Check-in lite). By simulating real-world situations against actual registrations, this gives the peace of mind that everything is configured correctly. It can also be used as a debugging tool to indicate where possible configuration issues lie in your access control logic.

As you’re simulating real-world usage, for each test case you will need to identify:

• The code value to scan
• The date and time of the scan, in the event’s local timezone
• The software operating mode for Checkin or Checkin Lite
• The physical scanning location (the gate location associated with CheckIn or Checkin lite)

Creating Scan Test Cases

Use the +Add button to define a new test case

Name and time

Enter a name, optional description and date/time for your test case

Mode and location

Select the operating mode and location of Visit Check-In (or Check-In lite). In this example we’re simulating access control mode, used for scanning badges at named locations to return an access/no access result. Note that location isn’t mandated on Visit Check-In (hence is an optional setting here), however normally when using Access Control you’ll want to be checking in the context of a known onsite location.

Simulation code

Select a valid scannable code to use in your test case. This can be one of:

• Visitor QR codes, generated automatically for every registration
• Optional Ticket QR codes attached to products ordered by registrants
• Third party code values imported as Registration Codes

Search for a registered visitor to reveal their QR code and any associated ticket codes they have ordered. Note that a Visitor QR code can be scanned in place of ticket codes, since the associated ticketed products are associated with the parent visitor’s order. The reverse is not true however; scanning a specific ticket code relates to any access logic related to that product only and cannot be used to represent the parent Visitor.

Expected result