Who did what: Store user aliases in the journal

By now, you’ve surely discovered the new ability to identify your users thanks to the SET USER ALIAS command. In 4D v18 R2, the command’s behavior has been extended. How? Keep reading! 

As we told you in this blog post, you can dynamically change a user name by calling the SET USER ALIAS command. After this call, the user name is replaced for the duration of the session and displayed in interfaces such as the 4D Server Administration window, lock alert, and returned by the Current user command. Now when an alias is set, it’s also stored in the journal. This lets you retrieve the correct user, even if several users share the same computer and/or system account.

• In the MSC’s Activity analysis tab:

• In the MSC’s Rollback tab:

• In the dialog displayed with the CHECK LOG FILE command:

• In the JSON file generated by LOG FILE TO JSON:

Note that if the current user or the alias changes during a process execution, a new operation with type 32 is written in the log file:

Hope this feature helps you determine who did what!