Home > Forum > User Voice > Extending the audit trail to views

Extending the audit trail to views
2

MVP

We recently had a presentation of WEBCON BPS for a new customer. They came up with the question if not only changes of an element are being kept in history, but also views.

So we need to define the definition, what as to be considered as a view.
Sometimes you can tell a lot from what you see on a report already, but keeping track of this would be too much in my opinion.

The easiest and most pragmatic way to keep track of views would be opening a preview or of course a form.
Maybe also viewing or downloading a file could be recorded.

The most luxury version would be configuration options (elements views, element edits, document downloads, document previews) on process level. By default it would then be switched off.

It might be feature other partners/customers would like to have as well.

Privacy overview

This website uses cookies so that we can provide you with the best user experience possible. Cookie information is stored in your browser and performs functions such as recognizing you when you return to our website and helping our team to understand which sections of the website you find most interesting and useful.


To see a full list of the cookies we use and learn more about their purposes, visit our Privacy Policy.