Reference of previous task..

Hi,
I have two questions Smiley Happy

1. i have a user task having 2 buttons- Approve and Reject. On click of either it will go to same external task which will send a email . On the basis of the buttons, i m going to put the subject of the mail as "Contribution approved" or "Contribution rejected". is there any way, where i can get the reference of the previous succesorset no?

2. is there any command line tool to get the previous task which invoked the current task?
i m using TeamSite 6.5.0 SP2 on windows server 2003 SP1.
hope to get some input... Smiley Happy

thnx
amit

Find more posts tagged with

Comments

Mr_Cruise

I think you are not taking the right approach for the design of your workflow. In your case you should have two separate tasks that call the same external task. This way you can pass different parameters to the same external task and then you will not need to know the previous task.

However, the best way to save state information is to set a workflow variable, as they can be manipulated from Perl and the command line.

Hope this helps!

kaalraa

But i doubt if we can update any workflow variable information from a usertask, so it is better to have a CGI task in order to store the approval/rejection status and passing it to next task. Hope it makes sense.

Adam Stoller

Hi,
I have two questions
1. i have a user task having 2 buttons- Approve and Reject. On click of either it will go to same external task which will send a email . On the basis of the buttons, i m going to put the subject of the mail as "Contribution approved" or "Contribution rejected". is there any way, where i can get the reference of the previous succesorset no?

2. is there any command line tool to get the previous task which invoked the current task?
i m using TeamSite 6.5.0 SP2 on windows server 2003 SP1.
hope to get some input...

thnx
amit

I suggest having the transitions for Approve and Reject go to two distinct externaltasks - each of which can call the same script and pass parameters either on the command line or (better) through task-level variables.

Unless you have some reason for providing a separate CGI interface - adding the cgitask would be an additional level of complexity (externaltask scripts tend to be much easier to design/implement/test than cgitask scripts) - on the other hand, a cgitask script could provide you the Approve and Rejection buttons and take care of whatever you were planning to do with the externaltask script - all in one. But again, I'd still favor the separate externaltask's calling the single script (presumably to send email and then transition either forwards or backwards along the flow)