Locking Model

becool321

Hi Guys,

I know the documentation say locking model cannot be changed once its created on branch, but just wanted to ask.

My production branch and release branch workflows are using same external task to lock files, but locking models are different: submit on prod and mandatory write on release which leads to believe my workflow failures (error locking file) on release branch are due to mandatory write locking model.

Please Advise.

Thanks,

Adam Stoller

Hi Guys, I know the documentation say locking model cannot be changed once its created on branch, but just wanted to ask. My production branch and release branch workflows are using same external task to lock files, but locking models are different: submit on prod and mandatory write on release which leads to believe my workflow failures (error locking file) on release branch are due to mandatory write locking model. Please Advise. Thanks,

It's certainly possible. I think you need to try to find more explicit information about the errors and whether the files that generate these errors are already locked by someone else, or not locked at all.

In the first case (locked by someone else) you may have to either provide a detailed report of who has what locked and send it out as email (which could then go to a usertask, which could then go back to the submit process and try again) - or you write code that explicitly unlocks (and perhaps re-locks) the files - before going to the submittask.

In the second case, if it turns out to be an issue - it's kind of the same thing as the end of the last suggestion, write some code that explicitly locks all the relevant files before attempting to do a submit.