AttractionSpeedgateReference

Speedgate setup

Speedgate Setup is basically the global setup page for SpeedGate, where you define the default behavior for all gates/scanners. Below it, there is a subtable/list with the individual scanners, which can override the defaults.

How the page is structured

  • Top section: global default settings for all SpeedGates
  • Subtable/list part: one line per physical scanner/gate
  • Actions: shortcuts for maintaining the related profile and setup tables

Global fields on the page

Defaults

  • Require Scanner Id
    • Determines whether a scan is only accepted when the scanner is known in the system.
    • If this is enabled, all requests must come from a registered scanner ID.
    • Used when tighter control is required over which physical devices are allowed to be used.
  • Image Profile Code
    • Default image/display profile for the gate.
    • This typically controls which images or screen layout the gate displays.
    • The field points to another setup table containing image profiles.
  • List of Allowed Numbers
    • The default list of allowed numbers.
    • This is a reference to a subtable containing numbers/barcodes that are explicitly allowed.
    • Used when only specific ticket or card numbers may be accepted.
  • Additional Items Profile Code
    • Default profile for additional item-based rules.
    • This comes from another setup table and is used when access depends on item-/product-related logic.
    • Think of it as an additional ruleset on top of tickets and membership cards.

Tickets section

  • Allow Tickets
    • Enables or disables ticket scanning globally.
    • If disabled, tickets are not accepted unless the solution handles this somewhere else.
  • Default Ticket Profile
    • The default setup for ticket validation.
    • The field points to a ticket profile subtable, where the actual rules are defined.
    • Used to define how tickets should be validated by default.
  • Ticket Profile Table
    • Contains the detailed rules for ticket validation.
    • Typically defines which ticket types are accepted and how they are validated.

Member Cards section

  • Allow Member Cards
    • Enables or disables scanning of membership cards globally.
    • If enabled, the gate can validate membership-based access.
  • Default Member Card Profile
    • The default rules for validating membership cards.
    • Points to a subtable containing member card profiles.
    • Used to determine which memberships are valid and how they are handled.
  • Member Card Profile Table
    • Stores the detailed setup for access via membership cards.
    • Typically contains the rules for validating memberships.

Wallets section

  • Allow Attraction Wallets
    • Enables or disables wallet-based access globally.
    • This is a simple yes/no setting on the default setup page.
    • There is no separate default wallet profile field on this page.

Subtable on the page: individual scanners / gates

Each line represents a specific physical scanner/gate or a POS.

These fields mostly function as overrides of the global defaults above.

Fields in the scanner subtable

  • Scanner Id
    • The unique ID of the physical scanner.
    • This is how the system knows which gate sent the scan.
    • Very important when Require Scanner Id is enabled.
  • Enabled
    • Determines whether this scanner is active.
    • If disabled, the gate is effectively deactivated in the setup.
  • Description
    • A readable name for the scanner.
    • Used to make it easier to identify, for example “Main Entrance” or “Exit Gate 2”.
  • Category Code
    • Groups the scanner into a category.
    • The field points to a category setup table.
    • Useful for organizing gates by role, area, or type.
  • Category Code
    • Contains the available categories for scanners/gates.
  • Image Profile Code
    • A scanner-specific image/display profile.
    • If filled in, it overrides the global image profile for this specific scanner.
  • Image Profile Code
    • Contains the visual display setups used by the gates.
  • List of Allowed Numbers
    • A scanner-specific list of allowed numbers.
    • If set, this gate uses its own whitelist instead of the global one.
  • List of Allowed Numbers
    • Contains named lists of approved numbers/barcodes.
    • Used to control what the gate is allowed to accept.
  • Allow Tickets
    • Enables or disables ticket access for this specific scanner.
    • Overrides the global ticket setting if needed.
  • Ticket Profile Code
    • Scanner-specific ticket validation profile.
    • Makes it possible for one gate to validate tickets differently from another.
  • Ticket Profile Table
    • Contains the rules used when validating tickets.
  • Allow Member Cards
    • Enables or disables membership cards for this scanner.
    • Can differ from the global member card setting.
  • Member Card Profile Code
    • Scanner-specific member card profile.
    • Makes it possible for this gate to use its own rules for membership validation.
  • Member Card Profile Code Table
    • Contains the detailed rules for membership cards.
  • Allow Attraction Wallets
    • Enables or disables wallet-based access for this scanner.
    • Functions as a local override for this specific gate.
  • Allow CityCard Integration
    • Enables support for CopenhagenCard on this scanner.
    • This is an integration-specific access method.
  • City Card Profile
    • Shows which Copenhagen Card location/profile is linked to the scanner.
    • This is not stored as a simple code field directly on the page, but is looked up from a related record.
    • In practice, it tells you which City Card configuration the scanner uses.
  • Additional Items Profile Code
    • Scanner-specific profile for item-related rules.
    • Overrides the default additional items profile for this gate.
  • Additional Items Profile Code
    • Contains the additional item-based access rules.

The page also has actions that open these related tables:

  • Allowed Numbers
    • Maintains whitelist setups.
  • Image Profiles
    • Maintains image/display profiles for gates.
  • Ticket Profiles
    • Maintains rules for ticket validation.
  • Member Card Profiles
    • Maintains rules for validating membership cards.
  • City Card Locations
    • Maintains the setup for the DocLx City Card integration.
  • Additional Items Profiles
    • Maintains item-related access rules.

A simple way to understand the page

Think of it like this:

  • The card at the top defines the default rules for all gates
  • The scanner subtable defines exceptions or overrides per physical gate or POS device
  • The related subtables contain the actual detailed rules, while this page is mostly used to select which ruleset should be applied.