Enabling/Disabling successor option in a User task

Hi,

I wished to know whether we can enable/disable the options( to choose successors like Approve/Reject) dynamically through an external script.
My requirement is :
-- User Task A (should have only one option/successor which would be an external task

--External Task B (after this task is completed transition happens back to User task A,but now the User task A should have two options i) Transition to Task B ii)Transition to another User task C )
--User Task C

Your suggestions would be helpful.
Thanks,
Santosh

Find more posts tagged with

Comments

kaalraa

Hi,

I wished to know whether we can enable/disable the options( to choose successors like Approve/Reject) dynamically through an external script.
My requirement is :
-- User Task A (should have only one option/successor which would be an external task
--External Task B (after this task is completed transition happens back to User task A,but now the User task A should have two options i) Transition to Task B ii)Transition to another User task C )
--User Task C

Your suggestions would be helpful.
Thanks,
Santosh

Santosh,

There are two options which comes to my mind are:
1. Use two different tasks Task A1 and Task A2 to overcome the situation. It means A1 >> B >> A2 >> B or C.

2. Use the logic to check as what is the predecessor of task A and depending upon that .. you can provide the number of successors within Task A. In that case you have to use

Adam Stoller

Santosh,

There are two options which comes to my mind are:
1. Use two different tasks Task A1 and Task A2 to overcome the situation. It means A1 >> B >> A2 >> B or C.

2. Use the logic to check as what is the predecessor of task A and depending upon that .. you can provide the number of successors within Task A. In that case you have to use <template_script> tag to write your code within.

The first response is correct, the second response I'm either misunderstanding, or it's just plain wrong. If you're dealing with a usertask, as was defined in the original post, you cannot dynamically alter it's successorsets in the WFT or in the instantiated workflow.

For an externaltask or cgitask you have the ability to dynamically select from among the defined successorsets programmatically - but for a usertask you are stuck with what you defined at the time of instantiation.

kaalraa

For an externaltask or cgitask you have the ability to dynamically select from among the defined successorsets programmatically - but for a usertask you are stuck with what you defined at the time of instantiation.

In this case... i would revert with my second option and would like to stick with first only; to use 2 separate tasks.

Thanks Adam... for clearing up my concepts as have never tried that in a Usertask.

santoshrt

Hi,

Currently I have implemented the same option, but the reason I dont want to continue with it is , Task A is an author task.
A user can execute the task from Email (Task A1 ..if I use two tasks(Task A1 and Task A2)
But when transition happens to task A2 (after completing the intermediate external task) the user still has the same mail and does not know that its a different task(i.e with different id).
With this option a user can execute the task only once from email..next time the user needs to login to TeamSite Content Center without being able to execute from email.
Seems to be a puzzle.I guess I may have to continue with this option with the limitation that user has to login to TS Content Center for the second time.

P.S : The user should nor be aware that there are two separate tasks (task a1 and a2) .

code.zip

Migrateduser

Use an externaltask to send email notification for the second time also.