Creating new Operations in Locked Components

[Ian Mitchell]

We have a component model which has locked components which most users can't update.
So, if they try to add new Operations to those components directly, EA correctly stops them.
BUT
When they take the same component, make it realize an interface, EA will let them select which operations they want to implement, THEN LETS THEM ADD THEM TO THE COMPONENT.
Surely this breaks the security model? Or have I missed an option somewhere?
How can I stop my users from compromising the integrity of my master model ? :-/

[qwerty]

The usual way: write a bug report and write some add-in to circumvent the bug.

q.

[Ian Mitchell]

@qwerty - does this mean that you can confirm this is a bug, with no work-around?

[Geert Bellekens]

Ian,

I know you won't like it, but adding version control sometimes helps with things like this.
For some dark unknown reason version control read-only is stronger then regular read-only.

Geert

[qwerty]

@qwerty - does this mean that you can confirm this is a bug, with no work-around?

Not yet , I just believed what you said. However, I'll  try tonight.

q.

[Ian Mitchell]

Implementing Version Control seems a poor way to make EA work properly!

[Helmut Ortmann]

Version Control has a lot of pros and cons. In this forum there are a lot of threads about it.

Be aware you have to pay something for Version Control:
- Performance
- Some peculier things that take your time and sometimes nerves
- Cross Package dependencies sometimes causing trouble
- I would prefer EA 10 because of some improvements

If you like Version Control and you need it it's worth trying it.

I'm working with safety relevant Software. Therefore Version Control is no question.  Sometimes it's a good thing to simply undo your changes or to get back to an previous version. It's more systematic but it takes its price.

Helmut

[qwerty]

@qwerty - does this mean that you can confirm this is a bug, with no work-around?

It is as you said. From my POV I consider this a bug.

q.