We would like to have a better overview on our user registration in BO. In
the OBJ_M_ACTOR table you are able to find some information about BO-users.
But I am interested in looking at the date when a user has been registered.
There is a M_ACTOR_N_LAD (last action date) column which gives you a hint in
combination with the M_ACTOR_N_LAT (last action type) column what has
happened when to a user.
However, if a new user is registered, the status in M_ACTOR_N_LAT is set to
something like “inserted”, but if the new user goes away and changes his
password in the next minute or someone changes some other information
related to this user, then the status changes to something like “updated”
and my information about the exact registration date is gone.
Has anyone given some thoughts to this problem or even better, has a
solution?
What I tried so far was implementing a database trigger (on-insert trigger)
on the OBJ_M_ACTOR table but for some unknown reason the trigger doesn’t
fire when an insert via the BO-supervisor tools happens.
Andrea Halbherr
Novartis Crop Protection
DW-DW Competence Center
R-1007.4.13
Tel.: ++41-61-697-6295
Fax: ++41-61-697-5283
Andrea,
you have to look on OBJ_M_ACTOR and OBJ_M_ACTORLINK tables as a logical unit of
information.
In the OBJ_M_ACTORLINK there are as well LAD/LAT fields, they remain the same
since creation of the actor. Changes are reflected in OBJ_M_ACTOR table. This is
what I could find out.
hope this helps.
Walter
“(Andrea Halbherr)” wrote:
We would like to have a better overview on our user registration in BO. In
the OBJ_M_ACTOR table you are able to find some information about BO-users.
But I am interested in looking at the date when a user has been registered.
There is a M_ACTOR_N_LAD (last action date) column which gives you a hint in
combination with the M_ACTOR_N_LAT (last action type) column what has
happened when to a user.
However, if a new user is registered, the status in M_ACTOR_N_LAT is set to
something like “inserted”, but if the new user goes away and changes his
password in the next minute or someone changes some other information
related to this user, then the status changes to something like “updated”
and my information about the exact registration date is gone.
Has anyone given some thoughts to this problem or even better, has a
solution?
What I tried so far was implementing a database trigger (on-insert trigger)
on the OBJ_M_ACTOR table but for some unknown reason the trigger doesn’t
fire when an insert via the BO-supervisor tools happens.
Andrea Halbherr
Novartis Crop Protection
DW-DW Competence Center
R-1007.4.13
Tel.: ++41-61-697-6295
Fax: ++41-61-697-5283