This is not turned on through RBS.  You can actually audit transactions on a BO and there is a class called Auditor which you can programmatically call and audit as well.  The reason for any delays here is due to the nature of auditing through a BO versus the database.  There is far more traffic that gets passed back and forth when auditing at this level (BO), thus to prevent any potential issues that can come from this, it has not been released.  Will this particular feature ever be globally turned on...the answer is maybe.  Since the database (i.e. triggers or an auditing tool at the data level) is recommended for major auditing due to performance and reliability, the only auditing recommended from the BO level is more complex and detailed auditing in regards to creating a point of sale transactions history, for example.  This is something that you would need to track and report on within your application.  In scenarios like this, it is then recommended to create auditing at the BO/client side.  Hope this makes sense.

I am a new user.  I've turned on audit tracking for the user in Security.  I've turned on the business object's AuditDataChnages property.  Is the audit tracking working in 1.6.7 Beta?  I've read in forums where this was not a feature turned on yet.  Is it not?  If not, any idea when?