Options
  • Locked Locked
  • Replies 8 replies
  • Subscribers 8 subscribers
  • Views 1668 views
  • Users 0 members are here
Related
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Managed Properties in Compliance Kit

dejan
Hi all,

We really like using managed properties to link document of different document types based on specific properties. It works very well in bi-directional way and automatically link documents.

Recently, I have found out that automatic metadata links are made in context of the currently logged user. If I check the history of specific document where managed metadata is just updated, I can see that the new version is created in a name of a currently logged-in user checking the history. As this is actually done through backend configuration, I would expect that the new version is made by "M-Files User". This could be very confusing for end-users and especially problematic in audit logs.

Wondering why is this a case and if this is actually a bug.

D.

Parents
  • I don't have any real knowledge of the design decisions made for this module but my guess is that they have wanted to keep the logged-in user in the audit trail since it was his/her operation that triggered the update on the other object and these updates are done during the same transaction. You would have the same end result in the audit trail if the Managed Properties module was not used and the user went and manually updated both objects to create the bi-directional references.

    In audit situations it should be possible to connect these updates on the related objects by looking at the logged-in user and the timestamp in the audit trail of both objects.
Reply
  • I don't have any real knowledge of the design decisions made for this module but my guess is that they have wanted to keep the logged-in user in the audit trail since it was his/her operation that triggered the update on the other object and these updates are done during the same transaction. You would have the same end result in the audit trail if the Managed Properties module was not used and the user went and manually updated both objects to create the bi-directional references.

    In audit situations it should be possible to connect these updates on the related objects by looking at the logged-in user and the timestamp in the audit trail of both objects.
Children
No Data
M-Files
M-Files Support


© 2025 M-Files, All Rights Reserved.