WFT vs. IPM and Workflow Modeler

Teamsite Version 6.7.1
Windows

We are looking to use, OOTB, Workflow Modeler for our WF needs. We have been successful in creating a workflow that functions properly on Submit and New job commands.

The time has come for us to integrate with our new templates. So far, I am reading conflicting information on DevNet and the latest manuals on the usage of both available_models.xml and available_templates.cfg.

In order for any tt_data command to kick-off (in ccStd for instance) the name of the workflow appears to be required in the available_templates.cfg file. However, no path to an IPM is valid, and frankly, wouldn't make sense anyway. Using only the available_models.xml configuration, I would expect the appropriate workflow to be spawned once a template is submitted (FINISH).

In a nutshell, when finally completing the form, and moving on to the workflow portion of the process, the actual TQWorkflow1 does not display, only what is configured in the available_templates.cfg. This seems counter-intuitive.

Any constructive help would be appreciated. And please, no RTFM attitude I've seen on this board from certain members. It isn't necessary.

Thank you in advance.

Find more posts tagged with

Comments

pdasarat

You don't need to add any entry in available_templates.cfg for the new workflow models. You have to add them in available_models.xml.

Can you post where you got this information from?...

However if you want to enable tt_data action under CC pro, you have modifiy application_custom.xml to add this action.

Pradeep

Migrateduser

You don't need to add any entry in available_templates.cfg for the new workflow models. You have to add them in available_models.xml.

Can you post where you got this information from?...

However if you want to enable tt_data action under CC pro, you have modifiy application_custom.xml to add this action.

Pradeep

Thank you for the reply.

I would have to retype it from the training manuals and notes from the class I had in Sunnyvale.

For now, we are fine with using the tt_data command/action under ccStandard, and in fact, that is where we want to use it at this time. available_models.xml is setup correctly.

Migrateduser

Another interesting thing about this. If I do NOT add the name of the workflow to the .cfg file, it will not display after clicking next from the DCR. Only what is in the .cfg will display (opposed to using only the available_models.xml).

I would have expected the tt_data command in the available_models.xml file to kickoff the workflow without even having to choose it regardles.

Migrateduser

I'm working concurrently with IW support (hasn't been assigned yet after 3 days) but I find it interesting that even in the iwutild.cfg file that they still reference the available_templates.cfg file. I suppose this is for legacy use of wft files.

I have included a snippet of this in this post.

pdasarat

Thank you for the reply.

I would have to retype it from the training manuals and notes from the class I had in Sunnyvale.

For now, we are fine with using the tt_data command/action under ccStandard, and in fact, that is where we want to use it at this time. available_models.xml is setup correctly.

If you have been to a formal training on the new modeler, then can you help me out in this post?

http://devnet.interwoven.com/forums_vb/showthread.php?t=19865&forumid=16

Pradeep

Migrateduser

Our actual problem has turned out to be a BUG in the software that we are awaiting a patch on. According to Interwoven, we are looking at a July/2007 timeframe.

Basically, the 'command' property 'tt_data' does not function correctly with 6.7.1

cc96ai

"latest manuals on the usage of both available_models.xml and available_templates.cfg."

Could you please point to the correct manuals ?
I go through WFN & WF, cant find any info on using BOTH.
Thanks

cc96ai

Finally , i found out TS will pick up the available_template,
i forgot to set to me .
....

Daily_Revenue.rptdesign