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

available_templates.cfg issue

hkers

Hello:

We had just upgrade from TS 5.5.2 to TS 6.5, and we are having issue w/ the available_templates.cfg.
In the previous version, we are using <branch> tag to limit the user to see a specific workflow based on which directory they are submitting the DCR. However, this does not work anymore after the upgrade.

Here is an example:

<template_file name="**** Workflow" path="****.wft">
<command_list>
<command value="submit">
</command>
<command value="tt_data">
</command>
<command value="new_job">
</command>
<command value="all" include="no">
</command>
</command_list>
<role_list>
<role value="all" include="yes" allusers="yes">
</role>
</role_list>
<branch_list>
<branch value="/default/main/X/WORKAREA/templatedata/Y/Z" />
<branch include="no" value="all" />
</branch_list>
</template_file>

The error we are getting is:

Could not find available submit workflow templates for user **** (master, users)

It is not filtering the workflow with the category/data-type directory. We had tried many different ways, the only way it works is by just putting the branch value up to the branch name, ie.

<branch value="/default/main/X" />

Does anyone encounter similar issue with TS 6.5? If YES, please shed us some light on this issue.

thanks,

Peter Smiley Happy

Find more posts tagged with

Comments

Adam Stoller

For which command-type were you trying this:
- submit
- new_job
- tt_data

From which UI were you trying to do this:
- CCStd
- CCPro

With respect to which UI - where in the UI / what mode ? i.e.:
- workflow portal (ccstd)
- workflow tab (ccpro)
- content tab (ccpro)
- closing Edit DCR window (ccpro or ccstd)
- etc.

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

nipper

Which UI ? STD or Pro ?

You may want to post the available temp.cfg

I just did a 6.5 install & that piece worked perfectly. Double check your names.

Andy

hkers

Hello Andy:

Command: submit
UI: CCPro (when hit the "submit" tab button)

This is an know bug issue in TS 6.1 and it was fixed in SP2.
Here is the bug description:

56139 <branch> element in available_template.cfg for specifying available
workflows does not work beyond branch level when its value attribute specifies a more
specific vpath.

However, we are encountering the same issue in Teamsite 6.5.

thanks,

Peter Smiley Happy

nipper

However, we are encountering the same issue in Teamsite 6.5.

Talk again to support. Too many times bugs come back after a new release. Boy
you would hope thay IW liked to use the merge utility to merge bug fixes into the
main release of code.

Andy

pratz

facing the same issue . not able to start the workflow for new_job in the workflow tab
Error message : Could not find available new_job workflow templates for user root (admin, )
when branch_list value is specified in either of the following format

<template_file name='My Workflow' path='my/workflow.wft'>
<command_list>
<command value='new_job' />
<command value='all' include='no' />
</command_list>

<role_list>
<role value='author' include='yes' allusers='yes'/>
<role value='editor' include='yes' allusers='yes'/>
<role value='admin' include='yes' allusers='yes'/>
<role value='all' include='no' />
</role_list>

<branch_list>
<branch value='/my/asia/india' include='yes' />
<branch value='all' include='no' />
</branch_list>
</template_file>

also if the branch list value is this way

<branch_list>
<branch value="/default/main/my/asia/india" include="yes" />
<branch value="all" include="no" />
</branch_list>

But if specified in the following format the workflow works fine
<branch_list>
<branch value=".*" include="yes" />
<branch value="all" include="no" />
</branch_list>

Using Teamsite 6.5 (upgrading from 5.5.2)
on Solaris 8
ContentCenter Smiley Tongue

rofessional
Role: Administrator

If its a bug is there any patch for it ?

Edited by pratz on 03/16/05 06:14 AM (server time).

Adam Stoller

This is trivial. All your branch_list specifications say:<branch value='all' include='no' />Launching a workflow from the workflow tab in CCPro and/or the Workflow portlet in CCStd is the same as launching a workflow from the To Do List in the old WebDeskPro UI -- i.e. there's no branch/workarea context - and so there are no workflows that meet the criteria you've set forth in your available_templates.cfg.

If you want to be able to launch a workflow from the Workflow tab - you would need to remove the constraint above *and* you would need to prompt for the branch and/or workarea within the WFT.

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