document check in and checkout

Hi All,

I have a workflow to which has an attachment.This attachment is attached at a particular activity through code.

Now there is a requiredment that in next activity user can add an attachment...but in this case..the prveious attachemnt should be checked out and new attachment should be added as its next version..

I am using below peice of code but it doesnt help

IDfSysObject sysobj = (IDfSysObject) idfSession.getObject(idfattachmentid);

IDfClientX clientx = new DfClientX();

Here idfDoCId is the id of previous document.

Please let me know what is the issue.

IDfCheckoutOperation checkoutOperation = clientx.getCheckoutOperation();

checkoutOperation.add(sysobj);

DfLogger.debug(this, "attachment added for checkout::!!!!", null,

null); //check and execute checkout operation

(checkoutOperation.execute()){DfLogger.debug(

this, "attachment checked out!!!!", null

null

);

//check in the new attachment

IDfCheckinOperation checkinOperation = clientx.getCheckinOperation();checkinOperation.add(idfDoCId);int versionlabel= IDfCheckinOperation.NEXT_MAJOR

;checkinOperation.setVersionLabels(

"Document from SCanning"

);

(checkinOperation.execute()){DfLogger.debug(

this, "Checkin Success!",null,null

);DfLogger.debug(

this, "versionlabel is!"+versionlabel,null,null

);DfLogger.debug(

this, "The object name of new version is"+sysobj.getObjectName(),null,null

);sysobj.mark(

"Document from Backlog SCanning"

);sysobj.setObjectName(strDocumentName);

sysobj.save();

DfLogger.debug(this, "The object saved::"+sysobj.getObjectName(),null,null

);

}

Find more posts tagged with

Comments

aflowers001

So what happens?

Do you get an error message?, does it not check in a new version?, how much of the debug logging is displayed?

MonaliMukund_katarni

There are no error messages...All the debug statements are displayed..i.e checkin success etc.

But the original document is checked out and checked in....The new document which is to be added as an attachement doesnot replace the earlier object...Also the version displayed is 1.0..whcih is current

aflowers001

Ah, that would be as expected. The new document is not actually attached to the workflow. You will need to ensure that you update the workflow packages to have the new document added.

MonaliMukund_katarni

No...When i navigate to that file location , the document is not created with a new version.

DCTM_Guru

Where is then "newer" version of the document coming from? From the user's computer or from the repository located in another folder?

Your code checks out and checks in the original 1.0 code as expected. There's nothing in your code where you specify where to get the newer version of the content.

MonaliMukund_katarni

The document is exported into the same folder in the repo where the earlier attachment is present.

IdfDocid in the code is the newer version id

aflowers001

I think Johnny might have something to look into. From the code I cannot see where the 'new' version is coming from.

Can you try something simpler such as

IDfSysObject sysObj = (IDfSysObject)sess.getObject(new DfId("<your roiginal object id>"));

if (sysObj.isCheckedOut())

{

sysObj.setFile("<the path to the new version>");

IDfId newSysObjId = sysObj.checkin(false, "");

}

See if that works at all.

At the least this should breate a new version of the object in question, and then you need to ensure that your workflow then has this.

DCTM_Guru

"The document is exported into the same folder in the repo where the earlier attachment is present."

- Keep in mind, if the file already exists on the file system, I think DFC will change it (ie append it), so that it doesnt overwrite the original file. For example, you check "test.doc". This creates test.doc on the filesystem - c:\test.doc. You export newer version there and you checkin fine. However, the next time you do this (assuming you didnt delete it, then when you check it out, DFC will create test1.doc -> c:\test1.doc. Your export code is still exporting "test.doc", so when you checkin, it doesnt pull the newer version, it only checks in the CURRENT version.

As Andy suggested, instead of relying on default naming convention, explicitly define which file you want DFC to checkin.

NandhakumarSoundarrajan

The best way to startup is too build the code with simple blocks... I would recommend you to follow the setFile() as suggested by Andy instead of going for CheckinOperation...

Sequence would be as follows:

Check out the document (i.e. the attachment)
Check it back in with next version
Set the content of the documemt (i.e. your new document)
save it..