[Condition Settings] Screen
This screen is displayed in the following cases.
- When [Add Condition] is clicked on the [Output Destination Settings] screen
- When [Settings] is clicked for [Output Conditions] on the [Output Destination Settings] screen
It enables you to configure the output conditions for each output destination.
- Up to 10 conditions can be set for a single output destination.
- The values that you can select for [Attribute] on this screen depends on the item selected in [Input].
[Attribute]
Selects the attribute.
[Condition]
Selects the condition.
[String to Compare]
Enables you to enter a string to compare when the following items are selected in [Condition].
- [Contains the following string]
- [Does not contain the following string]
- [Exact match with the following string]
- [Does not match with the following string]
- [Starts with the following string]
- [Does not start with following string]
- [Ends with the following string]
- [Does not end with the following string]
- [is equal to the following number]
- [is not equal to the following number]
- [is greater than or equal to the following number]
- [is less than or equal to the following number]
- [is greater than the following number]
- [is less than the following number]
- [has no value]
- [has a value]
[OK]
Saves the settings.
- The attribute value is handled as a number if any of the following conditions are selected in the [Output Conditions] settings.
- [is equal to the following number]
- [is not equal to the following number]
- [is greater than or equal to the following number]
- [is less than or equal to the following number]
- [is greater than the following number]
- [is less than the following number]
- Note the following when a condition that handles an attribute value as a number is selected.
- When there is trouble handling or interpreting attribute values as numbers, they are deemed to not meet the set conditions and skipped.
- Numbers use commas to separate digits and periods to represent decimal points. (For example: 123,456,789.012) Numbers cannot be recognized correctly otherwise.
- Attribute values containing a unit that includes a number, such as "m2", cannot be correctly interpreted as numbers.
- Attribute values other than the workspace integer type/floating point type cannot be handled as negative values. Symbols such as the minus symbol are ignored.