Re: Authorization for SEU

[Vernon Hamberg <vhamberg@xxxxxxxxxxx>]

Tomasz

Seems to me that PDE400 support should be able to tell you this. When 
I worked at a company that had Aldon's CMS, we took all authority 
from developers and made *PUBLIC *EXCLUDE. The CMD has all authority 
to source, so things could be opened within the CMS but not by users 
through SEU itself. This is generally desirable, to prevent casual 
changes outside the scope of the CMS. I suggest looking in their 
documentation - I believe you have that if you bought it - or call 
their support - I hope it does not cost you - the site said something 
about 90 days for free support.

Vern

At 01:01 PM 9/24/2006, you wrote:

> Hi
>
> I would like to add modification to SEU which allow me to browse any
> sources, but to edit only from list.
>
> I mmean I have:
> 1) LIB1, SRCF1, MEMB1, MEMB2
> 2) LIB2, SRCF2, MEMB3, MEMB4
>
> And now I would like to "have authorization" to browse all four members, but
> i.e. to allow edit only to member 1 and member 4? Is it possible?
>
> If I set Exclude for SRCF1 - I don't see it anymore - so it's not good
> solution.
>
> A few words why I need it. I bought PDE400 CMS and I would like to force
> source modifications by PDE projects managements, not by simple entering
> STRPDM in command line.
>
> Regards
>
> Tomasz Skorza
>
>
> --
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
> To post a message email: MIDRANGE-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.