available_templates.cfg

We came across a problem where we have almost 30 workflows on one server, the available_templates.cfg file is increasing and when a user wants to create a job he has to go and look for there department job.
Is there and way I can group these departments into a heading and list the workflows under each department
for example can i group all workflows for chociecare network under the HEADING called "CHOICECARE NETWORK" . If I can what is the Syntax??
or
can i have multiple available_templates.cfg files

Thanks
manju

Find more posts tagged with

Comments

Migrateduser

I'm not positive, but I think the answer to both of your questions is "no". However, if you want to limit the number of workflows visible based on user names and/or roles - that can be done via available_templates.cfg.

I would be interested in knowing if you can do what you desire.

David M. Doggette
Certified Interwoven Consultant

manju166

Thanks and I appreciate your response.
Instead of roles and users I categorized the workflows by branches and
the user has to go to the particular branch to create the job ,thats good and
i want the samething but what's happening is when user goes and creates the
job from "corporateintranetbranch"(look at the example below) he still sees
all the workflows.

<template_file name="Create or Update CorporateIntranet Departments Site" path="CorporateIntranet/corporate_ID.wft">
<command_list>
<command include="yes" value="new_job"/>
</command_list>
<branch_list>
<branch include="yes" value="CorporateIntranetBranch"/>
</branch_list>
</template_file>

Is there any other way where i can make the particlar branch user to see
only there workflows with out including branch list code in other workflows
(i mean i dont want to include the branch list code in the example below.
<template_file name="Create Elink Releases" path="ElinkNews/create_elinknews.wft">
<command_list>
<command include="yes" value="new_job">
</command>
</command_list>
</template_file>

I tried to do this but didnt work(please look at the example below.)

<template_file name="Create or Update CorporateIntranet Departments Site" path="CorporateIntranet/corporate_ID.wft">
<command_list>
<command include="yes" value="new_job">
</command>
</command_list>
<branch_list>
<branch include="yes" value="CorporateIntranetBranch"/>
<branch include="no" value="HumanaGoldBranch"/>
<branch include="no" value="IntranetNewsBranch"/>
<branch include="no" value="ElinkNewsBranch"/>
<branch include="no" value="PressReleasesBranch"/>
<branch include="no" value="ProviderBranch"/>
<branch include="no" value="VisitorsBranch"/>
</branch_list>
</template_file>

If there is no way I think I have to include the branchlist part in all the workflows
and I dont support all of the workflows

mogoo

our templating.cfg looks pretty much like yours, and the wfs only show up in the branches they're supposed to. The only difference I see is that we always include an "all" rule in it's respective list (then you don't have to list out each and every branch)...
<command value='all' include='no' />
<branch value ='all' include='no' />
...it is listed in the TS manual that way; maybe the all rule has to be there? Hope that helps...
maureen

manju166

I tried your way but it didnt work, it still shows all branches and as well as my branch workflow when i am in my brnach.
if i am in main workarea it dosent show mine, which is good
but still can u please be more specific by giving me a example.

thanks
manju

mogoo

Manju-
here's a complete example... this WF appears only in BranchA and BranchB, and to all roles besides authors. Hope it helps...
maureen

<template_file name='Submit WF' path='custom/content_submit.wft'>
<command_list>
<command value='submit' />
<command value='all' include='no' />
</command_list>
<branch_list>
<branch value ='BranchA' include='yes' />
<branch value ='BranchB' include='yes' />
<branch value ='all' include='no' />
</branch_list>
<role_list>
<role value='author' include='no' allusers='yes'/>
<role value='all' include='yes' allusers='yes'/>
</role_list>
</template_file>

manju166

Thanks Maureen.