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

Behaviour of CGI Task

Icebreaker

Hi There,

I have a cgi task in my wft whose successor is another cgi task.

The first cgi task works as expected, however the successor cgi task waits on user interaction to do 'Start Input'. I want the successor cgi task to get executed without any user interaction.

The 'immediate' attribute for both cgi tasks are set to 't'. Here is cgi tasks for your reference:

[html]

owner = "__TAG__("authors");"
description="Check for new files added for Finish Work task -- __INSERT__("$br");"
immediate="t" lock="t">

__INSERT__("

");

owner="__TAG__("authors");"
description="Checking approvals -- __INSERT__("$br");"
immediate="t" lock="t">

[/html]

Any help is highly appreciated.

Regards,

Find more posts tagged with

Comments

ISCBorisB

Do you use WFTask::CallBack to transition from CGI1 to CGI2?

If you do, note that it's sufficient for transition but not to activate "back to back" CGIs in immediate Mode.
Try to use TeamSite::CGI_lite::iwcallback() instead.

Adam Stoller

Another alternative is to chain the two operations together within the same CGI Task - and avoid the complexity of the intermediate transition altogether.

Icebreaker

Is is possible to call 2 cgi scripts in one single CGI Task?

Regards,

Adam Stoller

Is is possible to call 2 cgi scripts in one single CGI Task?

Regards,

Sure - you can have a CGI script perform a redirect to another CGI script either through javascript code or through something like a form submit action (the latter is fairly common, where the initial CGI presents options and the second CGI does something with the selected and submitted options)

The trick is that you need to make sure to tunnel through all the CGI / form variables such that the second CGI has sufficient context and information to do whatever it has to, including being able to send a callback to the workflow.

Icebreaker

Thanks for the info Ghoti.

I did try what Boris recommended, but I got the attached error (screen shot). I did the following in the cgi script.

$cgi->iwcallback($session,$task_id,"protect_wf_finish",$comments);

Any clue?

Regards,

Adam Stoller

Thanks for the info Ghoti.

I did try what Boris recommended, but I got the attached error (screen shot). I did the following in the cgi script.

$cgi->iwcallback($session,$task_id,"protect_wf_finish",$comments);

Any clue?

Regards,

Borris didn't tell you to call

iwcallback

that way.

Did you happen to bother to look at the perldoc page for

TeamSite::CGI_lite

? And specifically, did you happen to look at the syntax for the usage of the i

wcallback

method?

If so - you didn't read it very well - there are supposed to be only two parameters - not four! - and sense the first two parameters that you passed in do not conform to the two parameters expected to be received - you're getting a usage error from the CLT that the perl module attempts to call for you.

Try reading the manual (perldoc) - then try fixing your code - and see if that solves the problem.

Icebreaker

Hi Gothi,

I did checked the CGI_lite.pm located under - /app/iw-home/iw-perl/vendor/lib/TeamSite/

The iwcallback sub routine takes 2 parameters as you mentioned - iwcallback ($transition, $comment), however the sub routine calls the 'iwcallback.cgi' located under /app/iw-home/httpd/iw-bin/, but the iwcallback.cgi expects four mandatory parameters as mentioned in the alert message screen shot.

I infact attempted to pass 2 parameters and the task did not get transionted to the expected task, instead it goes back the first cgi task.

I will keep reading the perldoc and will make changes to code and test.

Regards,

labbrown

Hi did you ever find a solution to this? I am also trying to use iwcallback and getting the error.