When you create a
workflow, you can limit the set of entries from a table or list of values seen
by the user at run time. You do this by either selecting the values explicitly
Input List, or by using a filter expression (Admin Input
Filter). This section describes the syntax for writing admin input
There are two types
of data in
Cisco UCS Director Orchestrator
that you can filter:
table with two or more columns. You filter the columns to select the rows to
Lists of values
(LOVs)—a list of items, all of the same type. You filter the values in the
In addition, some
inputs are numeric, for example, disk storage sizes. You must include units
when you filter numeric inputs, as described below.
To filter a tabular
input, the input filter criteria have this form:
column_label operator expression [ AND column_label operator expression ]
where the elements
of the expression are defined as follows:
at the top of the column to be filtered. Type the name exactly as it appears.
The label is case sensitive and must include any spaces or special characters.
Do not enclose the label in quotes.
operator name is case sensitive; it must be all upper case.
and NOT_SUBSET are operators for list type inputs.
brackets denote that the enclosed expression is optional and can be repeated.
The brackets themselves are not to be included in the filter criteria
additional criteria to be met. If one or more AND criteria are appended, all of
them must be met to match a record.
criteria are applied serially: all records meeting the first criterion are
subjected to the second criterion, then those results to the third, and so on.
operators besides AND can be used to append additional criteria. In particular,
OR cannot be used. In other words, additional criteria can only be used to
narrow the search further, not to expand it.
match_expression [ OR match_expression ]
a union of any of the specified
match_expressions. In other words, only one of the
match_expressions has meet the criterion for that part
of the expression to be true.
regular expression using standard regular expression wildcard search characters
and escape characters. The full POSIX regular expression syntax is not
If you are
unfamiliar with regular expressions you can match literal values provided they
don't contain regex special characters, or that you escape the special
information about regular expressions, consult any regular expression reference
on the internet; there are many.
match_expression is enclosed in quotes, a
case-sensitive comparison is made, if appropriate.
Following is an
example of a table-type filter:
Cloud CONTAINS vcenter21 OR vcenter98 AND Power Status EQUALS off OR unknown
CONTAINS vcenter21 OR vcenter98 will match names containing
vcenter98, such as
TESTvcenter98. If the admin were interested only in
vcenter21 and vcenter98, a better expression would be
EQUALS vcenter21 OR vcenter98.
Lists of Values
LOV types are
lists of single values. To filter an LOV you therefore omit the column name,
and the AND operator is not used. The top-level search syntax is:
operator match_expression [ OR match_expression ]
The elements of
the syntax are as described for tabular data, above, with the exception that
IS_SUBSET and NOT_SUBSET operators are not allowed.
For example, if
the power status values from the tabular data example were in an LOV, the
search would look like this:
data such as disk size, LUN size, and volume size are specified with
units--megabytes (MB), gigabytes (GB) or terabytes (TB). If the units are given
in a table column, the units are part of the column label and must be included
in your criteria; for example:
LUN Size (GB) EQUALS 10.0
It is also
important to note that numeric expressions in filter criteria are regex matches
and not numerical comparisons. For example, consider this filter criterion:
LUN Size (GB) EQUALS 10
records with LUN size given as