on 06-20-2014 10:23 AM
Hi,
How is it possible that a locked document can be overwritten/changed with the sap mobile document desktop client and no new version is even created?
While a new version of the document is created when the document is not locked, which is normal.
Thanks,
Niki
Hi Niki,
I assume you have enabled auto chekin/checkout setting on the KM Repository in order to enable this scenario.
This setup is more like workaround, which enables exposing KM version-ed resources for SP 02. The client applications are actually unaware, that the resource is actually version-ed in the back end and this is the main reason for it. I was able to reproduce it as well.
For SP 3 we are working on implementation for the handling of version-ed resources in KM, which should resolve the issue.
p.s. if it is currently affecting your work scenarios you can report it at component BC-SRV-MCM
Best Regards,
Radoslav Tomov
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
101 | |
13 | |
13 | |
11 | |
11 | |
7 | |
6 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.