⚙️ Flavor configuration

In the configuration dialog of a Flavor, you define global properties and rules for the respective custom field. The settings apply everywhere the Flavor is used in the workspace.

Depending on the Flavor type, you can edit the title and description, restrict editing, define required fields or conditions, and specify visibility and usage context, among other things.

Open the Flavor configuration

Open the Flavor and select Configure to access the global settings.

Title

The Title field defines the name of the Flavor. The title is unique throughout the system and is displayed wherever the Flavor is used, for example in task dialogs, project master data, or List views.

The title can be changed later as long as editing of the Flavor settings has not been locked.

Description

In the Description field, you can add additional information about the Flavor. The description helps other people better understand the purpose of the field and the expected input.

Options

In the Options section, you can define how the Flavor may be edited and used.

Lock editing of settings

With Lock settings editing, you protect the Flavor configuration from changes.

Once enabled, only the person who set the lock and administrators can generally edit the protected settings or remove the lock again.

The following Flavor properties may be affected, for example:

• Title
• Type
• Color
• Settings in the configuration dialog
• Visibility options

Lock editing of values

With Lock value editing, you can additionally prevent other people from changing existing values of this Flavor.

Only the person who set the lock and administrators can then continue to edit the Flavor values.

Lock editing of values for guests

With Lock value editing for guests, you can specifically prevent people with a guest role from editing the values of the Flavor.

The restriction applies only to guests. Other people can continue to edit the values according to their normal permissions unless Lock value editing has also been enabled.

Whether guests can see the Flavor at all is still controlled separately through the Flavor's visibility.

Value input required

With Value input required, the Flavor is defined as a required field. The setting applies globally to this Flavor.

The property is available for Flavors used in tasks or project master data. If the option is enabled, the Flavor is marked with an *.

Use in tasks

If a task contains a Flavor with required value input, smenso checks whether a value has been entered when the task is changed to the system status Done.

If the required value is missing, the status change is prevented and a corresponding notice is displayed. The task can still be saved or closed.

Use in project master data

In project master data, a Flavor with required value input is also marked with an *. Apart from this, the option has no additional effect there.

Set condition

With Set condition, you can define rules for permitted Flavor values.

For example, for a Number Flavor you can specify that a value must be greater than 0 or fall within a certain value range.

If a value is entered that does not meet the condition, the field is highlighted accordingly. However, saving is not prevented.

You can also define your own validation description and a color for conditions that are not met.

In the following example, the entered value does not meet the defined condition. The value is therefore highlighted in color and marked with a notice.

Sum values from subtasks

For supported Number Flavors, you can specify that the value of a parent task is automatically calculated from the values of its subtasks.

Values are entered at the lowest existing level. Parent tasks automatically take over the sum of the directly subordinate values.

As long as a task has no subtasks, the value can be entered directly on the task. As soon as subtasks are present, the value of the parent task is calculated automatically.

Visibility

Under Visibility, you define which people can see the Flavor.

• Everyone
  The Flavor is visible to all authorized people in the workspace, including guests.
• Everyone (no guests)
  The Flavor is visible to internal people but hidden from guests.
• Selected Persons/Teams
  The Flavor is visible only to the selected people or teams.

Context

Under Context, you define the functional area in which the Flavor is used.

The context influences, among other things, where the Flavor is offered in filter menus or column selection and which Flavor values can be used in certain analyses.

For example, time analyses take into account Flavor values assigned to the Time context.

• None – not assigned to a specific context
• Task – use in the context of tasks
• Project – use in the context of projects and project master data
• Status report – use in the context of status reports
• Person – use in the context of person master data
• Time – use in the context of time tracking

Category

Using the Category dropdown, you can assign the Flavor to a thematic category. This allows Flavors within the workspace to be structured more clearly and distinguished from one another more easily.

By default, the General category is selected. If needed, you can select another available category from the dropdown.

The category is used for the organizational assignment of the Flavor and does not change either the Flavor type or the stored values.

Advanced

Copy GUID

In the Advanced section, you can copy the Flavor's unique GUID to the clipboard.

The GUID may be required, for example, for Formula Flavors, API integrations, or technical troubleshooting.

Delete Flavor permanently

Using Delete permanently at the bottom of the configuration dialog, you can completely remove the Flavor from the workspace.

Frequently asked questions (FAQ)

How can I configure a Flavor?

Open the desired Flavor and select Configure. There you can define, among other things, the title, description, permissions, visibility, context, and other properties of the Flavor.

How can I prevent others from editing a Flavor?

Enable Lock editing of settings. Afterwards, only the person who set the lock and administrators can generally edit the protected Flavor settings or remove the lock again.

How can I lock editing of Flavor values?

First enable Lock editing of settings and then Lock editing of values. Afterwards, only the person who set the lock and administrators can edit the Flavor values.

Can I show a Flavor to guests without allowing them to edit its value?

Yes. For example, set Visibility to All and additionally enable Lock editing of values for guests. Guests can then see the Flavor but cannot change its value.

How can I completely hide a Flavor from guests?

Under Visibility, select All (no guests). The Flavor will then not be displayed to people with a guest role.

Can a Flavor be defined as a required field?

Yes. Enable Value input required. The Flavor is then marked with an *. For tasks, smenso checks whether a required value has been entered when changing to the system status Done.

Can I define which values are allowed in a Flavor?

Yes. Using Define condition, you can define a validation rule. Values that do not meet this condition are highlighted accordingly and can be provided with a custom validation description.

What does the context of a Flavor mean?

The context defines the functional area to which a Flavor is assigned, for example Task, Project, Status report, Person, or Time. This influences, among other things, where the Flavor is offered in filters, columns, and analyses.

What is a Flavor category used for?

The category is used for the organizational assignment and structuring of Flavors in the workspace. It does not change either the Flavor type or the values already stored.

Can Flavor values be automatically summed from subtasks?

For supported Number Flavors, values can be automatically summed from subtasks. Values are entered at the lowest existing level, while parent tasks automatically calculate their values from the subordinate tasks.

What happens if I permanently delete a Flavor?

With Delete permanently, the Flavor is completely removed from the workspace. It will no longer be available afterwards and will be removed from all objects in which it was used. The action cannot be undone.