Editing locked files on TS 7.2.1

Hello All,

Currently, you cannot edit a locked file in TS 6.7.1. Edit link is grayed out. Now on TS 7.2.1 you can open a locked file, you do receive a message who is currently modifying the file but you can continue through and modify it, save it, regenerate it but not submit it.

Do any one of you have the same issue?
Windows 2008 64 bit VM ware.

Taalgaard?

Find more posts tagged with

Comments

ISCBorisB

Hello All,

Currently, you cannot edit a locked file in TS 6.7.1. Edit link is grayed out. Now on TS 7.2.1 you can open a locked file, you do receive a message who is currently modifying the file but you can continue through and modify it, save it, regenerate it but not submit it.

Do any one of you have the same issue?
Windows 2008 64 bit VM ware.

Taalgaard?

This is not new 7.2 feature...

What is your Branch locking mode? If it is "Submit", users in different WAs can edit their
local versions even if the File is locked. They won't be able to submit though until Lock
owner releases it one way or another

Jenni

Hi Boris,

I verified that the locking model is 'Submit' on both the servers (old and new).

I have the following config in iw.cfg for the new server

submit_lock_on_edit=true
optional_write_lock_on_edit=true
only_lock_owner_creator_submits=false

Is there any settings that I need to tweak in?

ISCBorisB

Hi Boris,

I verified that the locking model is 'Submit' on both the servers (old and new).

I have the following config in iw.cfg for the new server

submit_lock_on_edit=true
optional_write_lock_on_edit=true
only_lock_owner_creator_submits=false

Is there any settings that I need to tweak in?

I'm not sure I've made myself clear. What you've described as a "Problem" is in fact an intended
and documented behavior of the "Submit" Locking Mode. There is nothing you can do about that.

You can certainly re-create a Branch with the different locking Mode (it *seems* that you may
want "Mandatory Write" locking) but that's about it. I do not believe that you can simply change
locking mode of the existing Branch.

Now, it looks like the flags you've listed modified standard locking behavior of your previous
6.7 TS Instance. You can always open up a support case indicating the fact and requesting
guidance for the 7.2. Note though that these flags are undocumented (at least one is from
V6.5 days if not earlier) and as such are subject to change without notice.

Migrateduser

Hello All,

Currently, you cannot edit a locked file in TS 6.7.1. Edit link is grayed out. Now on TS 7.2.1 you can open a locked file, you do receive a message who is currently modifying the file but you can continue through and modify it, save it, regenerate it but not submit it.

Do any one of you have the same issue?
Windows 2008 64 bit VM ware.

Taalgaard?

My locking model on my branch is "Submit".

When I click Edit, it alerts me that someone else has the file locked, but it does not open up the DCR. I get brought back to the folder structure in the GUI.

nipper

Bo's point is that the 6.7 version of your branch was a different locking model. Probably mandatory write lock.

Jenni

I'm not sure I've made myself clear. What you've described as a "Problem" is in fact an intended
and documented behavior of the "Submit" Locking Mode. There is nothing you can do about that.

You can certainly re-create a Branch with the different locking Mode (it *seems* that you may
want "Mandatory Write" locking) but that's about it. I do not believe that you can simply change
locking mode of the existing Branch.

Now, it looks like the flags you've listed modified standard locking behavior of your previous
6.7 TS Instance. You can always open up a support case indicating the fact and requesting
guidance for the 7.2. Note though that these flags are undocumented (at least one is from
V6.5 days if not earlier) and as such are subject to change without notice.

Changing the locking model to 'Mandatory Lock' worked. Looks like the customizations we had on the 6.7.1 was overridding the 'Submit' lock. Thanks for the pointer.

Jenni

My locking model on my branch is "Submit".

When I click Edit, it alerts me that someone else has the file locked, but it does not open up the DCR. I get brought back to the folder structure in the GUI.

We do not have this behaviour though we are having the 'Submit' lock model on 7.2.1. TS allows us to edit the DCR.

Jenni

Bo's point is that the 6.7 version of your branch was a different locking model. Probably mandatory write lock.

Nipper,

I verified again on multiple branches (6.7.1). They were all 'Submit' lock.

Adam Stoller

I believe you will get different file-is-locked behavior if you are using multiple workareas on a single branch vs. a single workarea on a single branch; and in the first case - whether you are trying to edit the file within the workarea in which it was locked by someone else or if you are in a different workarea than the one in which the file was locked.