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; } } }

createfse_filter

Valentine

Do then even work? Are the ignored by the TeamSite?

I can't seem to find any reference in the documentation, just the knowledgebase article:

https://support.interwoven.com/kb/kb_show_article2.asp?ArticleID=1458

The question is, when creating the event filter, what is being matched against the regex, is it the full vpath?

Find more posts tagged with

Comments

Adam Stoller

Do then even work? Are the ignored by the TeamSite?

I can't seem to find any reference in the documentation, just the knowledgebase article:

https://support.interwoven.com/kb/kb_show_article2.asp?ArticleID=1458

The question is, when creating the event filter, what is being matched against the regex, is it the full vpath?

The regex is for the event-pattern if you look in the 6.5 (or later? or possibly earlier?) CLT manual it provides a list of the event names which you can use to compose your event pattern. e.g.:

UNIX> iwat CreateFSE /usr/iw-home/local/bin/myscript.ipl
WINDOWS> iwat CreateFSE "c:/iw-home/iw-perl/bin/iwperl c:/iw-home/local/bin/myscript.ipl

where "CreateFSE" is the event pattern to match against. If you wanted to match against all create events (files, workareas, branches) it would either be (Unix example provided only):

> iwat Create /usr/iw-home/local/bin/myscript.ipl
or
> iwat 'Create.*' /usr/iw-home/local/bin/myscript.ipl

Note the use of single-quotes above - this is to (hopefully) prevent interpolation of the '*' by the shell. On Windows I believe you'd need to use double-quotes because the Windows command prompt doesn't like single-quotes.

Valentine

umm
I think you've misunderstood.

Looking at the KB article, the regex applies to the branch, here is an excerpt from the iw.cfg:

log_createfse=yes
createfse_filter="(/default/main/Public)"

This enable the CreateFSE triggers, and limits them to the Public branch.

My question is, does it match to the branch or to the full vpath of the file that was created?

Adam Stoller

umm
I think you've misunderstood.

Looking at the KB article, the regex applies to the branch, here is an excerpt from the iw.cfg:

log_createfse=yes
createfse_filter="(/default/main/Public)"

This enable the CreateFSE triggers, and limits them to the Public branch.

My question is, does it match to the branch or to the full vpath of the file that was created?

Ah - sorry - I missed the focus being on the filter rather than setting up the trigger.

Yeah - that doesn't seem to be documented any more - last place I see it is in the 4.2.1 (yes 4.2.1) documentation:[indent]Because these events tend to produce a very large number of entries in the event log, you can prefilter each event type using regular expressions. To perform prefiltering, set createfse_filter, destroyfse_filter, renamefse_filter, or modifyfse_filter to a set of double quoted regular expressions. The event is then logged only if the full event line matches any of the regular expressions.[/indent]Based on the last line there - if this functionality still exists - the regular expression would be a match against whatever you see in the iwevents.log - so in the case of a branch function it will be a branch vpath, in the case of a publish event it will be either the vpath for the branch's staging area or the vpath for the new edition being created, in the case of unlocking a file it appears to be the vpath to the workarea and/or the relative vpath to the file in question. You'll have to look through your log file for the events to see what's being logged to help you determine what you want to use for filtering - but you probably should also contact Support to find out if this functionality still exists (and if it does, have them open up a documentation bug for the lack of its documentation).

Note also - from the above quoted documentation that