I can think of a couple of things:

a) You may (or may not) want to set / protect any type of predefined security setups and authorities that you may have against specific system applications developed for users who may have different responsibilities / tasks under a test environment. Then, you may want to restore those definitions over the test environment.

b) Modify / change any type of object that will trigger automatic system actions like data queues triggering the submission of purchase orders, invoices, etc., potentially sending test environment data to real faxes numbers, IP addresses, emails, etc. Those areas must be identified and systematically modified, so you can interrupt those automatic actions.

Peter Vidal

This communication is intended only for the use of the individual or entity named as the addressee. It may contain information which is privileged and/or confidential under applicable law. If you are not the intended recipient or such recipient's employee or agent, you are hereby notified that any dissemination, copy or disclosure of this communication is strictly prohibited. If you have received this communication in error, please immediately notify CareCentrix Compliance Hot Line at (877) 848-8229 and notify the sender by electronic mail. Please expunge this communication without making any copies. Thank you for your cooperation.

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.