DFS UCF Checkin, not-hardcoding path?

gdriessen

Hi all,

When checking in a document in webtop usign UCF, the UCF client is able to retrieve the filepath based on the ID that is passed on, i.e. the exact location is not know beforehand.

When using DFS to check in a document over UCF and only providing the ID, we do get a new checked-in version, but the content is not checked in. In the documentation it is shown that we can use a strLocalPath string to locate the content, but as it is stored in the documentum.ini in the UCF folder, we do not want to use that.

Can you please advise on how to do the checkin without have to indicate the full path on the client?

Thanks in advance.

Burlacu_Dorin

Hi,

UCF has it's own file registry of viewed and checkedout documents and predefined directories to save these files.

Usualy the files are saved under the %DOCUMENTUM_SHARED%/checkout.

When you checkin a document using only the ID, UCF will chekin the content of the file under that directory.

I need your client code to say what you are doing wrong,

but it looks like you get the Content provided by UCF and save it in some custom location and modify the file from the custom location (the file that is created by UCF is still stored under the checkout directory). On the checkin the registries of UCF does not know about other file than the one in the registry i.e the one from %DOCUMENTUM_SHARED/checkout.

As a solution:

You could send with your request besides ID of the document by means of any DFS Content.class (you do not need to modify the document.ini in this case) the path/content of the file you've modified, in this case the content you will pass will be checked in.

You could modify the file in the checkout folder and it will be picked up by UCF.

You could alter UCF registry to point the file you've modified (I'm not sure how this is achieved)

If you still have questions please send also the client code and detailed actions of the user.

Regards