Managing wait for time tasks

A wait for time task can be finished only at a specific time.

Wait for time tasks provide milestones for critical tasks. With wait for time tasks, you can ensure that important tasks start at the expected time. Typically, you make a wait for time task a prerequisite for an important task that must start at a specific time.

A wait for time task starts as soon as it is otherwise eligible to run, and finishes at a user-specified time. A started wait for time task has a status of In Progress until it reaches its specified, planned-for time, when it changes to a status of Finish.

Note: You can also do most of these steps on the Execution and Deployment Plan page when you run a deployment. You can add tasks and segments to a deployment while the deployment is running. Changes that are made during a deployment are preserved in the deployment plan that is used for the deployment.
  1. From the IBM® UrbanCode™ Release dashboard, click Releases & Deployments, and then click Deployment Plans.
  2. On the Deployment Plans page, click the name of the deployment.
  3. On the plan page, click Add Task for the segment where you want to add the task, and then select Wait for Time Task.
  4. In the Add Wait for Time Task window, in the Task Name field, enter a name for the task.
  5. In the Planned Time field, enter the wait time for the task or select it from the Planned Time list, and then click Save.
    The task is inserted into the segment. The time is the time that the task finishes and that dependent tasks, if any, can start.
    Note: Normally, if a wait for time task starts after the planned time, the task will immediately finish. If, however, you schedule a deployment to start after the planned time for the wait for task, the task will wait until the following day to start.
  6. Optional: To add a task tag to the task, complete these steps.
    1. In the Edit Task window, click the Task Tags icon, add task tags.
    2. In the Task Tags dialog box, select the tag.
      You can select multiple tags.
    3. Optional: To create a tag, click Edit Tags, and then click Add New.
      In the Name field, type a name for the tag, select a color, and then click Save.
    4. Click Save.
      The tag is added to the task.
    5. Optional: Click the Delete icon for a tag to remove it from the task.
    Tags can be viewed from deployment plan page. You have the option to view or hide task tags using the View Tags / Hide Tags toggle switch at the top of this page.
  7. Optional: By default, tasks are available for all environments and all deployments that are associated with the release. To change this pattern, complete these steps:
    1. On the Edit Task page, click Environments.
    2. In the Pattern area, select one of these options to change the task frequency:
      • Always Run, to make the task available for every deployment.
      • Run Once Per Environment, to restrict the task to one deployment per environment.
    3. Select environments for the task.
      The task is active for the selected environments. By default, the task is active for every environment that is associated with the release. Tasks that are not active for an environment have the Not Applicable status, , when you deploy to an ineligible environment. You can override the status when you run a deployment by reopening the task.
  8. Optional: To add attachments to a task, complete the following steps:
    1. On the Add Task page, click Attachments, and then click Add Attachment.
    2. In the Add Attachment window, click Browse, and then select a file.
    3. Optional: In the Description field, describe the attached file.
    4. Click Save.
      The file is attached to the task and listed in the Attachments tab. To remove an attachment, click Delete.
    To see an attached file, click the file name. Depending on the file type, you are prompted to choose an application with which to open or view the file.

    By default, task attachments are stored in the ucr_installation/attachements directory. You can change the default location by modifying the attachments.folder.path property in the ucr_installation/conf/ file. For example, attachments.folder.path=/my_folder/my_attachments.

The task is added to the deployment plan at the bottom of the task list for the selected segment. The task is assigned a task number based on the segment and the task's position in the segment. Reposition a task by clicking and holding the mouse over the task and dragging it to another location. Tasks can be reordered within a segment or moved to other segments. After you move a task, the task numbers are updated to reflect the current task order.
Moving a task

Make a critical event task or another task dependent on the wait for time task.