We have a custom in-house app (java based written by me) that takes packing
lists and drops them to def file and handles other such things as workflow
deletes/renames, data delete/rename/import, that sorta thing..basically the
developers utilize this app and it creates an automated set of instructions
that the env team just clicks a button and it does the code/data/filesystem
updates..but we as developers are not allowed to press that button.

 

From: Action Request System discussion list(ARSList)
[mailto:arsl...@arslist.org] On Behalf Of Jason Miller
Sent: Friday, July 30, 2010 1:00 PM
To: arslist@ARSLIST.ORG
Subject: Re: Capturing when an Admin Login is used

 

** 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 <lj.longw...@gmail.com> 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:arsl...@arslist.org] On Behalf Of Jason Miller
Sent: Friday, July 30, 2010 11:54 AM


To: arslist@ARSLIST.ORG
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 <lj.longw...@gmail.com> 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"_ 


_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"

Reply via email to