It's all about the answers!

Ask a question

auto Locking files doesn't work properly, in the stream

Arun K Sriramaiah (3.2k13277) | asked Mar 28 '19, 8:52 a.m.
edited Mar 28 '19, 8:55 a.m.
Locking resources doesn't work properly. In the stream we defined several types of files that need to be auto-locked when edited. When editing the file for the first time, a lock dialog pops up. Locking, editing and delivering the file works oké. But then editing the file for a second time by the same user, the auto-lock dialog doesn't pop up.

The file can be edited without a lock. Sometimes first and second time do get the lock and the third doesn't, sometimes even the second time the file will not be locked.

We need help with this locking mechanism, to lock files everytime they need to be edited.

2 answers

permanent link
Arun K Sriramaiah (3.2k13277) | answered Mar 28 '19, 8:59 a.m.

Please try making the <Lock file> is the default, it helps.

permanent link
Geoffrey Clemm (30.1k33035) | answered Apr 03 '19, 12:23 a.m.

When you deliver the file, did you select "unlock locked files"?

If not, the file will remain locked following the deliver.
You can tell that this is happened if you make another change to that file, and look in the Pending Changes view ... it will annotate that unresolved file with a "Locked" icon.

Arun K Sriramaiah commented Apr 17 '19, 9:55 a.m. | edited Apr 17 '19, 9:56 a.m.

Your answer

Register or to post your answer.

Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.