Auto-starting tasks did not start after completion of predecessor notification tasks in some sites.  The issue occurred with all task types where the task was set to auto-start and the predecessor task was a notification task.  It occurred in sites with the parameter Application.ACM.NotificationTasks.EnableTaskCanBeStartedNotificationForSuccessorTask set to No.  This parameter was used as a way of prompting users to start successor tasks before the introduction of auto-starting tasks, which automatically start.  However, a No setting for this parameter was not only preventing the notification email, but also preventing auto-starting tasks from automatically starting when the predecessor task was completed.

Now, auto-starting tasks always start automatically when the predecessor task is completed, as expected.  The Application.ACM.NotificationTasks.EnableTaskCanBeStartedNotificationForSuccessorTask parameter just controls whether or not notifications are generated when predecessor tasks that do not auto-start are completed, as expected.

Supplier Information & Performance Management