Flaky workflow?

Has anyone experienced problems with intermittent triggering of workflows?

We have a workflow set to trigger on the "Save and Close" or "Close" command from a DCT. The problem is, that the workflow is not consistently kicked off. I haven't identified a pattern for when this does/does not happen yet, but if I do I'll post.

Just wanted to see if this was something that others have experienced. Thanks in advance for your help!

Find more posts tagged with

Comments

mogoo

Is it intermittent with the same user, or different users? Same roles or different roles? If it's different users/roles, I'd look at available_templates.cfg -- someone might be exempt from that particular wf.

akshathp

One reason that the workflow might not be getting triggered could be related to user roles. I am not sure if in your tag in available_templates.cf you have included the "role_list" tag or not. The syntax is as follows:
<role_list>
<role value='editor' include='yes' allusers='yes'/>
<role value='all' include='yes' allusers='yes'/>
</role_list>

This tag controls the user role and checks whether a workflow is avaibale to the user in existing session or not. So the case could be that you must be testing the workflow as a role which is not entitled as per your cfg file.

Hope this helps.
Thanks,

Akshat Pramod Sharma
Interwoven Inc.

Migrateduser

One other debug idea is to turn on debugging in the available_templates.ipl. If you open the script in an editor you will see:

my $DEBUG_MODE = 0;

change that '0' to '1' and then try running saving and closing your dcr (or have users use datacapture as normal).

This debug option will create files down in iw-home/tmp/cci/
named in the format templates.$$

I would not leave this option on all the time (creates a lot of output if you have a very active server) but it may help track down the problem. If you are using TS5.5.x the ipl was replaced with a compiled executable, but you can change to using the ipl with a setting in iw.cfg (this requires a reboot to take effect).

Adam Stoller

Just in case you didn't know... If a DCR is already associated with a job - the Close / Save & Close options will *not* prompt you to launch another job...

Also - please try to post version/environment information - there are quite a number of different releases of software out there, and involved, and it helps to know which version on which platform and in many cases with which browser, etc, to help us help you more accurately.

--fish
(Interwoven, Curriculum Development)