-
When a task is marked as complete the process looks to any tasks that are dependent on the newly completed task. If a task is marked as “Not Started” and all of the dependency tasks are marked as complete then the process will change the task status to “Started” and email all resources that are assigned to the task that has started. The process notifies resources that a task is ready to start and saves the project manager the manual effort of updating dependent tasks. NOTE: The process relies on task dependencies and is most useful in those environments where task dependencies are managed. -
When a task is marked as complete the process looks to any tasks that are dependent on the newly completed task. If a task is marked as “Not Started” and all of the dependency tasks are marked as complete then the process will change the task status to “Started” and email all resources that are assigned to the task that has started. The process notifies resources that a task is ready to start and saves the project manager the manual effort of updating dependent tasks. NOTE: The process relies on task dependencies and is most useful in those environments where task dependencies are managed. -
When a task is marked as complete the process looks to any tasks that are dependent on the newly completed task. If a task is marked as “Not Started” and all of the dependency tasks are marked as complete then the process will change the task status to “Started” and email all resources that are assigned to the task that has started. The process notifies resources that a task is ready to start and saves the project manager the manual effort of updating dependent tasks. NOTE: The process relies on task dependencies and is most useful in those environments where task dependencies are managed. -
This process, Shift Project Dates, helps Project Managers change an entire Project / Idea’s dates to a new start date. Once the three attributes are added to the Idea /Project Views, the PM can trigger the process by entering a date in the New Start Date field and checking the Shift checkbox. The process runs automatically on Save. The process calculates the date difference between the original Start Date and New Start Date then shifts all Allocation, Task, and Assignment dates by the calculated difference. For example, if a Project is set to begin on January 1st and needs to be pushed to a February 1st start date, the process first determines that there are 31 days between the original start date and the new date. Next the process increases the start date for each Task, Allocation and Assignment by 31 days. NOTE: The process will shift Allocation dates regardless of resource restrictions such as a Termination Date or non-working time as marked on their calendar. The Team page will reflect the Available Start and Finish as shifted by the process, but the Allocation hours and % will take unavailable time into account. For example, if a shift process sets the start date for a resource to be after their date of termination the dates will change by the date difference, but the Allocation hours will correctly be calculated as zero. -
This process, Shift Project Dates, helps Project Managers change an entire Project / Idea’s dates to a new start date. Once the three attributes are added to the Idea /Project Views, the PM can trigger the process by entering a date in the New Start Date field and checking the Shift checkbox. The process runs automatically on Save. The process calculates the date difference between the original Start Date and New Start Date then shifts all Allocation, Task, and Assignment dates by the calculated difference. For example, if a Project is set to begin on January 1st and needs to be pushed to a February 1st start date, the process first determines that there are 31 days between the original start date and the new date. Next the process increases the start date for each Task, Allocation and Assignment by 31 days. NOTE: The process will shift Allocation dates regardless of resource restrictions such as a Termination Date or non-working time as marked on their calendar. The Team page will reflect the Available Start and Finish as shifted by the process, but the Allocation hours and % will take unavailable time into account. For example, if a shift process sets the start date for a resource to be after their date of termination the dates will change by the date difference, but the Allocation hours will correctly be calculated as zero. -
This process, Shift Project Dates, helps Project Managers change an entire Project / Idea’s dates to a new start date. Once the three attributes are added to the Idea /Project Views, the PM can trigger the process by entering a date in the New Start Date field and checking the Shift checkbox. The process runs automatically on Save. The process calculates the date difference between the original Start Date and New Start Date then shifts all Allocation, Task, and Assignment dates by the calculated difference. For example, if a Project is set to begin on January 1st and needs to be pushed to a February 1st start date, the process first determines that there are 31 days between the original start date and the new date. Next the process increases the start date for each Task, Allocation and Assignment by 31 days. NOTE: The process will shift Allocation dates regardless of resource restrictions such as a Termination Date or non-working time as marked on their calendar. The Team page will reflect the Available Start and Finish as shifted by the process, but the Allocation hours and % will take unavailable time into account. For example, if a shift process sets the start date for a resource to be after their date of termination the dates will change by the date difference, but the Allocation hours will correctly be calculated as zero. -
This notification process sends an email to the Manager of an investment (Project, Application, Idea, etc) when the resource assigned to the team has been hard booked. The process should be scheduled to run on a daily basis as the logic in it looks to all resources where their Booking Status has been changed from Soft to Hard on the day that the process is run. It compares the audit trail date change field to the system date. If the process is not scheduled to run daily no notification will occur on hardbookings from previous days. -
This notification process sends an email to the Manager of an investment (Project, Application, Idea, etc) when the resource assigned to the team has been hard booked. The process should be scheduled to run on a daily basis as the logic in it looks to all resources where their Booking Status has been changed from Soft to Hard on the day that the process is run. It compares the audit trail date change field to the system date. If the process is not scheduled to run daily no notification will occur on hardbookings from previous days. -
This notification process sends an email to the Manager of an investment (Project, Application, Idea, etc) when the resource assigned to the team has been hard booked. The process should be scheduled to run on a daily basis as the logic in it looks to all resources where their Booking Status has been changed from Soft to Hard on the day that the process is run. It compares the audit trail date change field to the system date. If the process is not scheduled to run daily no notification will occur on hardbookings from previous days.

