Attach depenedency task is notworking

Hi All,

I am creating a workflow in which I have attach dependency CGI task, but my workflow stuct at attach dependency task and don't go further. I get javascript error in CGI window (attached is the screen shot).

I have configured following two task level variables in my CGI task:
ImmediateTransition: true
TaskBeanId: workflow.task.DependencyTask

I am attaching contnet_center.log along with the post, any help will be appreciable.

Thanks,
Jitu

Find more posts tagged with

Comments

Adam Stoller

Are you starting with a copy of the PLC workflow and modifying it - or are you truly creating this workflow from scratch?

I'd suggest the former as the block of tasks at the beginning have some inter-dependencies which, if you left any of them out, might be the source of your issue.

It sucks (to use a technical term) that they went to such a "black-box" implementation, but that's what it is, so you might as well start from something that works. I tried doing something like this before (see thread) and perhaps some of the responses there will help you to understand...

g2svnit

Hi Ghoti,

Thanks for the reply!

Actually I am trying to create a workflow from scratch, in fact I have already created entrie flow, everything is working except for attach dependency task.
In my previous project I implemented a workflow with attach dependency task, it used to workfine with same configuration (which I am using currently), but this time it's giving error, quite strange!

Regards,
Jitendra

Rick Poulin

One of two things is happening..

Most likely = Your task is named 'Attach dependency' whereas your transition is probably named 'Attach Dependency Success'. Notice the case difference on the 'd'. That, or your transition isn't 'Attach dependency Success' for whatever other reason, and it should be.

Less likely = There's a bug in the deep innards of the workflow model processor that under certain very specific circumstances removes whitespace from your transition names, so that even if you correctly named it 'Attach dependency Success', your jobspec ends up with one of those spaces removed. It may appear random but it's not. It will change depending on the string length of initialization parameters including attached file paths and user names. Once you find a combination that triggers this problem, it'll always trigger it for that user+workarea+attachments combination. There's a longer explanation, but the point is that you can't do **** about it because it's so buried in the modeler, and Autonomy has told me they're not fixing it until at least TS7.4.

If you suspect the less likely scenario, run your job in debug mode and inspect the resulting jobspec for missing spaces in transition names.

g2svnit

Changing the transition name to 'Attach Dependency Success' resolved the error...lot of thanks for the pointer.
But keeping the dependency on the name of transition link seems little illogical to me Smiley Happy