Book a Demo

Author Topic: Ensure Repository Metadata Integrity, Including for Locked Items  (Read 2726 times)

adepreter

  • EA User
  • **
  • Posts: 192
  • Karma: +10/-10
    • View Profile
    Here is a general proposal to address
repository metadata integrity weaknesses, which can no longer be worked around using SQL UPDATE statements since EA Build 1721.

Just as EA provides Update() methods for elements, connectors, and diagrams, Sparx could introduce administrator-only UpdateMetadata() methods to maintain metadata consistency,  even for locked items.

These methods would support changes to:
- Element, connector, and diagram types and stereotypes.
- Properties (tagged values) and property groupings.
- Default sub-diagram types.[/li][/list]

They should allow updates either to individual items or in bulk to all items of a given type/stereotype.

This would provide a controlled and consistent way to maintain repository metadata integrity, with security and data integrity safeguards enforced by EA itself.

Cheers,
Alain
www.labnaf.one
« Last Edit: November 05, 2026, 07:23:09 pm by adepreter »

adepreter

  • EA User
  • **
  • Posts: 192
  • Karma: +10/-10
    • View Profile
Ensure Repository Metadata Integrity, Including for Locked Items
« Reply #1 on: November 05, 2026, 07:22:56 pm »
Alternative solution: New security permission “Security – Manage Metadata”, for example.

Users with this permission can make changes to items even when items are locked (locks are ignored)
Items can be elements, connectors, diagrams, packages including properties, typically
-   property/tagged value sets (add, delete, rename properties)
-   stereotypes and types of elements, connectors, diagrams, and packages

Important: When changing type or stereotype, existing property values should not be deleted, changed, or emptied

Eve

  • EA Administrator
  • EA Guru
  • *****
  • Posts: 8121
  • Karma: +119/-20
    • View Profile
I know you've been told that updating locked items for any reason is a hard no. It is a clear anti-pattern and will cause data integrity issues.

Adding a new permission doesn't address your problem in any way and wouldn't solve any of the issues that would cause.

An administrator already has the capability to remove locks that users have applied. You can do what you want with that.