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

Immediate attribute in cgitask

prabs

Hi,
We have created workflow with workflow modeler(ver 1.0.0.1) and activated into the ControlHub (ver 3.0.0) . In that workflow, we have set the 'immediate' attribute of cgitask to 'true' so that the cgitask gets activiated immediately after the execution of the previous task and throw up a custom cgi screen to the user. This is not happening.
What i have noticed is that, when the control comes to the cgitask, the screen throws up the error saying "Job 0 is no longer valid". I have to click on the project in the LHS navigation to get back to my list of jobs
If the 'immediate' attribute of cgitask is set to 'false', it takes too many clicks to open up the cgi screen itself, which annoys the end user.

Kindly help me resolve this issue

Find more posts tagged with

Comments

ISCBorisB

Hi,
We have created workflow with workflow modeler(ver 1.0.0.1) and activated into the ControlHub (ver 3.0.0) . In that workflow, we have set the 'immediate' attribute of cgitask to 'true' so that the cgitask gets activiated immediately after the execution of the previous task and throw up a custom cgi screen to the user. This is not happening.
What i have noticed is that, when the control comes to the cgitask, the screen throws up the error saying "Job 0 is no longer valid". I have to click on the project in the LHS navigation to get back to my list of jobs
If the 'immediate' attribute of cgitask is set to 'false', it takes too many clicks to open up the cgi screen itself, which annoys the end user.

Kindly help me resolve this issue

Check Workflow Developer's Guide to see when the immediate='t' attribute of
the CGI Task has an effect. It actually depends on the predecessor and Tasks'
ownership

Migrateduser

Why is this in the OpenDeploy forum?

ISCBorisB

Why is this in the OpenDeploy forum?

Grey area. There is no dedicated ControlHub Forum. It normally goes under OD umbrella.
Prabs seems to code a WF for the Control Hub so "TeamSite Workflow" Forum *may* sound
confusing etc...

prabs

As soon as the workflow transitions to the cgi task, i am noticing the following line in servletd_out.log

*************
2010-08-04 15:24:56,906 [http-8080-Processor19] ERROR com.interwoven.ui.controlhub.deploy.command.GetJobsCommand (chadmin commandID iw.ch.deploy.jobs) - No vpath found in the request
*************

I've set the 'AreaVPath' for all the tasks. Not sure what is happening.

I have also opened up a support case and waiting for the response

ISCBorisB

Ignore Logs for a moment. Have you checked WF Developer Guide? It clearly states Conditions
that allow the CGI Script to run automatically upon CGI Task Acticvation. Are these Conditions
met in your case? If not - the owner of the cgi task will have to start it manually.