Configuration > Strategy General Settings
The Strategy > General Settings section contains properties that define behaviour across both Optimisation and Prioritisation in Altus.
Initiative Types
The initiative types that can be selected for an Optimisation Plan are defined in this setting.
Note: Changing the initiative types here will also affect how Prioritisation works.
Optimisation Mapped Fields
The Optimisation Mapped Fields properties let you define which columns can be displayed in the left section of the Optimisation Gantt control.
Properties for an Optimisation Mapped Field:
| Property | Description | Options |
|---|---|---|
| Display Name | The title for the column header. | — |
| Field | A unique identifier for the mapped field. | — |
| Type | The type of data expected for the field. This affects how the column values are formatted. | Text, Date, Whole Number, Decimal Number, Currency. |
Note: For values to appear in a defined column, that column must also be mapped in the Mapped Fields definition for each relevant Initiative Type. If a column is not mapped for an Initiative Type, it will show as N/A in the Optimisation Gantt control.


Initiative Types > Mapped Fields
This section allows you to define where the data for each mapped field should come from for the selected Initiative Type.
Properties for each mapped field:
| Property | Description |
|---|---|
| Field | Must match the unique identifier for the Optimisation Mapped Field. |
| Direct Field Mapping | Choose from a dropdown list of all Dataverse columns related to the initiative type. For most fields, simply select the related Dataverse column name. |
| Internal Function | Currently only supported for the Projects initiative type, used for retrieving financial data from the Project’s finance grid. Selecting a value here means the mapped field value will be determined by an internal process that queries financial data directly. - Financial Aggregation: Aggregates all financial transaction data for the initiative, according to the transaction type specified in the Internal Function Value. - Financial Aggregation By Date Range: Aggregates all financial transaction data for the initiative within the Scenario’s horizon date range, according to the transaction type specified in the Internal Function Value. Use this property only if no value is set for Direct Field Mapping. |
| Internal Function Value | Used with the Internal Function property. Defines the value property of the financial transaction type option set value to aggregate. |
| Transform | (Not yet in use) |
If no mapped field is set for an Optimisation Mapped Field in an Initiative Type, N/A will be shown as the column value for all Initiatives of that type in the Optimisation Gantt.


Optimisation Financial Transaction Types
When a user displays the Finance Grid in an Optimisation Plan, the financial transaction types shown are determined by the Optimisation Financial Transaction Types defined in this setting.
Properties for each transaction type:
| Property | Description |
|---|---|
| Value | The option set value corresponding to the financial transaction type. |
| Allow Simulated Data Shift | If enabled, simulating a date shift for an initiative in the Gantt will also simulate a shift of financial data in the finance grid for this transaction type. |
| Hide | Allows an admin to hide a transaction type from the Optimisation Plan finance grid. |
Note: If all transaction types are set to ‘Hide’, the toggle button to display the Financial Grid will be disabled.

By default, all financial transaction types are shown, and only Budget and Forecast allow simulated data shifts.
Timeline Movement of Ongoing Initiatives
To support scenario simulation, Initiatives in the Gantt can be dragged to different dates, including those that have already started.
The Timeline Movement of Ongoing Initiatives setting lets you restrict this so only Initiatives scheduled in the future can be moved.
