Pass Successor Information

Is it possible to pass in successor information to a task. This way I could re-use the same email notify for reviewers as I do for deployment notification. They are the same list here, and only the next step differs... If not I can always use 2 tasks, but was looking for a cleaner way.

David R Musser
Eye Street Software
540-542-5257
dmusser@eyestreet.com
Win2k, TS 6.5 SP1, OD 6.01

Find more posts tagged with

Comments

Migrateduser

What if your email task had many (perhapy very many) successors after it and you just did a CallBack on the appropriate value, routing your workflow accordingly?

Current Environment(s):
(1) TS 6.1 SP1 on W2K3
(2) TS 6.1 SP2 on W2K
(3) TS 6.1 on W2K

nipper

If I read your question correctly, you can have 3 different returns from the external
task, one that is for email 1, the second for email 2, the third for error.

You will have 3 possible successor tasks, task1, task2, and error.

It is pretty straightforward. Something like this:

<successors>
<successorset description = "Go to Task1">
<succ v = "task1"/>
</successorset>
<successorset description = "Go to Task2">
<succ v = "task2"/>
</successorset>
<successorset description = "Error">
<succ v = "Error"/>
</successorset>
</successors>

Try it & post any questions.

Andy

DavidMusser

Thank you both... you are thinking along the same lines that I was, but I wanted to keep it out of the callback. I would like to control it outside of my email script, but I do not think that it's possible to do that.

So thanks!!!

David R Musser
Eye Street Software
540-542-5257
dmusser@eyestreet.com
Win2k, TS 6.5 SP1, OD 6.01

DavidMusser

Dave,

I think you are right... I think that will work. I was just wondering if there was a way to do it that did not involve the callback. I think I'm going to do as you've suggested with the callback.

Thanks -D

David R Musser
Eye Street Software
540-542-5257
dmusser@eyestreet.com
Win2k, TS 6.5 SP1, OD 6.01

DavidMusser

Under this same line of thinking... in an external task can you get information about the task that was previous to the current task? i.e. what task just happened so that I can know where to send it.

David R Musser
Eye Street Software
540-542-5257
dmusser@eyestreet.com
Win2k, TS 6.5 SP1, OD 6.01

Adam Stoller

The best way to do that is probably to use job-level variables for specifying the predecessor task - which you could use the wfvarfinishop attribute for your tasks to set. That way you can retrieve the information in your externaltask (this may not work right for a workflow with concurrent tasks - you'd probably need some other mechanism - like parsing the output of iwgetwfobj or something)

--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com