Through the Configure menu of a Flavor, global settings for the Flavor can be adjusted.
Open the Configure menu by right-clicking on a Flavor >
The following options are available:
1. Lock Settings Editing
With this option, the configuration of the Flavor, as well as all global settings of the Flavor, is locked. The permission to edit is granted only to the person who activates the lock, as well as administrators.
- Configuration menu
- Visibility options
The lock is indicated to others by notification icons. A request to unlock can be made.
2. Lock Value Editing
With this option, the value selection of the Flavor can be locked. The permission to edit is granted only to the person who activates the lock, as well as administrators. This option can only be activated if editing of settings was locked previously.
3. Hide for Guests
With this option, the Flavor can be hidden for guests. Regardless of where the Flavor is used/displayed, it is invisible to all individuals with a guest role.
4. Value Input Required
With this option, value input can be defined as required in the relevant Flavor.
This property is only available for Flavors used in either tasks or project master data, and it is a global setting.
When the option is activated, the Flavor is initially marked with an asterisk (*). Depending on whether a Flavor with required value input is used in project master data or tasks, this has different effects.
Usage in Tasks
If a task contains Flavors with required value input, when changing the status to Done, a check is made to ensure that all Flavors with this option have a value.
If not, the user is notified, and the transition to the Done status is prevented.
However, the task can still be saved/exit.
Usage in Project Master Data
In project master data, a Flavor with the active 'Require Value Input' option behaves similarly, and here as well, it is marked with an asterisk (*). In contrast to tasks, usage in project master data has no further impact.
Create a separate group for important Flavors that have been marked with the 'Require Value Input' option, which you place as the first Flavor group. Optionally, you can use emojis to further emphasize their importance.
The use of Flavors with active 'Require Value Input' also works when they are displayed in linked project master data flavor groups within a task.