Preventing another Enron... I guess it is Friday so humor is allowed. It is more likely to prevent another IPO.
How are you packaging? Packing Lists with its contents to a def or deployable applications to defs? On Fri, Jul 30, 2010 at 11:44 AM, LJ LongWing <[email protected]> wrote: > ** > > Yea…there is an ‘environment’ team that takes care of everything from > Dev->Test and Test->Prod….we developers aren’t allowed change access > anywhere except Dev. We must ‘package’ everything up that needs to be moved > and provide implementation instructions to that team….it truly makes > development harder…but I guess to prevent another Enron, we gotta do what we > gotta do. > > > > *From:* Action Request System discussion list(ARSList) [mailto: > [email protected]] *On Behalf Of *Jason Miller > *Sent:* Friday, July 30, 2010 11:54 AM > > *To:* [email protected] > *Subject:* Re: Capturing when an Admin Login is used > > > > ** Is that data you are talking about? How do you get code changes moved > to production? > > > Do you have app admins that have Admin rights to make the changes that > developers design? I have seen this with other systems but not Remedy > (yet). > > On Fri, Jul 30, 2010 at 10:35 AM, LJ LongWing <[email protected]> > wrote: > > ** > > Our SOX implementation basically made it so that WE (the developers) could > not have write access to production, plain and simple….we can have read > access to the DB, and read access to the User tool….but there is no Admin > for us in production…. > _attend WWRUG10 www.wwrug.com ARSlist: "Where the Answers Are"_ _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug10 www.wwrug.com ARSlist: "Where the Answers Are"
