Custom fields added by the Airport Badging Solution plugin - Genetec™ Airport Badging Solution 3.0

Genetec™ Airport Badging Solution Guide 3.0

Applies to
Genetec™ Airport Badging Solution 3.0
Last updated
2022-06-07
Content type
Guides > Plugin and extension guides
Language
English
Product
Genetec™ Airport Badging Solution
Version
3.0

The Airport Badging Solution (ABS) plugin adds new custom fields to your Security Center system. You must remember to grant access to these new custom fields to your badge officers.

Custom fields created by default

Installing the ABS plugin creates one custom data type and three custom fields in your Security Center system. They are used to track the status of the airport badges you manage. All three custom fields are created for the credential entity. This is because there is a one-to-one relationship between an airport badge and a credential in Security Center.

The added custom fiels described in the following table.

Entity type Name Data type Purpose
Credential Badge revoke state Revoke state type Track the reason why a badge has been revoked. The possible reasons are defined in the custom data type Revoke state type.
Credential Returned Boolean Whether or not the badge has been returned.
Credential Suspended Boolean Whether or not the badge has been suspended.
Best Practice: If you use other credential custom fields in your system, we recommend that you add a group name to the ABS-defined custom fields to separate them from your other custom fields in the credential layout.
IMPORTANT: If your badging officers are not administrators of your Security Center system, you must explicitly grant them access to these custom fields.
For more information, see Creating custom fields.

Custom fields that you might need to create yourself

There are custom fields that you might need to create yourself if you want to print certain badge properties on the badges, such as badge number and employee privileges. You need to create custom fields and map them to the badge-specific properties because only custom fields can be printed on badges. For more information, see Mapping badge application fields to custom fields.