The process of searching for objects in Heeds involves constructing a query, which is composed of a composition mode and one or more conditional statements. Each conditional statement comprises a field, an operator, and a value. For example, if you were searching for Heeds based on the metadata attribute "id" that you sent, your query would appear as follows: "id==inx-1234," where "id" represents the field, "==" indicates the operator, and "inx-1234" is the specified value.
The composition mode can be either "And" or "Or." When searching for Heeds and you intend to evaluate the values of multiple metadata fields, such as "id" and "type," you would utilize the "And" composition mode because both conditional statements must be true for a match. On the other hand, if you only require one of the conditional statements to be true, you would opt for the "Or" composition mode.
Below is our example demonstrated in the Boolean Condition activity.
This condition based searching is used in a number of workflow activities, these include
- Find Channels
- Find Users
- Find Heeds
- Boolean Condition
Operators
The following operators are available:
- Equal to (==) - returns true if the field value matches the value
- Not Equal to (!=) - returns true if the field value does not match the value
- Greater than (>) - returns true if the field value is greater than the value
- Greater than or equal to (>=) - returns true if the field value is greater than or equal to the value
- Less than (<) = returns true if the field value is less than the value
- Less that or equal to (<=) - returns true if the field value is less that or equal to the value
- In - returns true if the field value is contained within the value, the value could be an array or a single value
- Not in - returns true if the field value is not contained within the value, the value could be an array or a single value
- Regular Expression - advanced searching, will return true if the field value matches the regular expression
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article