Tracking now tracks userID instead of userName

Classic Servoy
1

Hello,

it seems that in Servoy 3 the userId is written to the log table rather than the userName as it was in Servoy 2. This is not so nice, because it breaks functionality based on that. Could this please be made an option or changed back to the way it was?

Thanks
Patrick

2

I have put this “case” to Servoy support and received this answer:

You are mistaken, we put the user_uid into the log table username if in the log table a column with name user_uid does not exist
The user_uid is prefilled with the pk (user_id), but can be changed by you to what ever you like (as long they are unique)

To get the old behaviour back just put the username in the user_uid (via JS security node)

I don’t think this is good behavior for several reasons:

  1. Something that worked one way yesterday doesn’t work the same way today
  2. Why should a column called “username” be filled with something called “user_uid”? A name sounds like “Peter George”, a UID sounds like “4d47a466-8aa0-4f9e-a508-9f7acf9d39c9”
  3. I have good use for the field user_uid but still want the username to appear where it was
  4. Why not simply add an extra column to the log or give me the ability via auto enter values to control what gets written?

Maybe somebody else is disturbed by this…

3

I have to agree with Patrick on this. It would be nice to have to username in the log table. I tried to change the user_uid with security.setUserUID(…), but then the tracking did not work anymore…
Has anyone changed the behavior successfully?