Discussions
Categories
Groups
Community Home
Categories
INTERNAL ENABLEMENT
POPULAR
THRUST SERVICES & TOOLS
CLOUD EDITIONS
Quick Links
MY LINKS
HELPFUL TIPS
Back to website
Home
Web CMS (TeamSite)
WFM - "simulate foreach"
m_rajani
I was wondering if you happen to know how to implement the following using WF Modeler. I have done this kind in WFTs, but not sure how to do it in WFM.
The client wants to send content out for translation in 3 languages. The workflow starts and give the content contributor a set of check boxen. The values are ru, jp and zn. The content contributor may select one or more, and the workflow does a few things that are identical to all three languages. For example, Tasks 11 - 14 are common. I dont want to copy and paste these tasks and use conditional links. Is there a way to do a
"foreach" loop and invoke the same set of tasks with different task variables.
For example VPATH is /default/main/JP fo jp and /default/main/RU for ru, etc.
+---------------------------------------------+
+ Task 11 -> Task 12 -> Task 13 -> Task 14 +
+---------------------------------------------+
I could use a nested workflow, however, how do I call the nested workflow 3 times. And these nested workflow can run concurrently and end independent of each other.
Thanks
Find more posts tagged with
Comments
Bill Klish
I see 2 options for this.
Leverage the new workflow model post processor that came with 6.7.1 SP1
or
Launch new workflow models using a url external task that creates a new job for each of your selected languages.
We personally use option 2 at one of our clients. Unfortunately, we had to write our own Java interface for this as Interwoven didn't provide any coverage for this in the CS SDK released with 6.7.1 (pre/post SP1).
Option 1 could work for you, but I haven't tried it. We tried using the pre-processor capability of the model and that didn't prove very useful for us.
m_rajani
Thanks Bill, would it be possible for you to post some pseudo code covering option 2?
JMcNeil
We're using a similar approach, one workflow which performs common tasks on a number of files, then a second workflow which can be invoked any number of times from the first workflow to do more specific processing. We use an external task and call the iwmodelc.bat script via the command line to start the n number of second stage workflows.