Below you will find pages that utilize the taxonomy term “Audit”
Did you know that OlivaNova is able to create application information logs automatically?
OLIVANOVA can generate code for application information logs automatically:
- for .NET environments OLIVANOVA uses the System.Diagnostics.Trace class included in the .NET Framework
- for J2EE platforms OLIVANOVA uses log4j
Audit information specified in a model … part 2
In the first part of this post, I wanted to show how easy it is to access information from the currently logged in user and store this information in an action the user executes (who created/changed a record).
Now, what happens, if we have several groups of users (roles)? Well, I could create some IF..ELSE block for each role, but this would probably be not a good idea. A much better approach is to create a base class within the model and inherit all roles from this. So, the model could for instance look like this:
Audit information specified in a model ... part 1
Almost any business application I delivered contains some kind of audit information. Depending on the size and the type of application this information is more or less sufficiently distinctive. Some typical information is almost always “who did what when?”. Sometimes a “why” would also be a justifiable question, but this is out of the scope for now.
So, by using a model driven software development approach along with OlivaNova, this is easy. Let’s say, I want to create a new customer in a small CRM system. The class I created for the customer looks like this: