How to detect if an element could be deleted without locks?

[Mauricio Moya (Arquesoft)]

I would like to validate if the current user is enabled (by evaluating if belongs to a security group) to delete an element. It would be great if the workflow scripts had the function CanDeleteElement, but not.

I don't want to lock the elements to the given group because if you don't belong to the group, you can not edit or create connectors to this element. But I need to allow all users to edit or create connectors to the elements, but only allows some users to delete the elements. Any idea?

[OpenIT Solutions]

Hi,

I thought you could create a connector to an element locked to you via UI and Automation Interface - have you tested ?

[Mauricio Moya (Arquesoft)]

Hi,

I thought you could create a connector to an element locked to you via UI and Automation Interface - have you tested ?

It is supposed the Automation Interface runs with the permissions of the user running the automation. But you can create the connector via INSERT into the t_connector table, but it changes the natural way of creating connector (via the toolbox or the quicklinker). The idea is not to change the normal behavior of the user interface, just restricting the element deletion.

[qwerty]

Why is it that you want to prevent it? Rogue modelers? Why not fire them if they don't behave well?

q.

[Mauricio Moya (Arquesoft)]

Why is it that you want to prevent it? Rogue modelers? Why not fire them if they don't behave well?

q.

They are many modelers! I can't fire them all! Just want to prevent accidental deletions

[qwerty]

Enable security. That's just what it was designed for. If on takes two steps (lock, delete) it's intentional.

q.

[Mauricio Moya (Arquesoft)]

Enable security. That's just what it was designed for. If on takes two steps (lock, delete) it's intentional.

q.

The idea is to allow connecting elements but not to delete them. It could be better designed if Delete elements was a permission different from Update elements.

[Paolo F Cantoni]

Enable security. That's just what it was designed for. If on takes two steps (lock, delete) it's intentional.

q.

The idea is to allow connecting elements but not to delete them. It could be better designed if Delete elements was a permission different from Update elements.

+1!

As Arquesoft said, in an Enterprise situation, there may be too many modellers!

Hell, even I've accidentally deleted the wrong arc.

Paolo