# Using Wildcards in Search

## Wildcards Accepted

You can use the following Wildcards in your searches:

1. % Percent Symbol (except as noted [below](#global-search-portal))

   Match Any Sequence of Characters. Represents zero or more characters in a search. 

   **Example: %out** – All results that contain the word “out” at the end 

   **Example: %out%** – All results that contain the word “out” in any position 

   **Example: Out%** – All results that start with the word “Out”; Outlook, OutBound
2. \_ Underscore 

   Matches a Single Character. Represents a single character in a search.

   **Example: SXY\_0091** – All results where this reference is contained: SXY**9**0091, SXY**8**0091, SXY**7**0091, and so on.
3. \[ ] Square Brackets 

   Match Any Single Character within a Range or Set 

   **Example: \[JM]on**  - Jon, or Mon

   **Example:\[A-D]** - All items that start with A, B, C, or D
4. \[^] Caret Enclosed in Square Brackets 

   Exclude Characters within a Range or Set 

   **Example: \[^Out]%** - All results that do not start with “Out”
5. "-" Hyphen 

   Match or define a Range of Characters within Square Brackets. 

   **Example: \[A-F]%**  - Anything that starts with A through F

   **Example: \[0-9]% -** Anything that starts with 0 - 9

## What is searched?

What is searched is determined by the entity you are actively searching, exceot for as noted in the [Global Search widge](#global-search-portal)[t](#global-search-portal) below.  

### Global Search (Portal)

{% hint style="warning" %}
**Known Issue: *****Unexpected Behavio*****r.** Using wildcards (%) in the Global Search widget causes Self-Service Portal Menus to behave unpredictably. This is resolved in ASM 10.6.9.14628.
{% endhint %}

**Calls/Tickets** = Description, Comments, Solution's Summary\
**Requests** = Title, Description, Authorization Comments\
**Tasks** = Description and History\
**Knowledge** = Title, Abstract, Solution, Additional Information field\
**Bulletins** = Body of the Bulletin

### Text Based, Field-Level Searches

Search the related table/or linked tables for the data to call back. 

{% @arcade/embed flowId="6sjMpmbw0TSkxtnWwdLL" url="<https://app.arcade.software/share/6sjMpmbw0TSkxtnWwdLL>" %}


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.alemba.com/asm-hermes/use-asm/using-asm-core/getting-started/searching-for-items/using-wildcards-in-search.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.