September 2025 - Name Allocation Manager

Support-ID

Description

NAM API - FIRST option did not work as expected

Sequence numbers are now properly released in name contexts with "Prevent duplicate names" enabled, when unique fully qualified name validation fails during final allocation check, preventing sequence number leakage

Tags are loading incorrectly when loading with primary and secondary sequence in batch

Batch requests now correctly allocate names when mixing items with both primary and secondary sequences.

Name allocation allows primary sequence as "0"

Name allocation now properly rejects sequence "0" for both Primary and Secondary sequences instead of allowing it.

"GET /v1/scopes/{scopeId}/names/{fullyQualifiedName}" does not return correct result

GET /v1/scopes/{scopeId}/names/{fullyQualifiedName}requests now return names from all name contexts under a scope instead of only returning the name from the first name context.

NAM API operates through enterprise-grade cloud infrastructure that includes security gateways and load balancing services. These systems automatically normalize URLs according to web standards before requests reaches application servers.

The Technical Issue

When %2F (URL-encoded forward slash) is sent in Name, the Cloud gateway automatically decode %2F back to / during request processing. This causes path parsing issues since / is interpreted as a path separator rather than part of the Name. This behaviour is standard across modern cloud platforms and cannot be bypassed at the application level. The same happens when \\ is present which gets decoded to /.

Our Solution: slash Token

To ensure reliable data transmission across all infrastructure layers, we've implemented a simple token replacement system:

Request: Use _slash_ wherever you need a forward slash character in Name

Use _bslash_ wherever you need a backward slash character in Name

API process: API automatically converts _slash_ to / in Name and _bslash_ to \

Error message status code is incorrect when try to create an existing freeform class tag

Allocating a name using a structured naming rule that matches an existing freeform name now correctly returns 409 Conflict instead of 400 Bad Request to indicate the name already exists in the name context.

Single Name gets generated when we have Primary and Sequence used with Overide with option

Name allocation now works correctly when requesting Primary and Secondary sequences together.

Primary Sequence jumps by 1 when trying to create a Name

Override option for both - validation added to prevent quantity greater than 1 for such requests

Fails to generate Names as requested with Primary as Overide and Secondary as FIRST.

Different combinations of First, Next & Override for both - primary sequence now correctly takes precedence over secondary sequence, ensuring primary sequence is generated first followed by the corresponding secondary sequence.

429 error when creating Sequence Reservations

Sequence Reservations now properly load all mapped types in the dropdown to handle naming rules with more than 50 type mappings, resolving 429 rate limiting errors.

BehaviourOnFailure is not working when set to Continue

Allocating Names API option BehaviourOnFailure with value "Continue", now properly processes remaining items after sequence conflicts instead of returning 400 Bad Request.

Name of name parts in a naming rule must be trimmed of empty spaces at the end

Name of parts in naming rules are now automatically trimmed of trailing spaces to prevent 400 Bad Request errors in other parts of the system.

Sequence Reservation fails to create from Web dashboard if Name context has "Prevent duplicate names" option checked

Corrected an issue preventing Sequence Reservation creation in the Web Dashboard when the associated Name Context enforced "Prevent duplicate names".

Web dashboard-record order gets changed ,min and max values defined for Sequence Reservation are cleared in UI

Corrected inconsistent ordering and cleared min/max values in the Sequence Reservation list when switching between reservations. Values and order now persist as expected.

Added validations to capture some unhandled errors returning 500 status code