run-as-user for automatic gl transactions

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

run-as-user for automatic gl transactions

Jacopo Cappellato-4
Is it ok if I change all the seca definitions for automatic general ledger transactions to use the run-as-user="system" setting?
IMO this is the most correct setting because the transactions are actually automatically created by the system and not by the user that triggered the event (for example a "packer").

Jacopo

Reply | Threaded
Open this post in threaded view
|

Re: run-as-user for automatic gl transactions

Ashish Vijaywargiya
+1.

--
Ashish

On Wed, Mar 31, 2010 at 3:09 PM, Jacopo Cappellato
<[hidden email]> wrote:
> Is it ok if I change all the seca definitions for automatic general ledger transactions to use the run-as-user="system" setting?
> IMO this is the most correct setting because the transactions are actually automatically created by the system and not by the user that triggered the event (for example a "packer").
>
> Jacopo
>
>
Reply | Threaded
Open this post in threaded view
|

Re: run-as-user for automatic gl transactions

BJ Freeman
In reply to this post by Jacopo Cappellato-4
good start.
think should review all to see if they can run that way.

=========================
BJ Freeman
http://bjfreeman.elance.com
Strategic Power Office with Supplier Automation <http://www.businessesnetwork.com/automation/viewforum.php?f=93>
Specialtymarket.com <http://www.specialtymarket.com/>

Systems Integrator-- Glad to Assist

Chat  Y! messenger: bjfr33man
Linkedin
<http://www.linkedin.com/profile?viewProfile=&key=1237480&locale=en_US&trk=tab_pro>


Jacopo Cappellato sent the following on 3/31/2010 2:39 AM:
> Is it ok if I change all the seca definitions for automatic general ledger transactions to use the run-as-user="system" setting?
> IMO this is the most correct setting because the transactions are actually automatically created by the system and not by the user that triggered the event (for example a "packer").
>
> Jacopo
>
>