Ticket profile
This setup table is used to control which tickets may be used in a specific speedgate/scanner.
What the page is used for
A ticket profile defines access rules for a scanner ID, for example:
- which ticket items are allowed
- which admission codes may be used
- whether access only applies at specific times
- whether access only applies on specific days via a calendar
- whether specific tickets should actively be rejected
Fields on the profile
- Code
- Unique code for the profile.
- Description
- Short explanation of what the profile is used for.
- Allow Ticket Request Token
- Enable this if a temporary token should also be accepted as proof of access.
- Validation Mode
- Strict: only tickets that match an allowed rule are granted access.
Lines on the profile
Rules are created as lines under the profile.
Each line can contain:
- Rule Type
- Allow = allow access
- Reject = reject access
- Description
- Internal note describing what the rule does.
- Item No.
- The ticket item the rule applies to.
- Admission Code
- Limits the rule to a specific admission type.
- Calendar Code
- Makes the rule active only on specific days.
- From Time / To Time
- Makes the rule active only within a specific time period.
How to create a ticket profile
- Open the Speedgate Ticket Profile list.
- Create a new profile.
- Fill in Code and Description.
How to create access rules
Allow a ticket
- Create a new line.
- Set Rule Type to Allow.
- Fill in Item No., if relevant.
- Fill in Admission Code, if relevant.
- Fill in Calendar Code, if relevant.
- Fill in From Time and To Time, if relevant.
Reject a ticket
- Create a new line.
- Set Rule Type to Reject.
- Fill in Item No..
Note:
- A Reject rule requires an item number.
- A ticket may be allowed by an Allow line, but still be stopped by a Reject line.
How the profile is used in practice
Once the profile has been created, it must be linked to the relevant speedgate/scanner in the speedgate setup.
When a ticket is scanned, the process is typically as follows:
- The system finds the ticket profile for the current gate.
- The ticket item and admission code are compared with the lines on the profile.
- Time and calendar are checked.
- Any Reject rules are evaluated.
- The result is either access granted or access rejected.
Good advice
- Start with very specific rules.
- Avoid overly broad rules with empty fields.
- Use Description on the lines so it is easy to troubleshoot later.
- Always test the profile on the specific gate after setup.
