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

Nested Workflow Call

kshitiz

Hi,

In a workflow there is a nested workflow. Is it possible to make a transition to the nested workflow without user interaction i.e. the task that the user gets in the to-do list to start the nested job shouldn't come.

Cheers!
Kshitiz

Find more posts tagged with

Comments

Adam Stoller

What version of TS (including SP level)?

Are you a wftfile or a jobfile with the wftask?

I believe it will run immediately with jobfile, but not with wftfile - or at least it might depend on the version of TS being used - as I recall that being a limitation that was noticed early on, but I don't recall if/when it was fixed to behave more like a cgitask (the same restrictions would apply with regard to immediacy) - and a quick look at the 6.1 documentation and iwwf.dtd would seem to imply that this has still not been "fixed" - so I guess the answer is: jobfile = immediate, wftfile = manual step required.

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

kshitiz

Hi

I'm using TS 5.5.2 SP3

I'm using a wft file to call the nested job. Is there no way that the task of Starting Nested Job in To-Do list can be removed.

thnx
KS

Adam Stoller

Not that I know of - and if you did remove it - how would you expect someone who is supposed to start the nested job to do so?

The only alternative I can think of would be to create your own cgitask script, put an interface in there for what you want to prompt for in terms of data for the workflow instantiation, and then call iwwft_compile.ipl from within your cgitask script. This would be "immediate" if the cgitask satisfies all the other requirements for immediacy, but you probably will not have the general parent-child relationship that wftask initiated jobs have unless you create it yourself.

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

Migrateduser

I believe that version 6.0 was the first version that allowed for a nested workflow, using <wftask> could be initiated without manual intervention. But it's still not documented - what a shocker. It is, however, in the DTD for workflow and it is a flag you put in the <wftfile> tag:


<!ELEMENT wftfile EMPTY>
<!ATTLIST wftfile v CDATA #REQUIRED
background (t|f) "f">

Basically, if you set the background attribute to "t", the nested workflow will kick off automatically. This works - I've used it.

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

Adam Stoller

Thanks Smitty - I thought I remembered something about this happening - but foolish me - I was looking for "immediate" not "background" when I looked at the DTD.

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

nipper

Really sad when you need to read the DTD for the documentation.

Very good pickup Smitty.

That will come in handy.

me

brandon1

Not to sound like a Teamsite drone, but a DTD is considered documentation.

Current Project: Content Services implementation

nipper

>Not to sound like a Teamsite drone, but a DTD is considered documentation.

So are manuals.

Migrateduser

I call BS on that one. The crappy Workflow manual includes the full text of the DTD, but they haven't updated it in a very long time. If you put the DTD in the manual, the correct info should be in the manual. Also, every other attribute for the workflow XML is in the manual - described in words to some extent even. Why wouldn't I expect the new ones to be in there as well? Telling me to always check the DTDs whenever a new version of TeamSite comes out is an absolute waste of my time. Give me a decent manual and I wouldn't need to look at a DTD ever.

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

Migrateduser

Oh I didn't find this in the DTD at first. I **** and moaned about this problem almost couple years back now because I was working on that behemoth of a nested workflow and the customer just refused to have to kick off the nested jobs manually. After much fuss, emailing IW engineers directly, they came up with the background attribute and I received the DTD info via email. When I got the 6.0 manuals, however, there was no mention of the attribute in the docs and I **** and moaned again (hard to believe, I know). The response I got was it was in the DTD and they created a documentation bug. And you and I both know what the document fairy does when a workflow documentation bug gets created. Hence the "DTD = documentation" ****.

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

milind

I believe that version 6.0 was the first version that allowed for a nested workflow, using <wftask> could be initiated without manual intervention. But it's still not documented - what a shocker. It is, however, in the DTD for workflow and it is a flag you put in the <wftfile> tag:


<!ELEMENT wftfile EMPTY>
<!ATTLIST wftfile v CDATA #REQUIRED
background (t|f) "f">

Basically, if you set the background attribute to "t", the nested workflow will kick off automatically. This works - I've used it.

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

Hi,

I am using TS 6.5 on windows 2K. Tried following with no luck.
<wftfile v = "wfb/Review_immediate.wft" background="t"/>
Also in DTD background attribute was missing.
<!ELEMENT wftfile EMPTY>
<!ATTLIST wftfile v CDATA #REQUIRED>

Tried to modify DTD and added backgroung attribute keeping default value as "t" doesn't help either.

Regards,
Milind

Adam Stoller

Hi,

I am using TS 6.5 on windows 2K. Tried following with no luck.
<wftfile v = "wfb/Review_immediate.wft" background="t"/>
Also in DTD background attribute was missing.
<!ELEMENT wftfile EMPTY>
<!ATTLIST wftfile v CDATA #REQUIRED>

Tried to modify DTD and added backgroung attribute keeping default value as "t" doesn't help either.

Regards,
Milind

What DTD are yout looking at? I just looked at IWHOME/local/config/wft/iwwf.dtd on a 6.5 Windows system and I see background listed as an attribute of wftfile.
Also - changing the DTD won't help anything - Interwoven provides those DTDs as reference for the most part and almost never actually uses them as such - they tend to be coded in the software rather than read from a file.

milind

Hi,
I was looking at the same DTD, but anyways setting "background" attribute should start the workflow immediately !. Don't know why it's not starting it.

Regards
Milind