OpenDeploy query

Niraj Kumar · 2024-09-04T21:16:17+00:00

There was an error rendering this rich post.

While doing publishing through command line using iwocmd command, is it possible to ignore publishing the locked files or files which are in still in edit mode?

./iwodcmd start <config filename> -k notifyActivity=yes

I read the document but couldn't find anything.

TIA,

Find more posts tagged with

TeamSite

OpenDeploy

Web Content Management

Note:

If there are Accepted Answers, those will be shown by default. You can switch to 'All Replies' by selecting the tab below.

Accepted answers

All comments

romilrose

Cannot do in OD. May be if you consider runnning your OD command via shellscript etc, then after your filelist is ready, you can loop your filelist files with /TeamSite/bin/iwlockinfo or /TeamSite/bin/iwfilestate to find if file is locked or edit-mode. Remove those files and trigger OD.

nipper

Are you using a Workflow ? There are WF parameters to autolock a file, that will cause the WF to fail if it cannot lock the file. Likely not the behavior you are looking for, but an option.

The filelist suggestion is the best approach. If you use a WF, you can have a step before the deployment that will remove any files from the task that are locked

Also, I do not think there is a way to see if a file is being edited (unless it is locked). The CLT iwfilestate shows if it is editable, but doesn't know if it is being edited.

romilrose

Yes, my bad. iwfilestate won't help to find whether file is edited or not. We can use /TeamSite/bin/iwattrib vpath modified

nipper

https://forums.opentext.com/forums/developer/discussion/comment/969375#Comment_969375

Doubt that will help either. At least if they are using a WF, the files they submit should be modified. Do distinguishing a file being worked on now, from a file that was completed before and meant to go out is likely impossible.