Yes, the audit logging feature would be the easiest way to do this.
-David
On Feb 7, 2009, at 10:26 AM, Vikas Mayur wrote:
I think this could be done using enable-audit-log feature, but I am
not sure as I never tested this stuff.
For more information refer to
http://www.nabble.com/svn-commit%3A-r652226---in--ofbiz-trunk-framework%3A-entity-dtd--entity-entitydef--entity-src-org-ofbiz-entity--entity-src-org-ofbiz-entity-datasource--entity-src-org-ofbiz-entity-jdbc--entity-src-org-ofbiz-entity-model--service-src-org-ofbiz-service--weba...-td16974277.html#a16974277
Vikas
On Feb 7, 2009, at 7:50 PM, Nikita Shinde wrote:
Hi Jacques,
I wanted to track the history of changes(CUD) made to any entity
and who made those changes. So I wrote a service to do that which was
triggered by eecas on that entity. But in my service I could never
get the
current logged in user who was making those changes, it always gave
me
admin(because in my entity-eca.xsd its set to admin).
I had a work around for this by using secas instead.
Regards,
Nikita.
-----Original Message-----
From: Jacques Le Roux [mailto:[email protected]]
Sent: Thursday, February 05, 2009 5:34 AM
To: [email protected]
Subject: Re: Question related to eecas
Hi Nikita,
"run-as-user" is defaulted to "system" not admin for some times now
(see
entity-eca.xsd).
I think you should poke into EntityEcaAction.java around line 80
and change
their for your purpose.
BTW, it's weird to use an EECA with an user different than system,
what is
the purpose ?
Jacques
From: "Nikita Shinde" <[email protected]>
Hello All,
When I trigger a service on an eecas, I always get
userLogin
as
"admin" which is correct because "run-as-user" being defaulted to
"admin".
But in the triggered service, I want the userLogin to be
the
existing logged in user, is there a way to get that?
Kind Regards,
Nikita Shinde
Amicon Technologies Pvt. Ltd., Mumbai, India.
