DCR locking behavior locks on "edit" TS7.3.2

Hi,

I have applied "Set a Locking Model on a Branch" as mentioned in administration guide. But its not working as mentioned in guide.

As per this post I am not able to find in TS7.3.2 version

/t5/TeamSite/quot-lock-on-modification-false-quot-Leaves-Pages-Locked-on/m-p/150448/highlight/true#M97204

Is there any way apply this DCR lock on Edit feature for particular branch without using formAPI? Please let me konw

Regards,

arafi

Find more posts tagged with

Comments

GoingMyWay

You need to make that change in IWHOME\local\config\lib\content_center\customer_src\etc\conf\customer\application_custom.xml. Then run make_toolkit.ipl.

Is your requirement to only have this behavior in a specific branch? This is a global change that will cause all files regardless of branch to be immediately locked when Edit is clicked.

-David

arafi

Thanks David for your quick reply.

Yes, this requirement is only have this in a specific branch. But as per Admin guide it should work if apply "mandatory write lock" on branch level.

As mentioned in guide here

"Mandatory Write. Ensures that only one user can edit a file at a given time.
Users must lock files while editing them. While files are locked, no other users
in any workarea on the branch can edit their version of those files. This option
is suitable for environments where serial development is required."

Regards

GoingMyWay

I think those locking models only apply if you have multiple workareas. Even if you do have more than one workarea, the first thing is you need to put the lock on the file (in this case a DCR) as soon as the Edit button is pushed.

I think you're going to need to either use formAPI/callserver to manually lock the DCR for any DCTs within a specific branch or update application_custom.xml to globally lock any file when Edit is clicked.

Is the risk/concern of making the global change that a whole bunch of files/DCRs will accidently get locked by people who click Edit when all they really want to do is view the read-only version of the DCR?

-David

Adam Stoller

I think there are [at least] two different concepts in play here.

The branch locking model has to be set when the branch is initially created. There is also a role-related locking-model setting (sub-command for iwroleadm) which supposedly (I've never tried this) allows you to set more-restrict locking models for users with distinct roles so that (as indicated in the 7.3 Admin Guide, starting at bottom of page 56) you could have [ALL] Authors using a Mandatory Locking Model even if they're working in a branch that is set to use the Submit Locking Model.
Note: The locking model settings are not specific to branches with multiple workareas, though some settings do make more sense in such contexts.
The application_custom.xml file settings for forcing files to be locked when they are edited applies to branches with Submit or Optional Write Locking models (some info can be found in the 7.2 UI Customization Guide on page 79 - I'm assuming, perhaps incorrectly, that the settings still work in 7.4x) - you can also find information in IWHOME/local/config/lib/content_center/reference/etc/conf/ref_teamsite_application.xml

GoingMyWay

I can confirm that the application_custom.xml settings still work in 7.4.1 with the Submit locking model. I haven't tried it with Optional Write.

-David