For few transactions in the database, they really taken care by the system
not by logged in user. I personally don't like the idea of system user
login but, but when we have direct db operations to perform without using
SECA instead EECA then system does not have any option to use logged in
user.
Hi Shikha,
As I can remember correctly(did not look at the code), you are right, the
current user is not passed to the action service. The reason is we don't
have a user login in the Delegator method(create/store).
If you did some workaround, please let us know.
--
Thanks & Regards
Pawan Verma
T
Hello Team,
We are facing an issue with EECA rule - The action service (entity-auto)
has changeByUserLoginId field which is always set as 'system' userLogin.
When explored it, we found that in EECA, userLogin passed to action service
is always 'system'. Current userLogin is not
