Conditions

Access

imos Ribbon : Main data > Main data > Element Manager > General Rules

Organizer > Tab Element Manager > General Rules

General Information

Conditions are applied in many areas in imos and are the basis for several selection and filter criteria.

The selectable attributes depend on which type has been selected.

ATTENTION: When setting conditions, make sure that the value types being compared are compatible. Both comparison values MUST have the same value type. If they do not, the parent dataset (e.g., the principle) will be ignored because the system cannot evaluate it.
  • Positive example: The Condition is defined as | Calculation Factor | not equal | 0 |.

    Test with Calculation Factor=2.5 → 2.5 ≠ 0 can be evaluated because both values are of type 'number'.

  • Negative example: The Condition is defined as | Calculation Factor | not equal | None |.

    Test with Calculation Factor=2.5 → 2.5 ≠ None CANNOT be evaluated because '2.5' is a 'number' and 'None' is a 'String'.

Options

Category

Filter the selection list in the Type combo box by category. Filtering helps to distinguish between the many condition types and to find the right type for your purposes. The following categories are available:

  • Standard: Condition types for most use cases in the area of CAD, CAM and outputs (annotating, dimensioning, document manager, ...)
  • Routing: Condition types for costing/ calculation and the use of routings
  • Descriptors: Condition types for Descriptors
Type

For assigning to a routing, the selected type must correspond with the type in the routing.

For assigning to a production order the Condition must have the type Production Manager part.

Notes Editable text field.
Declaration Declare attributes as variables which can be used as the comparative value, for example as part of a formula. Declaring variables is especially useful for PXM conditions.
Conditions

The available conditions depend on the selected type.

Extra for PXM-* types:

In a Condition of type PXM-*, for example PXM-Part, you can also nest sub-conditions of different PXM-* types. You define the type of a sub-condition in the first column.