Selective Visibility of elements

[Paolo F Cantoni]

I realise that what I'm about to ask is somewhat antithetical for a modelling repository, but at an enterprise level, some elements need to be visible to some users and not to others.

As far as I can tell, there's no way to do this in a single Sparx repository (as of build 1229).  You can secure against editing, but not against reading.

Would it be possible (in a sense) externally to EA to implement a form of Row-Level Security?  If one could do that (correctly), would it impact Sparx EA operations?

TIA,
Paolo

[Geert Bellekens]

I think EA will probably crash if you would prevent certain records from being read in the database, but I haven't tried.

Geert

[Paolo F Cantoni]

About 7 years or so ago, I managed to "lift" the EA DB specification so that it consisted of a set of views that returned the same structure as the tables normally do.  I was then able to change the underlying DB (while still returning the same views) without apparent problem - so that EA didn't even know it wasn't running on the normal structure.  This worked for both reading and writing.

For versions of SQL Server prior to 2106, MS recommends creating views to simulate Row-Level Security-like features.

This leads me to suspect that if one were careful and made sure that the permission predicates were set up to simulate view-like behaviour, one could get away with it.

Paolo