nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Prevent any locking in Branch

System

I have a requirement to prevent any locking at all in a particular branch.

I have tried the three locking models and each of them lock files.

Submit
Mandatory Write
Optional Write

When users import a new file it automatically places a lock onto the file. How can I remove locking entirely from a branch?

Find more posts tagged with

Comments

kaalraa

I have a requirement to prevent any locking at all in a particular branch.
I have tried the three locking models and each of them lock files.
Submit
Mandatory Write
Optional Write
When users import a new file it automatically places a lock onto the file. How can I remove locking entirely from a branch?

Locking is a mandatory mechanism / property for a branch. You cannot change or remove the locking from a branch once created.

In case you dont want the imported files to get locked, you can catch it thru iwat event and update as per your script.

nipper

File an enhancement request. That is not supported.

Now a couple ways to fix what you want to do are:

A) write a trigger that runs on a lock and unlocks it

b) remove the import menu item and substitute it with a custom menu item that first does an import and second unlocks said file.

That being said, you requirement for no locking is very strange to say the least. There could be some valid reasons for that, however it very well could be a serious design or training issue. Locks are a good thing. Using them is a good idea.

Dinner at GearUp says that this policy will cause some problems. Want to take that bet ? Smiley Very Happy

Andy

Migrateduser

I think the only way to change the locking after the Branch is created is to delete it and re-create it. At least that's according to the Admin guide.

The type of locking a branch uses cannot be changed after the branch has been
created

You got me thinking about the iwatlock command though. I might have to look into writing something that will unlock any file in that branch after it's locked.

kaalraa

I think the only way to change the locking after the Branch is created is to delete it and re-create it. At least that's according to the Admin guide.
You got me thinking about the iwatlock command though. I might have to look into writing something that will unlock any file in that branch after it's locked.

Thanks for re-phrasing and to understand my posting it in a correct way. However, if you can, please explain as what was the requirement behind the usage of a branch with No locking mechanism. Smiley Happy

Migrateduser

If a user is out sick or on vacation they want to be able to work on the file without having to unlock it. They do not like the locking of the files. I know that it's better to have locking in order to prevent user from deleting or writing over others files. But, in their case all they are working with is images that they upload and submit. No txt based files or DCRs.

nipper

If a user is out sick or on vacation they want to be able to work on the file without having to unlock it. They do not like the locking of the files. I know that it's better to have locking in order to prevent user from deleting or writing over others files. But, in their case all they are working with is images that they upload and submit. No txt based files or DCRs.

I agree for images you can bail on the lock. You should set up a trigger for that branch, once a lock is created, remove it.

I am still uncertain why the users care. If I upload a replacement image, the lock will be removed when the submit happens.

Point taken on the sick/vacation, however that is the exception rather than the rule. Why are people uploading images and not submitting them before vacation ?

Look into that question and then decide the appropriate response. Often there is a WF problem (maybe an external tasked died & the WF hung).

Andy

Migrateduser

Okay,
I'm close to finishing up the solution. I am currently running the following from a command prompt on the server.

d:\iw-home\iw-perl\bin\perl.exe iwatlock.ipl d:\iw-home\custom\custom_unlock.ipl

However, since it is a non-terminiating script, it just sits there. It's working properly and unlocking the file that.

But, how should I start this script up. As I stated, I am running it from a command prompt while using Remote Desktop. If logout (I can only access the server with Remote Desktop) then the command will die.

I'm missing the simple piece of the puzzle. How should I call the iwatlock.ipl file? Should I be creating it as a service? I'd rather not, since that involves getting our server support involved.

nipper

You can use DOS scheduler to do that or you can run it as a service (though I have never done that).

Still better is to use a TS trigger, edit iw.local file and on the lock command run your script.

Migrateduser

Cool, that worked using the iwat command (That was my first time ever using the iwat command).

Migrateduser

Still better is to use a TS trigger, edit iw.local file and on the lock command run your script.

You're suggesting that I add something to my iw.cfg file, correct. All I see is how to add logging of an event to the iw.cfg file in the documentation.

Can you give me an example?

ISCBorisB

You're suggesting that I add something to my iw.cfg file, correct. All I see is how to add logging of an event to the iw.cfg file in the documentation. Can you give me an example?

It's iwlocal.cfg, not iw.cfg. You can not use it, that's Unix specific element.
This configuration file does not exist in Windows (since Bill Gates does not know what "signal" is...)

So, in Windows you have 2 choices:
1. Use iwat - that you already did. That's it, you are done.

2. In some rare cases where you have to obtain and parse event object iwat is not sufficient.
In this case you create/register Windows Service from desired iwatxxx trigger.
You do not need these complications in your case.

nipper

It's iwlocal.cfg, not iw.cfg. You can not use it, that's Unix specific element.
This configuration file does not exist in Windows (since Bill Gates does not know what "signal" is...).

Sorry my bad, I forgot that was only on Unix

Andy

Migrateduser

Looks like I have what I need. I'm going to have to startup the iwat command from a Windows service. Unfortunately, this will require pulling teeth in order to get our admins to do it.

Thanks everyone for all your assistance.

ISCBorisB

I'm going to have to startup the iwat command from a Windows service.

Don't. You are done. iwat configuration is kept in iwstore. It'll work *automagically* upon reboot for example.
Note however that the same is not true for other iwat<event> triggers

Migrateduser

Got it. Thanks ISCBorisB.

cssexample.zip