Who did what: Store user aliases in the journal

Automatically translated from English

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:

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!


• Product Owner •

Damien Fuzeau has joined the 4D Product team in February 2019. As a Product Owner, he is in charge of writing user stories, then translating them to functional specifications. His job also entails making sure that the feature implementations delivered are meeting the customer needs.

Damien is graduated from the University of Nantes in software engineering. He spent more than 23 years in its former company, first as developer (discovering 4D in 1997), and later as engineering manager and software architect. This company is a 4D OEM partner and deployed 4D based business softwares for thousands users, on hundreds servers. So, Damien is used to 4D development and deployment in a multi-language context.