unlock.ipl

When using unlock.ipl to unlock workflow files, is there ever a situation that the script will exit without unlocking the file(s)?

For instance, if user A locks a file in workarea 1 then user B can not unlock that file when logged in as editor/author roles. However, it seems that user B could start a workflow that calls unlock.ipl and then successfully unlock this same file.

David M. Doggette
Certified Interwoven Consultant

Find more posts tagged with

Comments

akshathp

If a file is being unlocked via workflow, it can be unlcoked by external task IPL script. The script is not run as an editor or authro role. So, there won't be any restrictions. Hence it is critical during design of workflow to keep in mind about these factors.

Hope this helps.

Akshat Pramod Sharma
Interwoven Inc.

Migrateduser

On Windows, since external tasks run as the SYSTEM user, the unlock is always guaranteed to succeed (because SYSTEM is configured as a master).

On UNIX, the tasks run as the user in his "best" role (i.e., greatest privileges possible for that user), so it's contingent on whether that user can login with sufficient privileges to effect the unlock. Here is the logic used to test that condition (on both platforms):

User may remove the lock on a file if:
1. user owns workarea, OR,
2. user in role can modify the branch and is admin or master, OR,
3. user owns or created the lock.

--
Evers Ding
Staff Engineer, Interwoven