It would be very advantageous if ADmanager Plus could cancel the successive task via another automation policy and\or modification template. The process I was envisioning was a simple tick box to cancel the task. OK I admit it may not be that simple to implement .

I work in a FE environment with 10,000 students who by their nature can enrol on courses, leave before the course completes and then decide to return after a few weeks which makes things difficult to manage. The process is:-

1. Student withdraws - move student to a new OU and remove from access control group that allows access to buildings (once a student can no longer access a building it usually prompts them to get their student record in order).
2. After x days the account is moved to another OU and disabled.
3. After a further x days the home drive is moved to an archive and the account deleted.

My problem is if a student returns after step 1. I cant use a modification template to re-instate the account because the successive task will perform it's actions at a later date. If I use a workflow I will need to manually remove objects from the request which will be laborious to say the least.

I could just split it into different automation's but that would mean a fair amount of SQL work which seems counter productive.

Would the cancellation request for successive tasks be useful to anybody else? if so could it be added to the product roadmap?

If anybody has any better ideas for handling the above they would be greatly appreciated.

Regards,

Simon