Interproject Dependencies

General Settings

By default, only dependencies between projects are enabled.

The dependencies feature allows different initiatives to be included in dependency creation. The Dependencies > General Settings configuration page lets you specify which types of initiatives appear in the Dependencies Predecessor and Successor drop-down lists. This is done through the Initiative Types section.

Adding new Initiative types to Interproject Dependencies follows the same process as adding them to Prioritisation. For step-by-step instructions, see this guide.

Note

Currently the only types of Intiatives you can add to this list is: Programs, Portfolios, Proposals and Ideas.

When you add a new Initiative Type to the configuration, this mapping will appear in the Choose Initiatives window:

The New Initiative Type screen contains the following fields:

• Type (Table): Select the table of the initiative type to include in dependency creation.
• Custom Tab Label: Specify the name of the tab where these new initiative types will be displayed within the Initiatives Selection screen.
• Add Dependency (Related View): Select the view that will display the initiatives for dependency creation.
• Lookup Field (on Initiative): Choose the field that users can use to search within the view.
• Date Field (Start Date on Table): Set the start date field to be used for this new initiative type in the dependency.
• Date Field (Finish Date on Table): Set the finish date field to be used for this new initiative type in the dependency.
• Form (Containing the Dependency Tab): Specify the form that contains the Dependencies tab.

Note: If you enable dependencies between other types of initiatives in Altus, you will need to add the Dependencies tab (tab_dependencies) to those entities. This ensures that users can create and view dependencies within the entity.

Interproject Dependency Ownership

Interproject dependencies can be created by many different roles within Altus.

So that the correct users can see and manage these dependencies a function runs in the background when an Interproject dependency is created that updates the owner of the record to the Successor Project.

This update changes the relationship between the sensei_dependency entity and initiatives from referential to parental. With this change, when a successor initiative (or project) is deleted, all associated dependency records will be automatically removed, ensuring no orphaned records remain.

Additionally, read permissions for dependency records are raised to the Business Unit level for designated roles, while other roles remain at the Global level as specified.

Please Note: if a Predecessor initative is deleted the dependency record isn't deleted.