autoprivate.cfg space in filename

I'm trying (unsuccessfully) to use autoprivate.cfg to stop any file or directory with a space in from being submitted and being marked as private.

Can autoprivate.cfg be used for this?
If so how?

Steve.

Find more posts tagged with

Comments

Migrateduser

Yes, it can. I'm not usually so bold as to say RTFM, but believe it or not there's some decent documentation about it on page 35 of the Admin manual (that is, for TS 6.1 on Windows).

Dave

Current Environment(s):
(1) TS 6.1 SP1 on W2K3
(2) TS 6.1 SP1 on W2K
(3) TS 5.5.2 SP2 on Win2K

Adam Stoller

I've RTFM - but I'm still not convinved you can do this - since autoprivate.cfg requires specific prefix and/or suffix string sequences and doesn't (to the best of my knowledge) handle regular expressions) - I don't think there's a way you can say: "Mark all files that contain white-space in their names as private".

The example given in the manual has to do with marking a specific directory name that contains spaces as private: ((Network\20Trash\20Folder))

but how do you make a single rule that would cover both "Network Trash Folder" and "My Documents" for example? I don't think it can be done given the existing implementation of the autoprivate functionality.

--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com

Migrateduser

I admit I haven't had a need for autoprivate.cfg as yet, but why wouldn't some variation of ((\20)) work? True, this matches only files named " ", but the LISP-like syntax should allow for character matching, instead of entire word matching. It's clear that this file does not expicitly employ regular expressions, but I believe one would still be able to specify a single character as autoprivate criteria.

Dave

Current Environment(s):
(1) TS 6.1 SP1 on W2K3
(2) TS 6.1 SP1 on W2K
(3) TS 5.5.2 SP2 on Win2K

fish

I trust you mean the 'foolish' manual ;-)
I appreciate your boldness, and in reply to "Yes, it can" and without meaning to sound childish "no it can't".

I think that I was misdirected by the reference to patterns and matching in the manual and the numerous pattern matching expressions I've tried based upon the examples in the docs have not worked.

Unless anyone can offer me a solution I'll have to do a workaround based upon the iwat submit trigger.

Steve.

Migrateduser

Steve,

Yeah, I found the same to be true -- I've been experimenting with it a bit this morning, mostly out of pure curiousity and education. You were right, I was wrong! The utility that autoprivate.cfg is nice, but as so many other things Interwoven, they're at the 10-yard line, just short of a touchdown. How much more useful is it to use regular expressions with this versus how much more effort could their engineers / management gone through to go the whole way?

If you're able to find a workaround, please reply with a follow-up! I know others are interested in this topic.

Thanks,

Dave

Current Environment(s):
(1) TS 6.1 SP1 on W2K3
(2) TS 6.1 SP1 on W2K
(3) TS 5.5.2 SP2 on Win2K

Adam Stoller

Unfortunately iwat triggers are POST-operative.
If you are always using a workflow for submit operations you could make sure all your workflows verify that all files attached to the job/task do not violate naming conventions before allowing the files to be submitted.

TS6 no longer provides Submit Direct and TS5.x allows you to limit who can see the Submit Direct menu option - so that helps a bit -- however the iwsubmit CLT exists in all versions and thus you would need a trigger to catch cases where someone used the CLT rather than going through a workflow.

You should probably open a FR with support to provide regex handling in autoprivate.cfg to handle this kind of situation. That, or to provide PRE-operative trigger functionality.

--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com