4.1.1
Standardized the condition judgment logic in FineDataLink.
4.1.5.5
Applied the condition judgment logic in the File Transfer node.
This document introduces the condition judgment logic in FineDataLink, applying to:
Data Filtering > Add Condition and Data Distribution > Distribution Condition
Conditional Branch > Add Condition and Loop Container > Execution
Condition > Configuration Condition
Jodoo Input > Filtering Condition
MongoDB Input > Conditional Query > Configure Condition
File Input > Read Folder > File Filtering
File Transfer > Read Folder > File Filtering
Starting from FineDataLink 4.1.1, the condition judgment logic has been standardized.
The following table describes the details.
Date
Between
No Limit ≤ Value < No Limit (default value)
All, including null values
No Limit ≤ Value < Y
Less than Y, excluding null values
X ≤ Value < No Limit
Greater than or equal to X
X ≤ Value < Y
Greater than or equal to X and less than Y
Not Between
No Limit ≤ Value < No Limit
Empty
Greater than or equal to Y
Less than X, excluding null values
Less than or equal to X and greater than or equal to Y, excluding null values
Before
Value ≤ No Limit
Value < X
After
No Limit ≤ Value
X < Value
Greater than X, excluding null values
Equal To
No Limit
X
Equal to X
Not Equal To
Not equal to X, including null values
Null
-
Null values
Not Null
All non-null values
Text
In
For details, see Differences Between In and Contain Operators.
All data, including null and empty values
If the value is in Set X, the system will return the value. (Values that are null or empty are excluded from the results.) If not, the system will return an empty value.
Not In
If some elements of the value are not included in set X, the system will return the value. Values that are null or empty are included in the results.
Contain
The system will return all data. (Null values are included in the results, while empty values are excluded.)
If the value contains all elements of Set X, the system will return the value. (Values that are null or empty are excluded from the results.) If not, the system will return an empty value.
Not Contain
If the value does not contain all elements of Set X, the system will return the value. (Null values are included in the results, while empty values are excluded.)
Begin With
All, including empty strings but excluding null values
Strings that start with X, excluding empty strings and null values
Not Begin With
Strings that do not start with X, including empty strings but excluding null values
End With
Strings that end with X, excluding empty strings and null values
Not End With
Strings that do not end with X, including empty strings but excluding null values
Empty strings and null values
All, excluding empty and null strings
Value
X,Y
Equal to X or equal to Y
Not equal to X, excluding empty and null values
Not equal to X, and not equal to Y, excluding empty and null values
Greater Than
Less Than
Greater Than or Equal To
Greater than or equal to X, excluding null values
Less Than or Equal To
Less than or equal to X, excluding null values
Boolean
True
The system will filter the database data that exactly matches the boolean character, retrieving values of true or 1.
False
The system will filter the database data that exactly matches the boolean character, retrieving values of false or 0.
Others
Equal to X, excluding null values
All, excluding null values
Not equal to X, excluding null values
Supported condition types may vary across different functions.
Data Filtering > Add Condition
Data Distribution > Distribution Condition
Supports all types.
Conditional Branch > Add Condition
Loop Container > Execution Condition > Configuration Condition
Field types except for Date, Text, Value, and Boolean are not supported.
Supported:
Text (filename)
Date (file creation time and file modification time)
Unsupported: Value, Boolean, and other types
Limit support:
Null and Not Null are not supported for fields of text or date types.
Unsupported: Boolean and other types
Limit support. For details, see the following table.
Jodoo API has restrictions on judgment logic. FineDataLink supports the following condition types based on the judgment logic provided by the API.
Equal To and Not Equal To
Between (Only supports X ≤ Value ≤ Y.)
Null and Not Null
In (Allows passing up to 200 items.) and Not In (Allows passing up to 200 items.)
Verified and Unverified
In the Conditional Branch and Loop Container nodes, judgment conditions are converted to logical operators for display.
AND
&&
OR
||
==
!=
>
<
>=
<=
Hierarchical Nesting
()
Example: If the judgment condition is that the parameter ${test} is not equal to 1 or greater than 2, it will be converted to the logical expression ${test}!=1||${test}>2.
For FineDataLink of V4.1.1 and later versions, the condition types are described as follows:
1. Data Filtering > Add Condition and Data Distribution > Distribution Condition. Conditional Branch > Add Condition and Loop Container > Execution Condition > Configuration Condition.
X-Y
X < Value < Y
1\true
0 or false
Other values, including parameters
1 or true
2. MongoDB Input > Conditional Query > Configure Condition
Number
Range
Defining the date-type value:
Changed Select to Date after the upgrade.
MongoDB Input remains unchanged after the upgrade, still as MongoDB Input.
Equal To Any
X,Y,Z
Not Equal To Any
3. Jodoo Input > Filtering Condition
X ≤ Value ≤ Y
滑鼠選中內容,快速回饋問題
滑鼠選中存在疑惑的內容,即可快速回饋問題,我們將會跟進處理。
不再提示
10s後關閉
Submitted successfully
Network busy