Sparx User Privileges diagram connectors - query

[mohanp]

We are experiencing a strange situation regarding 'User Privileges' in the Sparx repository.

'User1' belongs to 'Group1' and 'User2' belongs to 'Group2'.

If a data model is created by 'User2' with 'Group2' edit privileges then I thought following won't be possible.

When 'User1' refers elements from the data model created by 'User2' in his/her data model then 'User1' should not be able to edit/delete 'Relationships' present between the data model elements created by 'User2', but it is possible and 'User1' can edit/delete relationships. Please note that this deletion also removes relationships permanently from the underlying data models.

I hope I am missing something here?

Thank you in advance for your help.

[qwerty]

There are no group rights related to creation of elements. You can configure user groups which can perform locking. But that must be done explicitely and is not done upon element creation. I guess it would be possible to do that with an add-in.

q.

[Geert Bellekens]

The locking mechanism isn't 100%.

Relations can often still be changed if the diagram they are showed on isn't linked.
This should be considered a bug and can be reported that way using the link on the bottom of the page.

The version control mechanism is better at stopping these type of things, but still isn't 100% bullet proof. (e.g. Schema Composer edit can still be saved on a version controlled artifact that is not checked out)

Geert

[mohanp]

Thank you so much both of you for speedy reply.

Sure will raise this up as a bug using 'Report a Bug' link.

Thanks and Regards,
Mohan.

[Eve]

Without excluding the possibility of places that exist in EA that do modifying locked connectors, you also should be aware of the option 'Apply Locks to Connectors' in the security menu.

https://www.sparxsystems.com/enterprise_architect_user_guide/15.2/modeling/securitypolicy.html

Without enabling that option locks are intentionally not checked. With it, the locking should be similar to  what you get when version control is applied. The difference is that if a change gets applied anyway a subsequent check out from version control will likely blow away the change. With security only (or in a shared version control model where someone else already has a package checked out) you can't get back to the original value.

[Geert Bellekens]

Wow, thanks Eve,

For some reason I completely overlooked that option about the connectors.
Is that new, or have I been blind the whole time?

Geert

[Eve]

Is that new, or have I been blind the whole time?

A quick search of the release notes says it's been around since 'Release Notes for 12.1 Build 1224'

[Geert Bellekens]

Is that new, or have I been blind the whole time?

A quick search of the release notes says it's been around since 'Release Notes for 12.1 Build 1224'

I must have somehow missed it all that time.

Thanks Eve

Geert