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

Workflow invocation

rpillai

Hi

I need to invoke a workflow when user is saving the DCR.
In the available_templates.cfg I have given the
command list

<command_list>
<command value="all" include="yes" />
</command_list>

But this is not working , I also tried the specific command for saving the DCR like

<command_list>
<command value="tt_data" include="yes" />
</command_list>

But this too is not working Smiley Sad

any other change I need to do . ?

Find more posts tagged with

Comments

sunil_j

Can you post your available_templates.cfg ?

Regards
Sunil

Interwoven TeamSite Consultant

rpillai

heres the available_templates.cfg

<?xml version="1.0" standalone="no" ?>
<!DOCTYPE available_templates SYSTEM './available_templates.dtd'>

<available_templates>
<template_file active="yes" name="Mkt Workflow" path="reserved/reserved_mkt.wft">
<command_list>
<command value="all" include="yes" />
<command value="tt_data" include="yes" />
</command_list>
<branch_list>
<branch value="reserved" include="yes" />
<branch value="all" include="no" />
</branch_list>
</template_file>
</available_templates>

sunil_j

Just try if this out ..

<available_templates>
<template_file active="yes" name="Mkt Workflow" path="reserved/reserved_mkt.wft">
<command_list>
<command value="tt_data" include="yes">
</command>
</command_list>
</template_file>
</available_templates>

Do not put any branch list entries and try it out.

Make some changes on the DCT, Save it and try to close, it should invoke the *reserved_mkt.wft* workflow template.

regards
Sunil

Interwoven TeamSite Consultant

Runtimes_settings.PNG

Runtimes_settings_2.PNG

Runtimes_settings_3.PNG

Sunil Mugalavally

I don't believe you can invoke a workflow on a DCR save.
tt_data command value is used to invoke WFs on hitting the DCR close button.

Anybody, please correct me if I am wrong.
-Sunil

Migrateduser

You probably could with FormAPI onSaveDone, just figure out what parameters to pass to the CGI and do a window.open passing them on the URL. It's probably better to just use tt_data though.

iwovjames

Which version of TeamSite are you using?

In TeamSite 6.0, CC Standard supports use of tt_data while CC Professional does not.

Migrateduser

You seemed to gloss over this point that CC Pro doesn't work with tt_data. Why is this? Seems like a strange thing to not include in an interface given that it was available in all prior interfaces. Interested in the reasoning behind the decision to not have tt_data active in CC Pro.

Thanks,

Jason

Migrateduser

tt_data is supported in CCStd because it fits in logically with the wizard user experience--all of the wizards have an optional step to invoke a workflow at the end. Since CCPro offers a different user experience where power users must explicitly start workflows, we decided to drop support of tt_data from that interface.

Michelle Neuringer
Interwoven Engineer

Migrateduser

Everytime that Interwoven decides to remove support for something that was previously there, it causes issues for your customers. The Web Desk Pro interface was supposedly for advanced users as well, but tt_data support was included there. I think it should also be included in CC_Pro. In fact, since you took it out, that must mean that someone out there might not want tt_data to work on cc_pro, so make it configurable. I just think it's bad design to have a functionality, but it only works in a certain UI when it could just as easily be in the other UI.

Hoping you'll reconsider your design choices in a future release,

Jason

Migrateduser

Amen to that. I wonder how Interwoven determines which customers its benefiting when they remove functionality that once was there. All of these issues could have been moot if only there was a single UI and not two UIs. I believe these issues will only get worse over time because of the fact that the 6.x UIs are separate and distinct. Functionality is bound to be added into one UI that is not in the other. Interwoven is under the bizarre misconception that people will always only use one UI and never the other. That is a huge flaw in thinking.

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

Migrateduser

I'm not sure that having 1 UI is the answer, but I do think that the core functionality should always be in both. Removing features for simplicity may be ok, but only in the UI designed for less sophisticated user (cc-std). I would never have functionality in cc-std that isn't also in cc-pro. At least have it as an option via configuration.

- Jason

ChiragK

The Other Option you have is to write ipl's that inkove Workflows from Commandline. This Ipl should be configured to be executed on the Save and Update event's on the DCR.