Managed Properties in Compliance Kit

Hi Karl and Joonas,

Thanks for your explanation. I do agree with you: in the most cases managed properties are updated due to change on some metadata by particular user, so it makes sense that the bi-directional side (other document matched over the same metadata) is also changed in a name of that particular user because it is a follow-up action.

One other thing bothers me still: it seems that update of the managed properties happens in the same thread as actions of just changing local properties for a document. This can cause significant delays and simple updates can take more time for end users (they are not aware that M-Files synchronously search for matching documents over specific properties and than updates relation property).
I think it would be much better if matched property actions are started in a separate thread. So that users can easily change metadata, separate thread would be started to find matching documents and would than update both matched sides accordingly (bi-directional matching between documents). In that way, user experience would be not degraded with a growing number of documents and matches.

Actually, I have already written about this problem https://community.m-files.com/index.php?topic=15402.msg41714#msg41714. Our load test for uploading of documents started to be at least 3x faster after we disabled managed properties rules! With increasing number of documents synchronous searches by update of metadata will get slower and slower. Asynchronous search over matching properties (in separate thread) would be very handy and would improve this uploading significantly.

Could you consider this as an improvement for next releases of Compliance Kit?

As I mentioned above, this is such a great feature and so unique on the market (automatic document links and even on a metadata-level based on configurable rules, just awesome!)

Best regards,
Dejan

Hi Karl and Joonas,

Thanks for your explanation. I do agree with you: in the most cases managed properties are updated due to change on some metadata by particular user, so it makes sense that the bi-directional side (other document matched over the same metadata) is also changed in a name of that particular user because it is a follow-up action.

One other thing bothers me still: it seems that update of the managed properties happens in the same thread as actions of just changing local properties for a document. This can cause significant delays and simple updates can take more time for end users (they are not aware that M-Files synchronously search for matching documents over specific properties and than updates relation property).
I think it would be much better if matched property actions are started in a separate thread. So that users can easily change metadata, separate thread would be started to find matching documents and would than update both matched sides accordingly (bi-directional matching between documents). In that way, user experience would be not degraded with a growing number of documents and matches.

Actually, I have already written about this problem https://community.m-files.com/index.php?topic=15402.msg41714#msg41714. Our load test for uploading of documents started to be at least 3x faster after we disabled managed properties rules! With increasing number of documents synchronous searches by update of metadata will get slower and slower. Asynchronous search over matching properties (in separate thread) would be very handy and would improve this uploading significantly.

Could you consider this as an improvement for next releases of Compliance Kit?

As I mentioned above, this is such a great feature and so unique on the market (automatic document links and even on a metadata-level based on configurable rules, just awesome!)

Best regards,
Dejan