October 2026 - Name allocation manager

Feature

Description

Name context

In this release, an administrator can configure Default naming rule support for a Name context in both the Name allocation manager(NAM) API and the web dashboard and configuration UI. The enhancement enables the administrator to mark a Naming rule as the default within a Name context when multiple naming rules are associated with the same type.

It addresses scenarios in which a name context has multiple naming rules that can generate names for the same type, yet the system selects a naming rule automatically without requiring your input from applications integrated with the NAM API. For example, when you allocate names during Unified Engineering excel data imports or when you create tags by dragging and dropping symbols onto a graphics canvas. The newly created tags automatically use the configured default naming rule.

The web UI also provides visual indicators for the Excluded For and Default For status of each naming rule and type combination within a Name context. This helps you identify, manage, and validate Name context configurations through a more intuitive interface.

Case Number

Defect

Resolved

962730165

Naming rule parts appeared disabled during editing because a Type mapping existed for the naming rule.

Naming rule parts linked to Type mappings are now updated correctly when the rule changes, ensuring all parts remain selectable and editable.

962641718

Create name request failed when Protection strings contain Japanese character

Tag creation, rename, and delete operations now work correctly when the project server directory path includes Japanese characters.

962860700

Importing configuration data does not bring back the expected Name contexts.

When you export from a folder that contains no scopes, the export action shows progress and then disappears without a validation message or other user feedback.

Exporting NAM using the Export button produces different results.

When you import configuration data, the system restores Name contexts correctly.

When you export from a folder with no scopes, the system now displays a clear validation message instead of failing without feedback.

When you run repeated exports, the output is now consistent. The system sorts Naming rules, Rule sets, and Scopes before writing them to the ZIP file.

962850432

Naming rule preview did not display the full generated name when a rule contained more than three or four parts

The preview section now displays the complete generated name across all rule parts.

962828464

NAM and NAM API correctly allocates a sequence but incorrectly returns HTTP 409 (Conflict) when you use a First sequence mode.

The retry pattern now executes correctly and returns a successful response.

N/A

The backend creates a sequence reservation when the request does not include a Type.
Multiple sequence reservations can be created for the same type and context.
Creation of a sequence reservation with an invalid type returns HTTP 500 instead of an expected HTTP 400 (validation) or HTTP 404 (not found).

If you create a reservation without a Type, the request is now rejected with a clear HTTP 400 validation error.

If you submit a reservation with an Invalid type, the service no longer returns a misleading HTTP 500. It now correctly returns HTTP 400.

The service now enforces a uniqueness constraint to prevent duplicate reservations for the same type and context.

N/A

Search field returns an unknown error when you enter symbol characters as input.

Input validation has been strengthened and symbol or special-character input is handled without returning an unknown error to you.

N/A

When you interchange the mapping attribute in Type Mapping, the system does not reflect the change.

Interchanged attribute mappings are now saved correctly and are reflected after you update the Type Mapping.

Support- ID

Description

Workaround

- / -

- / -

- / -