Protecting Package Hierarchy

[Fred Bevan]

Is it possible to protect packages as describe below so that our reports and scripts that reference specific packages are not subject to breaking as a result of users changing or deleting the packages?

Allow:
- create, edit and delete elements, diagrams and sub-packages within protected packages

Do not allow:
- deletion, renaming, or moving of protected packages

I tried various locking options but have not been able to achieve this.

[Geert Bellekens]

I don't think you can using built in functionality, but you can
- Write an addin that reponds to the EA events and prevents the illegal operation (Good)
Or if you are really desperate add a trigger to the database that stops the deletion, or move. (Bad)

Geert

[Fred Bevan]

Thanks Geert,

I've tried the available options, so I think you are right about not being doable with built-in functionality.

I have avoided writing an addin because deployment in this shop is a major deal. I have found the MDG technology approach to give me most of what I need and it is easier (around here) to distribute updated XML files than to install software.

I think this capability would be valuable for others so I will submit a feature request.

Fred

[beginner]

Not quite sure if that helps. But you can lock to different groups. That could provide the requested functionality. Though I wouldn't know the answer right away.

<hijack>
Why is it that after creating new elements in a locked package these are completely without lock? I would expect that setting a lock on a package means everything inside is locked once an forever. But no. EA only applies the lock recursively. And then forgets about it.
</hijack>

b.