Unable to Invoke Work Flow

Hi,
From some of our directories under a same work area, we are unable to invoke work flow. We are getting a message "There are no templates configured. Please contact your TeamSite Administrator".

Where as same work flow works as per the requirement from the other directories under a same work area. we didn't put any constraint in "available_templates.cfg" for this.

Could any one throw some light on this.

Thanks in advance.

Find more posts tagged with

Comments

Migrateduser

It would help if you attached your available_templates.wft file and also posted the exact directory you are attempting to invoke a workflow from.

Dave Smith
Sr. Software Engineer
Nike, Inc.
(503) 671-4238
DavidH.Smith@nike.com

s6634

Attached the "available_templates.cfg" file:
<?xml version="1.0" standalone="no" ?>
<!DOCTYPE available_templates SYSTEM './available_templates.dtd'>

<available_templates>
<template_file name='Submit Workflow' path='wft/Submit.wft'>
<command_list>
<command value='submit' />
<command value='all' include='no' />
</command_list>
<role_list>
<role value='author' include='yes' allusers='yes'/>
<role value='all' include='yes' allusers='yes'/>
</role_list>
<branch_list>
<branch value='all' include ='no' />
<branch value='/Internet/' include ='yes' />
</branch_list>
</template_file>

</available_templates>

Migrateduser

Is your wft file in the directory

.../iw-home/local/config/wft/wft/Submit.wft

That's how you've defined it. And you didn't show the path you are trying to invoke the workflow from.

Dave Smith
Sr. Software Engineer
Nike, Inc.
(503) 671-4238
DavidH.Smith@nike.com

s6634

Work flow Path: .../iw-home/local/config/wft/wft/Submit.wft

Path from where I was unable to invoke work flow:
/iwmnt/default/.../Internet/week/events
Path from where I am able to invoke the work flow:
/iwmnt/default/.../Internet/week/issues

Our version is 5.0.1 on Solaris
Thx,

Adam Stoller

Not sure if this will help - but you might try changing:
<branch_list>
<branch value='all' include ='no' />
<branch value='/Internet/' include ='yes' />
</branch_list>
to:
<branch_list>
<branch value='/Internet/' include ='yes' />
<branch value='all' include ='no' />
</branch_list>

I seem to recall (not looking at the code right now) that some of these directives are processed in a top-down manner such that the first 'match' wins. Of course this doesn't explain why it works for one of your paths and not the other, but it still might be worth a try.

--fish
(Interwoven Senior Technical Consultant)

s6634

Thanks a lot Fish. It worked after changing