Create a condition

  1. Go to the Presentation tab.
  2. Right click the Conditions folder and select New Condition.
  3. Click the new condition Condition_plan and define the attributes:
    • Technical Name: Enter a name for the condition. It is recommended that the name indicates the meaning of the condition. The name is used to identify the condition in selectors.
    • Group: By default new conditions are subnodes of the Conditions explorer node. You can type in a group name to generate a sub-folder of the Conditions node and move the condition to this folder. If sub-folders already exist, you can alternatively select an existing folder.
    • Type: Select Expression.
    • Check Result Type: Select either Positive or Negative to define what constitutes a fulfilled condition.
      • Positive means that the condition is fulfilled if the query associated with the configured report delivers a result.
      • Negative means that the condition is fulfilled if the query associated with the configured report delivers no result.
    • Expression: Open an editor for an attribute and enter the expression that shall be evaluated for the condition. Click for details about the expression language.
  4. Right-click the condition and select Set Condition State to 'Active' to activate the condition.
  5. In the toolbar, click the Save  Save_Expand button.

Expressions for conditions have the following syntax:

  • @ParameterName Operator Value
  • @Type == 'CloudService'

The parameter defines the value read from a filter or editor field. On assignment of the condition to a filter or editor field, you can specify which of the other fields in the editor or filter shall be read to get a value substituting the parameter.

For example if the expression defined for the condition is @Type=='CloudService' and the Type parameter is mapped to an interface control that returns the value CloudService , the expression will read 'CloudService'=='CloudService' and is fulfilled.

Take the following into account when defining the condition:

  • For some operators, like EMPTY, the definition of a value is not required.
  • String values and boolean values must be placed in single quotes. .
  • Strings in conditions are case-sensitive.
  • Multiple expressions may be combined via AND or OR, whereby individual expressions must be placed in parenthesis.
    • (@Type == 'CloudService') I ((@Type == 'OnPremise') & (@CloudCandidate == 'True'))
  • A parameter cannot be defined as a value for an operator. It is not possible to compare the values of two interface controls within one condition.

You can use the following operators and connectors. The value type is specified in the example syntax. If the value type is EMPTY, no value needs to be defined.

equals @Param == 'STRING ' (or 'True ' and 'False' for Boolean values)
does not equal @Param != 'STRING'
in @Param IN ['STRING', 'STRING', 'STRING'] (used when the value is a list)
not in !(IN ['STRING', 'STRING', 'STRING'] (used when the value is a list)
begins with @Param BEGINS_WITH 'STRING'
ends with @Param ENDS_WITH 'STRING'
contains @Param CONTAINS 'STRING'
does not contain !(CONTAINS 'STRING')
is between (@Param > NUMERIC1) & (@Param < NUMERIC2)
is empty @Param EMPTY
is not empty !(@Param EMPTY)
is greater than @Param > NUMERIC
is greater than or equal to @Param >= NUMERIC
is less than @Param < NUMERIC
is less than or equal to @Param <= NUMERIC
AND &
OR |
NOT !