OOB Workflows broken in 6.7.1 SP1 ?

This is not pretty. My deployments have been failing from the config branch. I use the OOB workflow (configurable default submit, with deployment). Deployments are broken. Basically, none of the command line parameters are being read, the deploymentName was not in the old config file, needed to be added, which I did. Now the filelist and destination are blank.

Where do I go from here ?

Putting the WF in debug mode, here are the deploy steps:

[html]
6.7.1

6.7.1 SP1

[/html]

Find more posts tagged with

Comments

Adam Stoller

Clearly they've switched from using the old externaltask script to using a "urltask" script - and it's unclear if they properly transcribed the information from the original script into the web service.

If/when I get an environment to play with .... I'll be able to substantiate such things - but for now - I leave it up to you to verify...

Migrateduser

I am currently running into the same problem with my 6.7.1 SP1 install.

I found kb article 57714 that it can be fixed if you change line # 402 of wft_opendeploy.ipl from:

$deployName = "wft_opendeploy";
to:
$tmpdeployName = "wft_opendeploy";

But it's still not working correctly for me.

I'm interested to see how/if you resolved this problem?

Cheers,

-Eric

nipper

So there are a couple of options.

The unofficial way, is to use the 6.7.1 WF. That is what I did.

There is also some documentation in TS6.7.1SP1 Workflow developers guide:

1. Specify the external task URL command using the following format:
< command
v="http://servername/iw-cc/ urlexternaltask?param1=value1&param2=va
lue2"/>
where servername is the local host on which the workflow is being run, and
param=value are the user-defined parameters.
2. Add the value ClassName as a variable to the external task, for example:
< variables>
< variable key="ClassName"
value="com.corp.custom.URLExternalTaskTest"/>
< /variables>
3. Create a Java class that implements the following interface:
com.interwoven.cssdk.workflow.CSURLExternalTask
4. Place the Java class in the appropriate location relative to the following directory:
iw-home/local/config/lib/content_center/customer_src/src
For example, if you created the following class”
com.corp.custom.URLExternalTaskTest
then the full path would be:
iw-home/local/config/lib/content_center/customer_src/src/com/corp/
custom/URLExternalTaskTest.java
5. Rebuild the Web applications.
6. Add that workflow template to the available_templates.cfg file. See
“available_templates.cfg” on page 29 for more information.

Migrateduser

hmm, In that case I will go the 6.7.1 WF route as that seems easier for forward compatibility.

Thanks for the quick response!

-Eric

Aadi

I am currently running into the same problem with my 6.7.1 SP1 install.

I found kb article 57714 that it can be fixed if you change line # 402 of wft_opendeploy.ipl from:

$deployName = "wft_opendeploy";
to:
$tmpdeployName = "wft_opendeploy";

But it's still not working correctly for me.

I'm interested to see how/if you resolved this problem?

Cheers,
-Eric

Also you have to configure the corresponding "wft_opendeploy.cfg" file which has refered in "wft_opendeploy.ipl" for the variable " $wf_opendeploy_cfg".