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

How is workflow invoked?

Annad

Hi,
Although I've been working with workflow for quite a while, I never had to deal with the underlying mechanism that actually invokes the workflow.
Would someone be able to explain how the available_templates.ipl file is invoked. I looked into this file, the main funtion which is available_templates() is not actually called from within the perl script. I believe that the the wf engine is actually calling thie.
Is there anything else thats going on here that I am not aware of?

Please get back to me asap.
Thanks.
Anna.

Find more posts tagged with

Comments

Dwayne

Is there anything else thats going on here that I am not aware of?

That's a pretty open-ended question. Hard to answer since we don't know what you are aware of.

The inner workings your describing, including the processing of available_templates.ipl, should be considered a "black box" as far as workflow development is concerned. The supported way of filtering workflow templates is via available_templates.cfg. The fact that it's parsed by a subroutine defined in available_templates.ipl should be unimportant.

Having said that, of course, it must be said that available_templates.ipl is something of a special case, because, in earlier versions of TeamSite, that was the file that you needed to edit to filter the list of workflow templates. I believe that it is includeed into the perl script that builds the list of WFT files to show the user. I don't recall off the top of my head which file that is, and it may change in future releases, anyway.

--

Current project: TS 5.5.2/6.1 W2K

Edited by Dwayne on 08/24/04 01:10 PM (server time).

Adam Stoller

As you've already indicated, the underlying system calls the available_templates() function in the available_templates.ipl script / module passing in various values - which it then uses in processing the available_templates.cfg file to determine which workflows should be displayed for you to select from. The selection is then passed (I believe) to the iwwft_instantiator.cgi

If you use iwjobc, you don't go through the available_templates.ipl code.

If you have 5.5.2 SP3(?) or higher you also have iwwft_compile.ipl

If this doesn't answer your questions - perhaps you can expand on your question a bit more.

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

Migrateduser

Anna

look, what ghoti suggest.
needs to configure available_templates.cfg and iwwft_instantiator.cgi.

thanks
Rishi Gupta

Annad

Well,
basically my problem is this.
In the available_templates.cfg file I have the following:

...
<template_file name="HRDC set EA" path="HRDC_wf/HRDC_update_metadata.wft">
<command_list>
<command value="tt_data"/>
<command value="all" include="no" />
</command_list>
<branch_list>
<branch value="all" include="no"/>
<branch value="/internet_hrdc-drhc/main/ab_nwt_nu-ab_tno_nu" include="yes"/>
<branch value="/internet_hrdc-drhc/main/bc_yk-cb_yk" include="yes"/>
<branch value="/internet_hrdc-drhc/main/ab_nwt_nu-ab_tno_nu" include="yes"/>
<branch value="/internet_hrdc-drhc/main/common-commun" include="yes"/>
<branch value="/internet_hrdc-drhc/main/gateways-passerelles" include="yes"/>
<branch value="/internet_hrdc-drhc/main/mb" include="yes"/>
<branch value="/internet_hrdc-drhc/main/nb" include="yes"/>
<branch value="/internet_hrdc-drhc/main/nl-tnl" include="yes"/>
<branch value="/internet_hrdc-drhc/main/ns-ne" include="yes"/>
<branch value="/internet_hrdc-drhc/main/on" include="yes"/>
<branch value="/internet_hrdc-drhc/main/pe" include="yes"/>
<branch value="/internet_hrdc-drhc/main/qc" include="yes"/>
<branch value="/internet_hrdc-drhc/main/sk" include="yes"/>
<branch value="/extranet_hrdc-drhc/main/unions_syndicats" include="no"/>
<branch value="/extranet_hrdc-drhc/main/IT-TI" include="no"/>
<branch value="/internet_gc-ca/main/service-canada" include="no"/>
<branch value="/intranet_hrdc-drhc/main/nh-ac" include="no"/>
<branch value="/interwoven/main/training-entrainement/WORKAREA/basic_workflow-acheminement_du_travail_de_base" include="yes"/>

</branch_list>
</template_file>
...

So this workflow should be invoked everytime the 'Save&Close' button is pressed on the DCT. However, it works only for some DCRs. If the file name (or the file path) contains the word 'all' in it, the workflow is not invoked.

I checked the available_templates.ipl file which writes some comments to a log file in iw-home/tmp/cci/template##.log However when a DCR (with the word 'all' in the file name or file path) is 'Saved and Closed' the log file is not even touched.

Any idea how to track down to the place where the workflow initiator decides not to run the workflow.

Thanks for your help.

-Anna
HRDC

Jeremy

Anna,

Could the DCR already be in a workflow when you click Save & Close? I think tt_data would not kick off a workflow if that DCR was already in a workflow.

Could that be the problem?

Jeremy

Annad

No.
I know that the workflow will not run if the DCR is in a workflow already.
I tested a file named 'Call_proposal' which is not in any other task, and the workflow still did not run

Thanks.

Dwayne

Looks like a bug in available_templates.ipl to me. The special case "all" value is being compared against the vpath, just like all the "normal" entries.

I beleive that you should be able to work around this by simply removing the "all" branch reference. But I'd still file it as a bug with Interwoven.

--

Current project: TS 5.5.2/6.1 W2K

Adam Stoller

Don't use "all" for branch values, branch values are regex's and as such "all" doesn't make sense the same way it does for things like roles, users, and commands.

You can *try* putting a 'negative' rule at the BOTTOM - something like <branch value=".*" include="no"/> - though it might be better to find more definitive patterns to use.

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

Dwayne

Don't use "all" for branch values

Except that available_templates.dtd at least implies that "all" is an appropriate value, since it lists it as the default value. If it's not a bug in available_templates.ipl then its a doc bug, IMO.

(followup rant) I personally think that Interwoven made a bad design decision in "overloading" the value attribute to include the "all" functionality. It would have been much cleaner to have a separate boolean attribute for this.

--

Current project: TS 5.5.2/6.1 W2K

Edited by Dwayne on 08/25/04 06:28 AM (server time).

Annad

Thanks so much to Ghoti and Dwayne for your help.
I changed the line "<branch value="all*" include="no"/>" to "<branch value=".*" include="no"/>"

AND IT WORKED. THANK ****.

I did file this as a bug to Interwoven. Hopefully next service pack fixes it.
Thanks again.

-Anna
HRDC

Annad

Thanks so much to Ghoti and Dwayne.
I changed the word 'all' in the branch list to '.*' and IT WORKED. THANK ****.

I did file a bug case to Interwoven about this.

Regards,
Anna,
HRDC