Adding automated deploy tasks to deployment plans
Automatic tasks run automatically and typically interact with IBM™ UrbanCode™ Deploy applications.
Automatic tasks represent IBM UrbanCode Deploy application processes. When an automatic task starts, the associated application process starts in IBM UrbanCode Deploy. Automatic tasks generate feedback in IBM® UrbanCode Release, and can apply status updates to the applications.
Applications are created by integrating with external products, such as IBM UrbanCode Deploy. For information about the IBM UrbanCode Deploy plug-in, see Integrating with IBM UrbanCode Deploy. The applications that you create with IBM UrbanCode Release do not have automatic tasks and are typically assigned to manual tasks. For information about creating applications, see Managing applications with the Applications page.
Automatic tasks can be created for any application that is assigned to the deployment plan's parent release. All application processes are available. If an application has several processes, say deploy and rollback types, each one is available and can be assigned to automatic tasks. An automatic task can be assigned a single application process; application processes can be assigned to multiple automatic tasks. For information about assigning applications to a release, see Creating releases and specifying release details.
Although most automatic tasks use versioned applications, you can assign unversioned applications to automatic tasks. For example, IBM UrbanCode Deploy applications that have configuration-type or operational-type processes typically do not use snapshots. You can set automatic tasks to use unversioned applications those process types.
Typically, automatic tasks are run in the release environment that is selected for deployment. You can restrict an automatic task to only run if the release environment has one or more environment tags. For information about environment tags, see Configuring release environments.
Automatic tasks start when the parent segment starts. If the execution pattern for the segment is sequential, automatic tasks start according to task order. Otherwise, automatic tasks, like manual tasks, start when the segment starts. An automatic task can have prerequisite tasks, in which case, it starts as soon as all prerequisite tasks are complete.

To edit a task, click the action icon for the task, and then select
View/Edit, . After a task starts, the Comments tab becomes available on the
Edit Task window where you can view or add comments about the task. You can add
dependencies between tasks. A task that depends on another task cannot start until the prerequisite
task is resolved. To manage task dependencies, see Managing dependent tasks.