Lock down environment

Slap

Member
How might one go about locking down an environment from development in OneWorld Xe?
 
Remove the OMW activity rules that are needed for check-out, check-in and object transfer.
 
Slap,

I have created two logons for our Developers. The first logon only has access to the Development environemnt and has access to OMW and RDA etc. The second logon has access to the Prototype and Production environments and does not have rights to OMW and RDA etc.

This keeps the developers from making changes in the prototype and production environments.
 
Use Object Management Configuration to setup rules so that when the project
is at status 26 or higher, Developer role (02) cannot check in, check out or
design etc. That way you won't need any separate logon ID's and any
dvelopers that you have will only be able to conduct design activities when
the project is at status 21 (or lower).

Hope that helps. You can setup OMW to do anything you want it to do and if
you don't want someone doing something at any stage - it CAN be configured
that way.


From: JDEJohnny <[email protected]>
Reply-To: [email protected]
To: [email protected]
Subject: Re: Lock down environment
Date: Fri, 8 Nov 2002 04:47:21 -0800 (PST)

Remove the OMW activity rules that are needed for check-out, check-in and
object transfer.
John
B7333 (SP19.1)/Coex AS/400 (A73 CUM11)
--------------------------
To view this thread, go to:
http://www.jdelist.com/ubb/showthreaded.php?Cat=&Board=OW&Number=44836
+ - - - - - - - - - - - - - - - - - - - - - - - -+
This is the JDEList One World® / XE mailing list/forum.
Archives and information on how to SUBSCRIBE, and
UNSUBSCRIBE can be found on the JDEList Forum at
http://www.JDEList.com

JDEList is not affiliated with JDEdwards®

+ - - - - - - - - - - - - - - - - - - - - - - - -+


Peter J Fourie
 
Back
Top