Creating a scenario

portfolio scenario name. It is important to choose a descriptive name.

Full description of the portfolio strategy

Description of this portfolio scenario

Codes are generally entered in uppercase letters and with underscores _ It is important to enter them because they can be useful in case of errors or during import.

Select a status the scenario: approved, draft… By default, the status set to Draft

This refers to the period which the scenario will be run. For example: from January 2025 to December 2027.

This field allows you to select a user to serve as the manager . By default, the user who created manager will be selected.

This field allows you to select, one by one, the projects that will be included in the portfolio scenario

This field allows you to select the desired projects from the drop-down list. You can check individual projects one by one, or select all of them by checking the first box. If you uncheck a box corresponding to a project, that project will no longer appear in the portfolio project list.

This field allows you to select the projects that will be included in the portfolio filter criteria:

• Contains
• Attachments
• theme
• user role(s)
• With late milestones
• Father project
• Start of smoothing of remaining work
• project template
• project manager
• status
• Start date
• End date
• Weather
• summary sheet document

You can add project attributes Project : profits, weather, etc. This will provide strategic information to refine the scenario. The following project attributes are available:

• Chain : a string of 225 characters
• Digital
• Boolean
• List
• Date

The following project attributes are not available:

• Multi-line
• Wealthy
• Image
• Document

The selected attributes appear as tiles, and you can drag them to reorder them.

Allows you to choose whether to use the scenario with the theme . The associated resource constraint fields appear or disappear depending on this selection.

Allows you to choose whether to use the scenario with the theme . The associated budget constraint fields appear or disappear depending on this selection.

This unit is for reference only; it is used solely for display purposes (e.g., JH…)

This field is used to select the correct category to display the resources for the projects included in the scenario

This field is used to define a minimum load for resources: the gauge will use this value to determine whether to display the correct assumption. This is for display purposes only. You cannot enter a “maximum” constraint value if a “minimum” constraint value has already been entered, and vice versa.

This field is used to define a maximum load for resources: the gauge will use this data to determine whether the assumption is correct or not. This is for display purposes only. You cannot enter a “maximum” constraint value if a “minimum” constraint value has already been entered, and vice versa.

This currency symbol is for reference only and is used solely for display purposes (e.g., €, $, £…).

This field is used to select the correctbudget category budget display the budgets for the projects included in the scenario

This field is used to set a minimum value for budgets: the gauge will use this value to determine whether to display the correct scenario or not. You cannot enter a “maximum” constraint value if a “minimum” constraint value has already been entered, and vice versa.

This field is used to set a maximum limit for budgets: the gauge will use this value to determine whether to display the correct assumption or not. You cannot enter a "maximum" constraint value if a "minimum" constraint value has already been entered, and vice versa.