Locked document and versioning

[Niki]

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

[Former Member · Accepted solution]

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

[Niki · Accepted solution]

Thanks for the feedback,

We had already opened an oss message and they told us to enable auto chekin/checkout setting on the KM Repository.

We are testing different scenario before we go to the production system.

Is there a known release date for SP 3?

[former_member206563 · Accepted solution]

SP3 is planned for mid October this year.