cgitask with immediate="t" not starting automatically

Hi ,

Hi ,

Using TS 6.5 SP1 Win 2003 .

I have two cgi task in wf one after the other .

First cgi task is the start task of workflow.
Second cgi task is activated after the first one .
Second cgi task has also immediate="t"

Owner of both the tasks is same .

The first cgi task starts immediately as worflow is activated . But the second cgi task does not starts automatically .

I need to go to the task list and then click 'Start Input Task' .

Attaching the code for both the cgi tasks and worflow .

Whatelse is the requirement for the cgi task to start automatically ?
I have fulfilled the two requirement :
1. Owner of previous task and cgi task should be same .
2. immediate="t" should be there for cgi task

Regards
Rohit pathak

Regards
Rohit Pathak

Find more posts tagged with

Comments

Bill Klish

Are there any errors showing up in any of the logs?

Adam Stoller

Hi ,

Hi ,

Using TS 6.5 SP1 Win 2003 .

I have two cgi task in wf one after the other .

First cgi task is the start task of workflow.
Second cgi task is activated after the first one .
Second cgi task has also immediate="t"

Owner of both the tasks is same .

The first cgi task starts immediately as worflow is activated . But the second cgi task does not starts automatically .

I need to go to the task list and then click 'Start Input Task' .

Attaching the code for both the cgi tasks and worflow .

Whatelse is the requirement for the cgi task to start automatically ?
I have fulfilled the two requirement :
1. Owner of previous task and cgi task should be same .
2. immediate="t" should be there for cgi task

Regards
Rohit pathak

Regards
Rohit Pathak

You don't indicate if you followed the third requirement - as documented in the manual (which was copied from the Workflow Supplement Tutorial available on this site):

The cgi task follows another cgitask, both owned by the same user, and the first cgitask script used the TeamSite::CGI_lite::iwcallback() method to initiate a callback to the workflow engine.

I'm only giving the page reference for the SP2 manual because that's what I have available - the rule, however, goes back to at least 5.5.2 and probably all the way back to 4.0 when Workflow was introduced.
Some have indicated that you can use the appropriate CCI URI in place of TeamSite::CGI_lite::iwcallback - I never had to do that, but I also haven't had to deal with back-to-back cgitask's for a while...

rohitspathak123

Hi Fish ,

Thanks for ur reply .

In my post i have mentioned 2 pre-conditions , but actually I am also following all the 3 condition .

If u see in test2.wft code ...i have used $task->CallBack()

Is $task->CallBack() different from TeamSite::CGI_lite::iwcallback() ?

I even tried TeamSite::CGI_lite::iwcallback() but its not working .

Regards
Rohit Pathak

Sailesh

Hi Rohit,

I could not see TeamSite::CGI_lite::iwcallback() been called in your wuWfDcrJspMappingAndRegen.ipl

You need to do iwcallback() for your CGI to run immediately.

kaalraa

Is $task->CallBack() different from TeamSite::CGI_lite::iwcallback() ?

Yes... there are a lot of differences between CGI_Lite::iwcallback() and $task->CallBack(). Also the usage of these two are quite different.

Read out the manuals for more information... or can ask for specific usage.

ISCBorisB

Hi Fish ,

Thanks for ur reply .

In my post i have mentioned 2 pre-conditions , but actually I am also following all the 3 condition .

If u see in test2.wft code ...i have used $task->CallBack()

Is $task->CallBack() different from TeamSite::CGI_lite::iwcallback() ?

I even tried TeamSite::CGI_lite::iwcallback() but its not working .

Regards
Rohit Pathak

CGI to CGI transition issue can often be avoided in the first place. In many cases you can have single CGI task and from it invoke multiple CGIs.
For example, on "Done" Action/Button of CGI-1 you may post to the action that is CGI-2, etc. "Last" CGI in the chain would have to call back to WF

Adam Stoller

CGI to CGI transition issue can often be avoided in the first place. In many cases you can have single CGI task and from it invoke multiple CGIs.
For example, on "Done" Action/Button of CGI-1 you may post to the action that is CGI-2, etc. "Last" CGI in the chain would have to call back to WF

True - or a single CGI script can be written the calls itself, passing state information, so that each time it calls itself it executes different portions of the code.