Regex Partial Match

ASTER::CONDITION::REGEX::Search

Search for a partial match of the query string using regular expressions within the target string.

It returns true when there is a partial match.

It is not necessary for the keyword to match the entire string; it returns “true” if even a part of it matches.


​

There are two main types of string searches using regular expressions: "exact match" and "partial match". In internal processing, exact match searches are referred to as "match", while partial match searches are referred to as "search".

  • ASTER::CONDITION::REGEX::Match ( Exact Match )

  • ASTER::CONDITION::REGEX::Search ( Partial Match )


If there is no match in the search, you can use the immediate execution condition "REGEX Mismatch".

You can write separate processes for matching and non-matching results in the event editor on CF25. Additionally, you can identify events using the "search uID".

New Features

You can obtain all submatches on a capture group basis as strings and export them to JSON. This makes it convenient to verify search results and edit strings.


Parameter.1

Source String for Search

Parameter.2

Query String, using regular expressions ( Keyword )

Parameter.3

“Search uID” is the Number for event identification.

Key Point.1

Regex.Partial Match, also internally referred to as regex.search, can be used in the same way as a regular string search without using regular expressions. However, it incurs higher processing load to obtain search results compared to a regular string search.

Key Point.2

If the regular expression used in the search contains a syntax error, the "Regular Expression Error" of immediate execution conditions can be utilized. Event identification using the search identification number is available.

"Search identification number" is also explained in the section "Mismatch determination".

If you do not know how to use it, please use the "search identification number" with a value of zero.However, if you set it to zero, you will not be able to identify events using the "search identification number.

If the "search identification number" is properly set at the time of search, the event can be identified by the "search identification number" in the "mismatch judgment" which is an immediate execution condition when there is no match in the search.