Concurent editing

[yiki]

if we're using a single shared".EA" file Is there a way to give control what user has access to what package?

Note: I know Security give an overall permission but that's not what I want.

Thanks

[OpenIT Solutions]

No. If you want package level security you will need to integrate with a VC platform and use it to manage package level permissions. I suppose you could also wrtie a workflow script - but it would be v messy approach in my opinion.

[yiki]

perfect , thanks that's what I thought.

[yiki]

than if u use a DBMS instead of an ".eap"file you can give access to package right? instead of using version control

[qwerty]

You can also use EA's internal security mechanism (I guess you were talking about another security). This one can be used in EAP and DBMS repositories.

q.

[Geert Bellekens]

than if u use a DBMS instead of an ".eap"file you can give access to package right? instead of using version control

No :-?
Unless you know a DBMS (supported by EA) that has row level security?

Geert

[yiki]

Thanks qwerty I have tried the built in Security and it works  both ways "for giving access to single package" or setting up a "role".

Geert so you mean that if I implemented a DBMS that is supported by EA I can't control packages unless I use the built in EA security?!

[qwerty]

Again answering for Geert: he's talking of the DBMS capabilities regardless of EA. And what you desire can not be covered by a DBMS he (or me) knows.

q.

[yiki]

Oh ok. Thanks for the  clarification.

To summarize:
The only way to controll access to packages without using version control is use built in feature of EA " Security" ( wether I was using .EAP or shared DBMS) coz no DBMS supported by EA can control who can access what.

Thanks all