When PATGuard Cloud creates a new asset via the user interface, it generates a new Asset ID to identify it.
There are a number of rules which are applied and can be configured depending on what suits your setup.
- Rule: Within the lowest level (Location) the Asset ID must be unique. This rule cannot be changed or configured.
- Configuration: A specific option is available that nominates that all assets in your subscription should have unique Asset IDs. This will be useful mostly to customers who are managing their own assets.
When generating the actual number portion of the Asset ID, PATGuard Cloud uses the most recently created asset as a reference within the selected scope.
- Scope: the scope for generating the next Asset ID can be the same Location they are in, or Site, or Client, or the whole subscription
- Location: If the most recently created asset is AX1101, then the next number will be AX1102 (unless that already exists in the location in which case AX1103 will be used etc)
- Site: This looks for the most recently created asset across multiple Locations in the same Site
- Client: This looks for the most recently created asset across each Location within each Site
- Customer: This looks for the most recently created asset across the entire subscription
- Mode: the specific mode for the number portion can also be controlled
- Latest: whatever the reference asset is, this will look to be the next available (see example a
- Gap: if the reference asset is AX1101, this will look to use the lowest unused number in sequence e.g. AX0001, then AX0002 etc
- Max: If the reference asset is AX1101, then this will look for the highest AX#### asset and then sequence afterwards. If the highest happens to be AX3081, then AX3082 will be used