In Microsoft Content Management System 2002, if the state of the posting is not saved, after releasing the lock on a posting using the API, it will change the state back to Saved. Microsoft has stated this as a bug in the system. I had a situation in which I really needed to release the lock without the state change. At last I figured out an ugly way to achieve this.
= = "urn:schemas-microsoft-com:office:office"
How It Works
It directly changes the owner of the posting in the database (ugly). Because it is a direct database change, the server cache must be cleared in SCA to see the changes. By passing the GUID of the posting, the relevant Node is taken from the database and the owner of the posting is changed.
dataConfiguration.config file must be modified to point out the MCMS database name and server name.
<parameter name="database" value="mcmsdatabase" isSensitive="false" />
<parameter name="server" value="mcmsserver" isSensitive="false" />
Even though it works fine for me, please do check before using this. Because this is a direct database change, you must be very careful before using this.
N.B: Unfortunately, direct access to the MCMS database without using the MCMS publishing API breaks the Microsoft Support Boundaries for MCMS. So, if you are interested in using Microsoft Support, please don't use this.