Thanks for the second look, I realized I fat fingered my cmd line query. Passing the second parameter as 0 or 1 provides the same result in updateing the task and data in the db - assuming the group ref can be found. I wonder if I need to somehow force the rule to pass the second parameter. Something I will try and see if it is possible.
As for the stored proc does... here is a short description.
Submission-
Essentially the workflow conists of a request with multiple tasks. during the workflow, the tasks are activated based on the extension fields compelted during the submission of the portal request. End user completes the submission form with task desciption, date and extension field
Rule evaluted-
As the workflow is processed the condition branch has a set of rules to active and forward the tasks to variosu groups for completion
The stored proc is executed and takes the task number
Update the task short desc and date based on details entered from the submission form
Finds the group ref from the extension field chosen
Execute another stored proc (taskgroupforward) to update the forward to value based on the group chosen in the extension field
While I am still reviewing all the new features of v9.1, I have not found any other way to perofmr what I am doing. any thoughts on what can be done differently using our of box features in v9.1?
Aprpeciate your help...