Capitalization Schmapitalization

Bryan_K

Has anyone tried setting up a workflow in available_templates to disallow all users except the ones expicitly listed? Example:
<user_list>
<user value="us\smith" include="yes"/>
<user value="US\davis" include="yes"/>
<user value="us\jones" include="yes"/>
<user value="all" include="no"/>
</user_list>

I have noticed that the user values are case sensitive (which, IMHO is really a pain), but thats fine, except for the seemingly random nature of when a user's domain is capitalized and when it isnt. I used to think it had to do with the way it was listed in .uid files, but now I have changed all users and domains in my .uids to lowercase and some users still have capitalized domains. This can be verified by checking what is displayed in the upper righthand corner of the screen when a user is logged in. I am running TS 5.5.2 in Win2k.

Anyone know where TS pulls this info from?

Adam Stoller

Please contact Interwoven Support and ask to have this filed.

In the meantime you can probably work-around this by [not officially supported] modifying available_templates.ipl to do a case-insensitive match of the user name.

I don't have line numbers handy - but in the subroutine "matches_criteria" - there's a bit of code that looks like this (condensed for this post):

---

  if ( $allowRegExMatching == $true ){
   if( $input =~ /$pattern/i ){
    debug ("MATCHED!\n");
    return ($result eq "yes");
   }
  }
  else {
   if( $input eq $pattern ){
    debug ("MATCHED!\n");
    return ($result eq "yes");
   }
           }

---

If you change the lower part to look like:

---

   if( lc($input) eq lc($pattern) ){
    debug ("MATCHED!\n");
    return ($result eq "yes");
   }

---

I believe it will have the desired effect. HOWEVER - it may also have undersired effects if there is anywhere within the available_templates.cfg file that you are actually counting on case-sensitivity.

--fish
(Interwoven Senior Technical Consultant)