Callback not transitioning

HI,

We are running teamsite 6.1 on NT. In the wf, weve come across soemthing that I had not come across on Unix platforms. THe cgi gave a call back but the workflowtask did not transition to the next task. Ive come across NT being unreliable in executing iwgetwfobj becoz sometimes XML is either invalid or empty pr maybe connection to iwserver is not made.

Does anyone have a suggestion for a way to catch this callback from failing to transition? Or do we ahve to write a wrapper for the callback task which we are contemplating to do. This is an NT specific error.

Any ideas? thoughts? suggestions?

Regards,
kingtut

Find more posts tagged with

Comments

cliffhanger

If I understand you right, you have a workflow that was working fine in Unix, but when the same WFT got ported to NT, "A" task is not transitioning. Or am I wrong?
Either way, could you please post "cgi-task"(??) snippet of your WFT and also the cgi?

kingtut

Hi Cliffhanger,

no, this wf is implemented in NT env only. It works fine normally. Only some jobs would have this issue where the task hangs, as the callback doesnt transition to the next task

the task callback is pretty simple.
in the cgi
$task->CallBack(1, "Done");

Regards,
kingtut

WFT snippet of the task
<externaltask name="Approval4_Select"
owner="__TAG__('wf_editor');"
description='__INSERT__("$dcrSaveNames"); - Selection of 4th_Approval Task'>
<areavpath v='__INSERT__("$AreaVPath");'/>
<successors>
<successorset description='Approval'>
<succ v='Email_Group4'/>
<succ v='4th_Approval'/>
</successorset>
<successorset description='No Approval'>
<succ v='Measurement_Concurrent_Approvals'/>
</successorset>
</successors>
<command v='__INSERT__("$IWPERL $COMMON_CODE_PERL/WFApprovalSelect.ipl");'/>
<variables>
<variable key='approvalNeeded' value='workflow process not selected yet'/>
<variable key='approvalTask' value='4th_Approval'/>
<variable key='timeoutDays' value='__INSERT__("$TimeoutApprovalDays");'/>
</variables>
</externaltask>

cliffhanger

no, this wf is implemented in NT env only So chances are, this is not a NT issue.

Anyhow, in those special case scenarios, are you sure in your WFApprovalSelect.ipl you are reaching till the callBack()?

Perhaps you could add some log statements in your .ipl and use that as a check to see whether for thsoe special scenarios your .ipl is reaching till the callBack().

-cliff