Privileges for users to Cancel Checkout files checked out by other user

What should be the privileges , Extended privileges and client capability of a user for doing cancel checkout in Webtop?

I think only user with superuser privilege can cancel checkout files which are checked out by other user.

Could anyone help me out on how can we cancel checkout files by giving privilege other than Superuser to a user...

Please reply....asap

Regards,

Swarup

Find more posts tagged with

Comments

Viswa

I guess only the object owner or super user can perform cencel checkout operation

Imran_Yusubov

Super user.

DCTM_Guru

We got around this problem by creating a custom method and configuring it to "run as server". Any user can call method and the method executes as install owner. Method can be called by WDK action or workflow.

Viswa

//We got around this problem by creating a custom method and configuring it to "run as server". Any user can call method and the method executes as install owner. Method can be called by WDK action or workflow.//

Good programing logic Johnny

sameeksha

Hi Jonny,

Could you please send us the detail steps you followed to accomplish this task.

We are also facing the same issue and we are in urgent need of the same.

Any kind of help would be greatly appreciated.

Regards

-Sameeksha Sharma

msroth

I would caution you about letting someone other than the lock owner cancel a checkout. Such an action could goof up an object's version tree and really upset users. Cancelling someone else's checkout should be an administrator's job and only after sufficient coordination with the lock owner.

DCTM_Guru

Scott,

Can you provide details on why canceling a checkout could "goof up" an object's version tree? Obviously, if the original person has modified the document locally and someone cancels his/her checkout, the author would have to check it out again. His previous changes should still exist on his local computer, but he would need to locate and checkin from file system (vs default checkin), since the new checkout will create new copy of the original version. Now if a newer version is checked and the original person wants to make edits to it, he will have to merge his changes with the newer version.

This is process can be "convulated", but I dont see it messing up the version tree. The alternative, having the document locked, until admin person gets in contact with that person (who may be on vacation) was not acceptable for my client's project.

-Johnny

msroth

Johnny,

Every situation is certainly different; however, I believe that users cancelling each other’s checkouts is not the norm and still advocate against it. When I made my comment, I envisioned a scenario similar to what you described, but with the frustrated user checking out/in a previous version and branching the version tree. When I said “goofed up” I didn’t mean to imply that the version tree would be broken and require database surgery to repair it. I simply meant that the version tree could become a version bush. Perhaps "goofed up" was too glib a statement, sorry, "convoluted" is probably more accurate.

--Scott

DCTM_Guru

Thanks Scott for your view point. I do agree that this shouldnt be the norm, but you know how sometimes customers want to do things their way.

gyanus

Hi Johnny,

It would be very helpful if you would elaborate on the above statements. If possible could you share any related code.

Could you shed some light on how to achieve cancel checkout for a particular role(users with non-superuser privilege) through customization.

We are really not able to achieve the cancel checkout. Plz reply...very urgent....asap

Thanks in advance

Regards,

Swarup Moulik

DCTM_Guru

I dont have access to this code any more. All you need to do is to write a server method and then pass in the object ID of the document that you want to cancel the checkout on.