March 2026 - Name Allocation Manager

Support-ID

Description

Bug 4221445: Unable to remove padding Zero ("0") from Naming part Primary sequence.
Bug 4118693: [IMS Request 4114757] NAM prevents users from removing the padding value in a pre-existing naming rule.

A defect was identified where users were unable to remove the padding value from a Primary/Secondary sequence within a Naming Rule.
Users can now remove the padding value from both Primary/Secondary sequence naming parts without encountering errors.

Bug 4436162: [IMS 4429216] Shell - NAM is failing to correctly allocate sequence numbers when two different naming rules generate conflicting tag names in the Scotford Production environment.

Resolved -An issue in the naming engine where name conflicts generated by separate naming rules within the same name context could cause the system to repeatedly assign the same sequence number. In certain cases, this prevented correct allocation of the first or next available sequence and caused the system to stall in the sequence‑assignment logic.
The sequence‑resolution process now consistently identifies and assigns a valid, non‑conflicting sequence number.
Note:Prefix, suffix, padding, and separator are never considered when determining the next available sequence number. Only the actual part values participating in the sequence criteria influence sequence allocation.

Bug 4331676: Pentest Finding 4313611: Missing Server Side Input Validation - Create NamingRule, RuleSet, Scope, Sequence reservation, NameContexts.

The API no longer bypasses UI restrictions by accepting special characters. Unified validation has been added across both server and UI layers to prevent invalid or unsafe inputs.

Bug 4338192: ENG(Tags) : Tag creation issue when class has sequence reservation created using conditions except Equal and Not equal.

Resolved - An issue where sequence reservation failed for all operators except EQUAL and NOT EQUAL, resulting in a 500 Internal Server Error during name allocation. Sequence reservation now properly supports the LESS THAN and GREATER THAN operators for numeric values.
When multiple clauses within a sequence‑reservation rule apply different operators to the same attribute, all such clauses must now use compatible value types.
The API and dashboard now provide improved validation and clear, user‑friendly error messages when creating sequence‑reservation rules.

Bug 4331675: Pentest Finding 4313669: Missing Server Side Input Validation - NamingRule DataType & Type.

Resolved - An issue where entering large minimum or maximum length values in a naming‑rule part caused the Naming Rule editor to hang or become unresponsive. This could also be exploited by malicious users to crash the application, and result in distorted previews for large max‑length values.
The system now enforces proper validation for length limits and uses a symbolic preview format that represents intent rather than repeating characters. Validation messages have been added to ensure users provide appropriate values.

Bug 4312112: Issue with field Description in Ruleset and Name context.

Creating a Ruleset or NameContext no longer results in a 400 error when the Description field contains only 1–2 characters. The system now applies appropriate minimum and maximum length validation and displays a clear warning when the description is shorter than 3 characters or longer than 100 characters.

Bug 4329317: Update of Naming Rules in Ruleset fails if Naming Rule name is long.

Adding Naming Rules with long names to a Ruleset no longer distorts the editor or hide key controls. The Naming Rule chip now supports multi‑line wrapping when text exceeds the available width, ensuring the full name remains readable and the remove (×) icon stays accessible.

Bug 4330783: [NAM1.0] - Issue in saving the Scope on updating Ruleset.

A 500 Internal Server Error occurred during Name Context update when a Naming Rule was assigned before the Ruleset.
The workflow now correctly handles this assignment order without failures.

Bug 4099104: Canceling the dialog by esc key does not close all windows.

Pressing ESC while editing a naming part in a Naming Rule (e.g., changing the Separator option) no longer leaves the dropdown control visible or interactive after the dialog closes. The ESC action now correctly closes all child controls along with the main dialog.

Bug 4110997: UI Issue : Sequence reservation - Field Type not showing complete class name if it is more than 9 characters.

In the Sequence reservation definition Field Type values longer than 18 characters were previously truncated and not fully visible. The UI now displays long text using ellipsis, with a tooltip showing the complete value.

Bug 4122454: NAM1.3 : Deleted sequence reservations still showing in the page until refreshing the page.

Deleting a Sequence Reservation now updates the page immediately without requiring a manual refresh. Previously, deleted entries continued to appear until the page was refreshed. The UI has been updated to correctly remove Sequence Reservations from the list as soon as they are deleted.

Bug 4503468: 500 error thrown when updating Inactive types under a Name Context with a Naming Rule which does not exist.
Bug 4514844: Creation of Name Context from API throws 500 error

Resolved - An issue where creating/updating a Name Context with a non-existent naming rule, incorrectly returned a 500 error instead of a proper 404.

Bug 4338135: Able to deactivate Naming rule in the dashboard when it is type mapped in Engineer configuration

Names can no longer be allocated using inactive Naming Rules. A validation check has been added to the API to prevent name creation whenever the associated Naming Rule is inactive.