Discussions
Categories
Groups
Community Home
Categories
INTERNAL ENABLEMENT
POPULAR
THRUST SERVICES & TOOLS
CLOUD EDITIONS
Quick Links
MY LINKS
HELPFUL TIPS
Back to website
Home
Web CMS (TeamSite)
Available_Templates.cfg File
System
I am having a problem with my available_templates.cfg file. I have the following:
""<template_file name=" JMFE Author/Editor Submit Workflow" path="default/JMFE_author_submit_with_email_DEPLOY.wft">
<command_list>
<command value="submit"/>
<command value="tfo_workflow"/>
<command value="all" include="yes"/>
</command_list>
<role_list>
<role value="author" include="yes" allusers="no"/>
<role value="editor" include="yes" allusers="no"/>
<role value="admin" include="yes" allusers="no"/>
<role value="master" include="yes" allusers="no"/>
<role value="all" include="yes" allusers="no"/>
</role_list>
<user_list>
<user include="yes" value="jmfamily\iujftim" />
<user include="yes" value="jmfamily\iujmose" />
<user include="yes" value="jmfamily\iustej8" />
<user include="yes" value="jmfamily\teamsite" />
<user include="yes" value="jmfmaily\cemctp5" />
<user value="all" include="no"/>
</user_list>
<branch_list>
<branch value="all" include="yes"/>
</branch_list>
</template_file>
""""
The problem is that one of the users that is listed in the userlist cannot see the workflow. They are part of the admin group but they cannot see it. The only time they see it is when I change the role element for the admins to allusers="yes".
Is anyone having a similar problem? It seems like the userlist is being ignored? But it works for me when I add myself to the userlist but remove all of the role ALLUSERS=yes lines.
Thanks
Mark
Find more posts tagged with
Comments
Migrateduser
Fixed the problem. I turned on debug and I had the domain as lowercse but it was checking it against an uppercase domain. I editted the available_templates.ipl file to uppercase the expression before checking it. I am going to submit this fix to IWOV as well so that they fix their ipl file.
Migrateduser
This is probably a unix vs. windows programming issue. The correct thing to do on windows would be to make the comparison expression case insensative for windows only (case matters on unix usernames... not sure about windows).
Component.zip
Adam Stoller
There has been at least one request for this already filed - don't remember the number off-hand, but if you contact Support, they can add your customer name to the request.
There is a potential issue with going "too-far" in case-insensitivy - as it is desirable to have the same code work on both Unix and Windows (Windows usernames are *not* case-sensitive, Unix usernames are).
One could modify the available_templates.ipl file to make this work, but if you do it, remember that it is an unsupported modification and may be overwritten when applying a patch, service pack, or upgrade.
--fish
(Interwoven Senior Technical Consultant)
Component.zip