Scheduled Deployments

jajtiii

Instead of using OD for this, we have decided to incorporate a workflow model that uses two successor tasks during the final deploy to production. One successor task is a delay what waits until the given period has expired before pushing to production. If it activates, it deactivates the sister task. The sister task is a user task that allows a user to either push the task on anyway, cancel the job or to send it back for rework (change) - any of these actions deactivates the delay task.

The user task will lock the given file, thus preventing someone else from modifying it before it the current version has been deployed.

Does anyone see any flaws/weaknesses with this plan?

TS 6.5, OD w/DD 6.0.1
Solaris 9

JonathonG

Why not just put the timeout on the usertask? That would simplify your design significantly.

Jonathon
Interwoven Developer
Allstate, Inc.