cgi task not working

Hi,

I have a cgi task which sets the priority of a workflow.This cgi task is invoked after a user belonging to a particular group takes ownership of the group task and clicks on "set priority" button. I have set the immediate flag to true, so when the user clicks on set priority button from the workflow the cgi task window appears. If from the same window user clicks on cancel the task by default goes to an intermediate task which has the button "start input task" . Is it necessary to provide some input to cgi everytime you transition to it. How can we move back to the group task where user took ownership of the task on clicking cancel. My problem is this intermediate task which appers when user clicks cancel. I have already tried transition on cancel but it doesnt seem to work.

Find more posts tagged with

Comments

Adam Stoller

Hi,

I have a cgi task which sets the priority of a workflow.This cgi task is invoked after a user belonging to a particular group takes ownership of the group task and clicks on "set priority" button. I have set the immediate flag to true, so when the user clicks on set priority button from the workflow the cgi task window appears. If from the same window user clicks on cancel the task by default goes to an intermediate task which has the button "start input task" . Is it necessary to provide some input to cgi everytime you transition to it. How can we move back to the group task where user took ownership of the task on clicking cancel. My problem is this intermediate task which appers when user clicks cancel. I have already tried transition on cancel but it doesnt seem to work.

Your post is a bit confusing. There is no such thing as an "immediate task". There is a CGI Task with the "immediate" attribute set to "true" (or "t").

If I understand you correctly you have a Group Task followed by a CGI Task - yes?

Do you have some form of iwat trigger script in place to ensure that the CGI Task is owned by the same user who took ownership of the Group Task? If not, the ability for the CGI Task to start immediately will be based on whether the person who took ownership of the Group Task happened to be the user whose name is hard-coded in the WF as the owner of the CGI Task.

Assuming you've got that part taken care of - am I correct that you're talking about hitting a "Cancel" button within the CGI Task window? Or are you talking about hitting a "Cancel" button somewhere else? (like in the Task Details screen?)

The more detail you provide and the more clearly you provide it - the easier it will be for someone to provide guidance.

swatis

I have set the attribute immediate="true". You took it correctly i have a group task followed by a cgi task. The member of the group after taking the ownership clicks on "Set Priority" button to trigger the cgi task.

As of now i am not using any iwat that should take care of the ownership, but in the cgi script i made sure that when user navigates aways from the cgi window by selecting the priority and clicking on "ok" the owner of the next task should be the owner of the previous group task by using the setowner function. I am using wft. and teamsite 7.1.

I am talking about hitting the cancel button in the cgi task window. If user clicks on this the window close but i get an intermediate task which has the button "start input task" i dont have this task but my problem is why does a cgi task not remain on its state when i close the window just like other tasks.

I was going through the workflow documentation just a few mins back and found out that if a user attempts to close cgi task window, user can explicitly start that task after clicking on the start button. I think this is the default functionality of teamsite. but is there a workaround for this???

ISCBorisB

What's unclear (to me anyway) in all that is the role of "set priority" button.
Have you customized/hacked a group task so that certain CGI is executed on (or perhaps instead of) priority change?

If you have, this is not a CGI Task, even if you call the same CGI code that your group task may transition to.
To begin with, posted form is more likely than not differs, "immediate" set has no impact, transition mechanisms are
up to you and so on.

If you haven't, what does "...when the user clicks on set priority button from the workflow the cgi task window appears..."
really mean? From your questions it does not look like you force a Group Task / CGI Task transition on priority change.
So what happens?

Adam Stoller

I have set the attribute immediate="true". You took it correctly i have a group task followed by a cgi task. The member of the group after taking the ownership clicks on "Set Priority" button to trigger the cgi task.

Okay - you have a Group Task with a SuccessorSet / Transition description of "Set Priority" - that transitions to a CGI Task that supposedly does something regarding setting some priority value - yes?

As of now i am not using any iwat that should take care of the ownership, but in the cgi script i made sure that when user navigates aways from the cgi window by selecting the priority and clicking on "ok" the owner of the next task should be the owner of the previous group task by using the setowner function. I am using wft. and teamsite 7.1.

How are you using the "set owner" function during the Group Task to ensure that the owner of the CGI Task is the same person?
Are you doing this manually?

I am talking about hitting the cancel button in the cgi task window. If user clicks on this the window close but i get an intermediate task which has the button "start input task" i dont have this task but my problem is why does a cgi task not remain on its state when i close the window just like other tasks.

Are you saying you have a CGI Task window that runs a CGI script that presents (among other things) a "Cancel" button to the user, and upon clicking on that button the CGI Task window closes? If so - does clicking on the cancel button attempt to perform any kind of transition (it doesn't sound like it)? If not - then that is why you are being left with the "Start Input Task" in the Task Details screen. The CGI Task is still the current "active" task - it's just waiting to be invoked again on the premise that if something other than "Cancel" is selected it will "do the right thing" and transition to whatever task comes after the CGI Task.
If any of the above does not conform to what you are actually doing - please clarify, in detail.

I was going through the workflow documentation just a few mins back and found out that if a user attempts to close cgi task window, user can explicitly start that task after clicking on the start button. I think this is the default functionality of teamsite. but is there a workaround for this???

You can attempt to trap the closure of the window and perform some type of transition before closing the window - but other than that, no.

swatis

@adam - Thanks for the reply, i got what you want to convey.

I'll have to make the transiiton happen on cancel.