March 2025 - Name Allocation Manager

Feature

Description

Enhanced uniqueness check to prevent duplicate names

Introduced a new option within the name context to ensure stricter control over name allocation to prevent duplicate names.

What’s Improved:

A new configuration option allows you to enforce strict uniqueness for names within a name context.

When enabled, this option ensures that no two allocations in the same name context can have identical Fully qualified names (allocated name combined with invisible name part values), regardless of their associated types or naming rules.

How It Works:

Previously, duplicate names for example, P-1 could exist in a name context if they were allocated to different associated types for example, a Plant and a Pump.

In the new option, the system will validate and enforce unique names, ensuring that there is only one instance of the same name. For example, only one P-1 within the name context.

Enhanced allocation handling for First/Next options

Improved handling of name allocation when using the First or Next options in scenarios where multiple naming rules exist within the same name context.

What’s Improved:`

The system will now automatically increment sequence numbers to avoid conflicts when allocating names.

If a conflict is encountered, for example, a name generated by another naming rule that already exists, the system will seamlessly move to the next available sequence number, ensuring smooth and uninterrupted name generation.

Example Scenario:

Two naming rules are applied in the same name context: one with a sequence and one without.

The naming rule with a sequence is allocated the names P-1 and P-2.

The naming rule without a sequence is allocated the name P-3.

When requesting the Next allocation, the system will allocate P-4 instead of P-3 to accommodate the existing P-3 from the other naming rule.

NOTE: To implement this enhancement, the padding character for the sequence name part has been limited to '0'

Improved deletion reliability for Scope / Name context with allocated names

The deletion process for Scope / Name context containing a large number of allocated names has been enhanced to be more reliable.

What’s Changed:

Previously, deleting a Scope / Name context with a large number of allocated names could cause the deletion process to stop midway, leaving the Scope / Name context and its names in an incomplete state.

Now, deletion is handled as a background task, allowing the Scope / Name context to be removed immediately while the associated names are deleted gradually in the background.

Compliance with AVEVA’s log retention policy

Infrastructure changes have been made to be compliant with the mandatory retention period for the logs.

Compliance with Capability Audience Validation

Capability Audience validation NAM without any downtime. The upgrade addresses a security vulnerability where solutions could use access tokens to impersonate SCM and make Capability Provider Contract calls to other, unrelated solutions.

Support - ID

Description

Workaround

N/A

Audit logs for NAM tenancy created in a CONNECT folder are visible in the NAM web dashboard. Tenancy created at account level audit log is only visible in CONNECT Audit

None

Support - ID

Description

N/A

No validation on quantity of names requested leads to 500 error - A check has been added to validate that no more than 1000 names can be requested in a single request, this also applies to GET operation for names where each page will serve no more than 1000 names.

Audit Ingestion to CONNECT for NAM entities is fixed and audit logs are visible in CONNECT reports and NAM web dashboard