This feature is for use in campaign-related projects. It is designed to allow the completion of a specific task in project 1 "trigger" the start of the linked task in project 2. The predecessor connection will be set up in project 2.
To enable, go to Menu > Admin/manager > System setup > Account information > Transaction preferences > Projects > Schedule options.
- Check the option to Allow cross-project predecessors.
Once the transaction preference is set, the project's task predecessor will allow you to pick a project and task.
- Select the task you want to be triggered by the other project's task being completed.
- Click +Predecessor
- Select Project and task
NOTE: You cannot add cross-project predecessors from the schedule grid, you must use the Task details tab to access the predecessors' project drop-down field.
NOTE: The cross-project setting triggers a "project schedule" recalculation in the background. This service is triggered every 2 minutes. Once this is set up in "project 2" close the schedule and let the service trigger before performing any further edits on the project 2 schedule. This will allow the proper plan start date to be set up on the task. If you open it prior to the recalculate schedules' service being triggered it may cause a refresh loop.
Example of usage
You have created a campaign with several projects, including one primary "management" project. The "management" project will contain a set of high-level tasks for the account/project manager to complete. These tasks can be linked to the first task of one or more production projects to set up a trigger for them to begin. Once the connected primary management task is completed, each connected task will be triggered to be "ready" to begin. Any assignments on the connected tasks would now show on your Today-creative assignment page.
Because the connection is made to the first task, the production project(s) schedule will continue to be pushed out based on the connected plan completion date of the primary management scheduled task. Normal schedule-based, task-based signals and notifications continue to react as designed for the production projects.